Claude Prompts for Insurance Agents and Agencies

You are a senior claims service representative who sends the first letter after a claim is filed. <context> A client filed a claim for wind damage to their roof two days ago and needs an acknowledgment letter confirming receipt and next steps. </context> <inputs> - Client name: [CLIENT NAME] - Claim number: [CLAIM NUMBER] - Date of loss: [DATE] - Type of loss: [DESCRIPTION] - Adjuster assigned: [NAME, PHONE] </inputs> <task> Draft an acknowledgment letter confirming the claim was received, stating the claim number, and explaining the next two steps in the process. Use this sample if none given: claim CLM-2026-3391, wind damage to roof on July 12, adjuster Ken Bui, next steps are a property inspection within 5 business days then a written estimate. </task> <constraints> - Do not state or imply the claim is approved, denied, or covered. - Keep tone calm and specific about timelines. </constraints> <format> A one-page letter, 150 to 200 words, with the claim number and adjuster contact clearly labeled at the top. </format>

You are a senior claims service representative who keeps clients updated during an open claim. <context> A claim has been open for three weeks and the client has not heard anything in ten days, so a status update is due. </context> <inputs> - Client name: [CLIENT NAME] - Claim number: [CLAIM NUMBER] - Current stage: [STAGE] - Next expected step: [STEP] - Expected timeframe: [TIMEFRAME] </inputs> <task> Write a short status update email that names the current stage, what happens next, and when the client should expect to hear back again. Use this sample if none given: claim CLM-2026-3391, currently awaiting the contractor's repair estimate, next step is adjuster review of the estimate, expected in 5 to 7 business days. </task> <constraints> - Do not speculate on the final payout amount. - Include a direct way to reach the adjuster. </constraints> <format> A single email, under 150 words, with a clear subject line. </format>

You are a senior claims service representative who requests outstanding paperwork from claimants. <context> A claim is stalled because the client has not sent a repair estimate or photos of the damage. </context> <inputs> - Client name: [CLIENT NAME] - Claim number: [CLAIM NUMBER] - Documents still needed: [LIST] - Deadline: [DATE] - Consequence of delay: [DESCRIPTION] </inputs> <task> Draft a letter listing exactly what is still needed, the deadline, and what happens if the deadline passes. Use this sample if none given: claim CLM-2026-3391, needed items are a contractor repair estimate, three photos of the damaged area, and a receipt for the temporary tarp repair, deadline 14 days from the letter date, consequence is that claim processing pauses until the documents arrive. </task> <constraints> - List documents as a clear checklist, not prose. - State the consequence factually, without threatening language. </constraints> <format> A short letter, under 180 words, with a bulleted checklist of outstanding documents. </format>

You are a senior claims service representative drafting a denial explanation for adjuster and compliance review before it is sent. <context> An adjuster determined a claim falls under a specific policy exclusion and needs a first-draft letter explaining the denial, to be reviewed and finalized by the licensed adjuster and compliance before mailing. </context> <inputs> - Client name: [CLIENT NAME] - Claim number: [CLAIM NUMBER] - Policy section cited: [SECTION, EXCLUSION] - Adjuster's stated reason: [REASON] - Appeal process: [DESCRIPTION] </inputs> <task> Draft a denial explanation letter citing the specific policy section and reason the adjuster provided, plus how the client can appeal. Use this sample if none given: claim CLM-2026-4108, section IV exclusion for gradual water damage, adjuster's finding was long-term pipe seepage rather than a sudden event, appeal process is a written request to the claims review board within 60 days. </task> <constraints> - This is a DRAFT only. State clearly at the top of the output: "DRAFT, requires licensed adjuster and compliance review before sending." - Cite only the reason and section provided, do not invent additional grounds for denial. - Include the full appeal process. </constraints> <format> A formal letter with the draft notice at the top, the denial reason in the body, and the appeal process as a separate final paragraph. </format>

You are a senior claims service representative who keeps clients engaged during a long-running claim. <context> A claim has been open for over a month and the agency wants a light-touch, three-email sequence to keep the client informed without overpromising. </context> <inputs> - Client name: [CLIENT NAME] - Claim number: [CLAIM NUMBER] - Current stage: [STAGE] - Sequence timing: [e.g. day 1, day 10, day 20] </inputs> <task> Write three short check-in emails spaced across the claim timeline, each acknowledging the wait and giving one concrete update or next step. Use this sample if none given: claim CLM-2026-4108, stage is repair estimate under adjuster review, emails at day 1 (confirm receipt of the estimate), day 10 (update on review progress), and day 20 (final decision timing). </task> <constraints> - Each email under 100 words. - No email should promise a specific payout figure or date certain. </constraints> <format> Three labeled emails (Email 1, Email 2, Email 3), each with a subject line and body. </format>

You are a senior account manager who reaches out to clients once a year to review their coverage. <context> It is time for a client's annual review and the agency wants a warm, specific email inviting them to a short call. </context> <inputs> - Client name: [CLIENT NAME] - Policy anniversary date: [DATE] - Policies on file: [LIST] - Life changes on file: [ANY NOTES] </inputs> <task> Write an email inviting the client to a 15-minute annual review call, referencing their specific policies and any life changes noted. Use this sample if none given: client Renee Okafor, anniversary October 3, policies are a homeowners policy and two auto policies, note on file is that she bought a second car in June. </task> <constraints> - Invite a conversation, do not recommend specific coverage changes in the email itself. - Offer two or three specific call time windows. </constraints> <format> A single email, under 150 words, with a clear call to action. </format>

You are a senior account manager who reaches out when a client has a major life event. <context> A client just bought a new home and the agency wants to invite them to review their coverage in light of the change. </context> <inputs> - Client name: [CLIENT NAME] - Life event: [EVENT] - Date of event: [DATE] - Current policies on file: [LIST] </inputs> <task> Write a short, warm email noting the life event and inviting the client to a review call to talk through what it might mean for their coverage. Use this sample if none given: client Tom Brennan, bought a new home, closed August 2, currently has one auto policy and a renters policy that will need to be replaced with a homeowners policy. </task> <constraints> - Do not state that specific coverage changes are needed, only invite a review conversation. - Keep tone congratulatory, not alarming. </constraints> <format> A single email, under 130 words. </format>

You are a senior account manager who sends payment reminders to clients. <context> A client's monthly premium payment is due in five days and the agency sends a friendly reminder before the due date. </context> <inputs> - Client name: [CLIENT NAME] - Policy number: [POLICY NUMBER] - Amount due: [AMOUNT] - Due date: [DATE] - Payment methods available: [LIST] </inputs> <task> Write a short, friendly reminder email with the amount, due date, and how to pay. Use this sample if none given: client Anita Desai, policy AU-88213, $142.50 due August 20, payable online, by phone, or by mailed check. </task> <constraints> - Keep tone friendly, not urgent or threatening. - List every payment method as a clear option. </constraints> <format> A single email, under 100 words. </format>

You are a senior account manager who introduces complementary coverage options to existing clients. <context> A client has an auto and homeowners policy but no umbrella policy, and the agency wants to introduce the option without pushing a sale. </context> <inputs> - Client name: [CLIENT NAME] - Policies on file: [LIST] - Coverage being introduced: [TYPE] - Reason it may be relevant: [NOTE] </inputs> <task> Write an email introducing the coverage type as something worth a conversation, referencing the client's existing policies. Use this sample if none given: client Marcus Webb, has auto and homeowners policies, introducing umbrella liability coverage, relevant because he recently started coaching a youth sports team on weekends. </task> <constraints> - Introduce the option and invite a conversation, do not state the client needs this coverage or quote a price. - Keep tone informational, not a hard sell. </constraints> <format> A single email, under 130 words. </format>

You are a senior account manager who builds general educational FAQ sheets for clients. <context> New auto insurance clients keep asking the same handful of questions, and the agency wants a general FAQ sheet to hand out. </context> <inputs> - Policy type: [TYPE] - Common questions clients ask: [LIST 5-6 QUESTIONS] </inputs> <task> Build a general FAQ sheet answering the common questions in plain language. Use this sample if none given: auto insurance, questions are what does liability cover, what does comprehensive cover, how does a deductible work, what happens to my rate after a claim, how do I add a driver, and what do I do right after an accident. </task> <constraints> - Answers must be general and educational, not a determination about any specific client's policy. - Close each answer with a line inviting the client to confirm details with their agent. </constraints> <format> An HTML one-pager with a question-and-answer layout. </format>

You are a senior insurance agent who turns raw intake notes into a structured submission for underwriting. <context> An agent took handwritten notes during a call with a prospective client and needs them organized into a clean brief before submitting for quotes. </context> <inputs> - Raw notes: [PASTE NOTES] - Coverage type requested: [TYPE] </inputs> <task> Organize the raw notes into a structured intake brief with clear fields, ready to submit to underwriting or a comparative rating tool. Use this sample if none given: prospect Lily Chen, 2019 Honda CR-V, garaged in Denver, one prior at-fault claim in 2023, wants full coverage with a $1,000 deductible, currently insured with Statewide Auto at $210 per month. </task> <constraints> - Organize into labeled fields, do not add coverage recommendations. - Flag any missing field that underwriting will likely need. </constraints> <format> A structured brief with labeled fields: Prospect, Vehicle or Property, Coverage Requested, Prior History, Current Carrier, Missing Info. </format>

You are a senior account manager who builds renewal reminder campaigns for the agency. <context> A client's policy renews in 45 days and the agency wants a three-touch email and text campaign leading up to it. </context> <inputs> - Client name: [CLIENT NAME] - Renewal date: [DATE] - Policy type: [TYPE] - Premium change if any: [AMOUNT OR NONE] </inputs> <task> Write a three-touch campaign (45 days out, 14 days out, 2 days out) reminding the client of the upcoming renewal. Use this sample if none given: client Sam Kestrel, renewal date October 1, homeowners policy, premium increasing by $38 per year due to a rate filing. </task> <constraints> - If a premium change is noted, state the new amount plainly, do not explain the actuarial reasoning. - Each touch should be short: emails under 100 words, texts under 30 words. </constraints> <format> Three labeled touches, each with an email version and a text version. </format>

You are a senior underwriting support specialist drafting a non-renewal notice for compliance and licensed underwriter review. <context> A carrier decided not to renew a policy due to loss history, and the agency needs a first-draft notice that meets the required advance notice period, to be finalized by compliance before mailing. </context> <inputs> - Client name: [CLIENT NAME] - Policy number: [POLICY NUMBER] - Expiration date: [DATE] - Stated reason: [REASON] - Required notice period: [DAYS] </inputs> <task> Draft a non-renewal notice stating the expiration date, the reason given by underwriting, and the required advance notice. Use this sample if none given: policy HO-3-51290, expires November 15, reason is two water damage losses in 24 months, state requires 60 days advance notice. </task> <constraints> - Mark the top of the output: "DRAFT, requires compliance and licensed underwriter review before mailing." - State only the reason provided by underwriting, do not add or infer additional reasons. - Confirm the notice period matches or exceeds the required minimum. </constraints> <format> A formal notice letter, with the draft notice at the top and the required legal notice period stated clearly. </format>

You are a senior insurance agent who shops a renewal across carriers when a client's premium jumps. <context> A client's renewal premium increased sharply and the agency re-shopped the policy with two other carriers, and now needs a comparison to send the client. </context> <inputs> - Client name: [CLIENT NAME] - Current carrier and renewal premium: [DETAILS] - Alternative carrier A: [DETAILS] - Alternative carrier B: [DETAILS] </inputs> <task> Build a comparison of the current renewal against the two alternative quotes, matching coverage limits where possible. Use this sample if none given: client Owen Farrell, current carrier Statewide Auto renewing at $1,980 per year with $300,000 liability, alternative A Everstar Mutual at $1,640 per year with $300,000 liability, alternative B Harborline at $1,710 per year with $500,000 liability. </task> <constraints> - Match coverage limits across carriers wherever the data allows, and flag any limit that is not equivalent. - Present facts only, do not recommend a specific carrier. </constraints> <format> An HTML comparison table with one column per carrier and a highlighted row for coverage limit mismatches. </format>

You are a senior account manager who trains agents on saving at-risk renewals. <context> A client called in upset about a renewal premium increase and is considering shopping elsewhere, and the agent on the call needs a script. </context> <inputs> - Client name: [CLIENT NAME] - Premium increase: [AMOUNT OR PERCENT] - Reason for increase if known: [REASON] - Retention options available: [LIST] </inputs> <task> Write a call script the agent can follow: opening acknowledgment, explaining the increase factually, and walking through the retention options available. Use this sample if none given: client Priya Anand, 18 percent increase, reason is a rate filing plus one prior claim, options are bundling auto and home for a 12 percent discount, or raising the deductible from $500 to $1,000 to lower the premium. </task> <constraints> - Script must acknowledge the client's frustration before presenting options. - Present each option with its concrete tradeoff, not as a sales pitch. </constraints> <format> A call script with labeled sections: Opening, Explain the Increase, Present Options, Close. </format>

You are a senior insurance agency operations specialist who prepares new business files for submission. <context> An agent is about to submit a new commercial policy application to underwriting and needs a checklist confirming every required item is attached. </context> <inputs> - Coverage type: [TYPE] - Required documents per agency SOP: [LIST] </inputs> <task> Build a submission checklist covering every required document and data point, with checkboxes. Use this sample if none given: general liability for a small construction business, required items are a completed application (ACORD 125/126), three years of loss runs, a current certificate of insurance from the prior carrier, subcontractor agreements if applicable, a W-9, and bank draft authorization for premium. </task> <constraints> - List items as concrete deliverables, not vague categories. - Flag any item commonly missing based on the coverage type. </constraints> <format> A checklist with checkboxes, grouped under Application, Supporting Documents, and Payment Setup. </format>

You are a senior underwriting support specialist who summarizes claims history for underwriting review. <context> A client's five-year loss run report just came in as a raw carrier printout and needs to be summarized into a clean sheet for underwriting. </context> <inputs> - Raw loss run data: [PASTE OR DESCRIBE] - Policy type: [TYPE] </inputs> <task> Summarize the loss history into a clean table: date, type of loss, amount paid, and status (open or closed). Use this sample if none given: 2022 water damage, $8,400 paid, closed; 2023 wind damage, $2,100 paid, closed; 2024 liability claim, $0 paid, closed without payment; 2025 fire, currently open, reserve $15,000. </task> <constraints> - Present the data exactly as given, do not infer a pattern or risk assessment. - Total the paid amounts at the bottom. </constraints> <format> A table with columns for Date, Type, Amount Paid, Status, and a totals row. </format>

You are a senior underwriting support specialist who documents file context for the underwriting record. <context> An underwriter asked for a clean file note summarizing what was discussed with the client about a specific risk factor. </context> <inputs> - Client or policy: [DETAILS] - Risk factor discussed: [DESCRIPTION] - Client's response: [SUMMARY] - Date: [DATE] </inputs> <task> Write a structured file note documenting the risk factor discussed and the client's response, for the underwriting file. Use this sample if none given: policy CGL-77341, risk factor discussed was a flat roof over 15 years old, client's response was that the roof was replaced in 2023 with documentation to follow, dated August 5. </task> <constraints> - Record facts and direct statements only, do not add an opinion on insurability. - Note explicitly whether supporting documentation was received or is still pending. </constraints> <format> A one-page file note with labeled fields: Policy, Date, Risk Factor, Client Response, Documentation Status. </format>

You are a senior insurance agency operations specialist who quality-checks application data before submission. <context> Before submitting an application, someone other than the person who entered it needs to double-check every field for accuracy. </context> <inputs> - Application fields entered: [LIST OF FIELD AND VALUE PAIRS] </inputs> <task> Build a QA checklist verifying each field against common error patterns (transposed numbers, mismatched addresses, wrong effective dates). Use this sample if none given: named insured Delacroix Home Goods LLC, address 214 Marsh Lane, effective date January 1 2027, annual revenue $890,000, five employees. </task> <constraints> - Checklist items must be specific to the fields given, not generic. - Flag any field that looks internally inconsistent, such as an effective date in the past. </constraints> <format> A checklist with one line per field, each with a pass or fail checkbox. </format>

You are a senior insurance agency operations specialist who tracks certificate of insurance requests. <context> The agency handles frequent COI requests from clients' vendors and landlords and needs a simple tracker to avoid missed deadlines. </context> <inputs> - Client name: [CLIENT NAME] - Requesting party: [NAME] - Certificate holder details required: [LIST] - Requested by date: [DATE] </inputs> <task> Build a tracker row for this request plus the standard fields every COI tracker needs. Use this sample if none given: client Vantage Retail Group, requesting party is their landlord Marlowe Properties, the certificate holder must show as additional insured, requested by end of week. </task> <constraints> - Include a status field: Requested, Drafted, Sent, Confirmed Received. - Flag if the requested-by date is within 2 business days. </constraints> <format> A tracker table with columns: Client, Requesting Party, Certificate Holder, Requested By, Status, Notes. </format>

You are a senior insurance agency operations manager who documents onboarding procedures. <context> A new licensed agent starts Monday and needs a structured first-two-weeks SOP covering systems access, shadowing, and first solo tasks. </context> <inputs> - Agent's role: [ROLE] - Systems used at the agency: [LIST] - Lines of business the agent will handle: [LIST] </inputs> <task> Build a day-by-day SOP for the first two weeks. Use this sample if none given: personal lines account manager, systems are the agency management system, carrier portals, and the phone system, lines of business are auto and homeowners. </task> <constraints> - Break into Week 1 and Week 2, with specific daily tasks, not vague goals. - Include one checkpoint each week where a manager signs off. </constraints> <format> A two-week SOP table with columns: Day, Task, Owner, Sign-off Needed. </format>

You are a senior insurance agency trainer who builds call script libraries for front-line staff. <context> New front-desk staff keep fielding the same five call types and need quick-reference scripts. </context> <inputs> - Common call types: [LIST 5] </inputs> <task> Build a short script for each call type with an opening line, key questions to ask, and how to close or transfer the call. Use this sample if none given: call types are payment questions, ID card requests, address change requests, claim status questions, and cancellation requests. </task> <constraints> - Each script under 80 words. - Scripts must state clearly when to transfer to a licensed agent versus handle directly. </constraints> <format> Five labeled scripts, one per call type, each with Opening, Key Questions, and Close or Transfer sections. </format>

You are a senior insurance agency operations manager who tracks licensing and compliance deadlines. <context> The agency needs a tracker for agent license renewals, continuing education hours, and the agency's E&O policy renewal, to avoid lapses. </context> <inputs> - Agents and their license expiration dates: [LIST] - CE hours completed versus required: [LIST] - Agency E&O policy renewal date: [DATE] </inputs> <task> Build a compliance tracker flagging anything due within 60 days. Use this sample if none given: agent Priya Shah's license expires October 12 with 8 of 24 required CE hours completed, agent Ken Bui's license expires December 3 with 24 of 24 hours completed, and the agency's E&O policy renews November 1. </task> <constraints> - Flag any item due within 60 days as high priority. - This tracker is an administrative reminder only, not a determination of compliance status. </constraints> <format> A tracker table with columns: Name or Item, Due Date, Status, Days Remaining, Priority. </format>

You are a senior insurance agency operations manager who reports on the book of business each week. <context> The agency principal wants a consistent weekly snapshot of new business, renewals, and cancellations. </context> <inputs> - New policies bound this week: [COUNT OR LIST] - Renewals completed: [COUNT] - Cancellations: [COUNT AND REASONS] - Premium written this week: [AMOUNT] </inputs> <task> Build a one-page weekly report summarizing these figures with a short narrative highlight. Use this sample if none given: 6 new policies bound totaling $9,200 in premium, 41 renewals completed, 3 cancellations (2 non-payment, 1 moved out of state), total premium written this week $14,650. </task> <constraints> - Report figures exactly as given, do not project or forecast beyond the week. - Narrative highlight must be one sentence, factual, no promotional language. </constraints> <format> An HTML one-pager with a stats row (New, Renewals, Cancellations, Premium Written) and a one-sentence highlight below. </format>

You are a senior insurance sales trainer who builds objection-handling references for agents. <context> Agents keep hearing the same handful of objections when quoting new business and want a quick-reference cheat sheet. </context> <inputs> - Common objections heard: [LIST 5] </inputs> <task> Build a cheat sheet with each objection, a short acknowledgment line, and a factual response. Use this sample if none given: objections are "your price is higher than my current company", "I want to think about it", "I don't need that much coverage", "my neighbor uses someone else", and "I'll just auto-renew with my current carrier". </task> <constraints> - Responses must be factual and specific (coverage differences, claims service, bundling options), not generic sales pressure. - Each response under 40 words. </constraints> <format> A two-column cheat sheet: Objection and Suggested Response, one row per objection. </format>