Insurance · Cold Call
The Insurance Cold Call Script That Keeps a Claims Leader on the Phone
You dialled a VP of Claims Operations at a regional mutual at 11:40 on a Tuesday. She's got a queue report open, a producer has already called her once this morning about a commercial file, and the CAT desk is watching a hail line move across the state. She picked up because she thought it was the IA vendor calling back. You have about eight seconds before she decides whether you're a human being or an autodialer, and about forty-five before she decides whether you understand what she actually does all day.
This is not a discovery call. You are not going to qualify her, walk her current-state workflow, or ask what her top three priorities are. The only job is to say something so specific about days-to-close, ALAE, SIU referral volume, or what happens to her complaint count six weeks after a storm that she thinks how does a stranger know that about my shop. Everything else — the demo, the actuarial scrutiny, the integration surface against a 20-year-old policy admin system — belongs to a meeting you haven't earned yet.
What follows is a working insurance cold call script for selling into claims and underwriting leadership at P&C carriers: Chief Claims Officers, SVP Claims, VPs of Claims Operations, Directors of Claims Transformation, SIU Directors, and the COO who owns the combined ratio they all roll up to. Use the language as written, out loud, and expect to be interrupted inside the first two sentences. The dialogue at the bottom shows what that actually sounds like.
The cold call script
Say it in your own words. The structure is the part that matters.
- 1
90-Second Prep: Answer These Out Loud Before You Dial
Who is this person? Not "claims leader." Exact title and tenure: "Denise Alvarado, SVP Claims, in seat fourteen months, came over from a national carrier, owns personal auto and homeowners plus the CAT desk." A Director of Claims Transformation hired six months ago is a different call from an SVP Claims who's been there nineteen years and built the current process herself. What's the trigger? A rate filing that just got approved or kicked back. A hail or named-storm event in their footprint in the last ninety days. A core migration announcement. Three adjuster or SIU postings open. A new Chief Claims Officer. If there's no trigger, the segment is the trigger: "every regional carrier we work with writing auto and property in the Midwest is dealing with this." What's the ONE problem? Write it on a sticky note. Cycle time, or leakage, or SIU referral rate, or CAT surge staffing. Not all four. Pick the one their title owns. What's the ask? "Twenty minutes, Tuesday 8:15 or Thursday after 4." Specific length, two specific slots. Have the follow-up email drafted in a window before you dial, so you can send the invite while she's still on the line.
- 2
The Opener (0–8 seconds)
"Hi Denise — Marcus at Verity. We haven't spoken before, this is a cold call. Can I have thirty seconds to tell you why I rang, and then you can tell me to get lost?" [PAUSE. Two full seconds. Do not fill it.] Tonality: slower than feels natural. "Can I have thirty seconds" ends *down*, not up. If she answers flat and clipped, come in flat and clipped — match her within one notch. Do not be bright. Nobody in claims is bright at 11:40 on a Tuesday. Pattern-interrupt variant: "Denise — Marcus, Verity. You don't know me. Bad time?" Do not say: "How are you today," "Did I catch you at a bad time," "I'll be brief," or "the reason for my call is to introduce myself and our platform."
- 3
The Reason — Cycle Time Version (VP Claims Ops, SVP Claims, Chief Claims Officer)
"We work with about nine regional carriers writing personal auto and homeowners. The thing that keeps coming up with VPs of Claims Operations is non-cat property files that should close in twelve days sitting at twenty-six, twenty-eight — and it's almost never the adjuster. It's one file waiting on a photo estimate, an appraiser assignment and a coverage question in three separate queues, and nobody owns the waiting. Then six weeks later it shows up as complaint volume, and it shows up again at the agent council. Is that anywhere near your world on property, or have you got that one solved?" The out at the end — "or have you got that one solved" — is what makes the honest answer safe. Keep it.
- 4
The Reason — Leakage / ALAE Version (COO, Chief Claims Officer, Director of Claims Transformation)
"We work with a handful of carriers your size on the loss ratio side. What the COOs tell us is that they can quote their combined ratio to the decimal, and they cannot put a defensible number on leakage — the range they'll admit to is two to five points of paid losses. Soft-tissue BI settled above reserve to close before month-end, subro opportunities that never got flagged, salvage left on the table. And every point of it has to come back through a rate filing. Is leakage something your chief actuary has a number for, or is it still a range?" Use this one when the title owns the combined ratio rather than the queue.
- 5
The Reason — Fraud Version (SIU Director, Director of Special Investigations)
"We work with SIU Directors at about a dozen carriers. The pattern is always the same — the referral rate sits at one, maybe two percent, the file gets to SIU after the rental's been paid and the medical bills are in, and now the adjuster has to go accuse someone they've spent three weeks building rapport with. And most of them have already been through one analytics tool that buried them in false positives and got switched off. Is that roughly your history with it, or did yours land better than most?" Naming the failed prior vendor *before they do* is the single highest-value sentence you can say to an SIU Director.
- 6
Two Questions Maximum — Then Close
You are not running discovery. Narrow and factual only. Pick two: "Today, is somebody manually chasing those queues, or is something routing it?" "Roughly what's your average days from FNOL to final payment on property right now?" "Is that on a roadmap for this year, or is it in the living-with-it pile?" "How many alerts a week can your SIU unit actually work? Two? Twenty?" "When you deployed IAs after the last hail event, what did cycle time do?" Do NOT ask: what are your priorities this year, walk me through your process, what's your budget, who else is involved. You haven't earned any of it and you'll burn the reason to hold the next meeting. Listen for the admission — "yeah, it's a mess," "we've been meaning to look at that," "the board asked about that number last quarter." The second you hear it, stop asking and close.
- 7
The Ask
"Here's what I'd suggest. Twenty minutes, not a demo — no deck. I'll bring the model empty and you put your own numbers in it: your paid losses, your ALAE ratio, whatever leakage number your actuary will stand behind. If the number's not big enough to be interesting, say so on the call and I'll leave you alone. I've got Tuesday at 8:15, before your queue meeting, or Thursday after four. Which is less bad?" Then: "Sending the invite now while we're on — can you tell me it landed?" Book it verbally and calendar it later and you will get a no-show. Send it on the line.
- 8
Gatekeeper / "What is this regarding?"
Short, calm, specific, no cleverness: "It's about their property cycle time — days from FNOL to close. Marcus at Verity. She won't know me." Or for SIU: "It's about SIU referral volume. Marcus at Verity, he won't know my name." Never claim a prior relationship, never say "it's personal," never say "he's expecting my call." Claims assistants have heard all three this week.
- 9
Voicemail (Under 20 Seconds, No Ask)
"Denise, Marcus at Verity — you don't know me. Calling about FNOL-to-close on non-cat property; it's the thing every regional carrier your size seems to be fighting right now. I'll try you again Thursday morning. 555-0148." The voicemail's job is name recognition for attempt two and the email that follows it. Not a callback. No "give me a shout back at your convenience."
- 10
The Soft No and the Recycle
"No problem, I'll let you go. Last thing — is this a timing thing or a not-a-priority thing?" [Listen.] "Got it. When does your planning cycle close for next year?" … "And is the pressure this year coming from severity, or retention, or is it expense side?" "Perfect. I'll come back to you in August, before that closes. Sending one email now so my name's in your inbox." A call that produces a dated callback and a named pressure is not a failure. A call that produces "send me something" and nothing else is.
- 11
Immediately After
Email inside five minutes. Subject line references the call, not your company: "Our call just now — 26 days on property." Log her exact words. If she said "we're bleeding on subro," that phrase goes in the email and it opens the discovery call. Do not paraphrase it into "recovery optimisation." Log the disposition honestly. "Interested" is not a disposition. "Booked Thursday 7:45, mid-Duck Creek migration, burned by prior fraud vendor, mutual — expense ratio target 28" is.
How the call actually sounds
Prospect on the left, the rep on the right.
Rep
Hi Denise — Marcus at Verity. We haven't spoken before, this is a cold call. Can I have thirty seconds to tell you why I rang, and then you can tell me to get lost?
Buyer
I've got about that. I'm walking into a claims review in four minutes.
Rep
Then I'll be quick. We work with about nine regional carriers writing personal auto and homeowners. The thing SVPs of Claims keep raising is non-cat property files that should close in twelve days sitting at twenty-six, twenty-eight — and it's not the adjusters. It's one file waiting on a photo estimate, an appraiser assignment and a coverage question in three separate queues, and nobody owns the wait. Is that anywhere near your world, or have you got it solved?
Buyer
Look, I'll save you some time. We're eighteen months into a core migration off an AS/400 that half my staff learned on. There is no IT bandwidth in this building until 2027. Zero.
Rep
That's fair, and honestly that's why I called rather than emailed. Quick question — what's your days-to-close done since the migration kicked off? Every carrier I've talked to mid-migration says it went the wrong direction, and the ones who don't say it usually haven't looked.
Buyer
…It's up. Property's up about four days. But that's a project cost, everybody knows that, it comes back at go-live.
Rep
Sure. And in the meantime the DOI complaint count doesn't wait for go-live and neither do your agents. What I'd want to show you sits outside the migration path entirely — read-only against the claim file, flat file or queue, nothing writing back into the core, no schema change, nothing that touches check issuance or your statutory extracts. Your integration team never gets pulled in.
Buyer
I've heard that sentence before. Two years ago we bought fraud analytics and the vendor swore the same thing. My SIU Director got four hundred alerts a month, precision was garbage, and we turned it off inside two quarters. So you'll understand the reception.
Rep
I do. Do you remember what threshold they set it at, and whether your SIU Director set it or the vendor did?
Buyer
The vendor did. They tuned for recall because they wanted the case study. We had six investigators.
Rep
Right — that's not a model failure, that's a capacity mismatch, and it's the most common way these die. The way we'd do it is inverted: score last year's closed files, the ones where you already know the outcome, and see whether it would have flagged the SIU-confirmed ones and how many clean files it dragged along with them. Your SIU Director sets the alert volume he can actually work, and we size to that, not to what the model spits out.
Buyer
Even if that were true, we're a mutual. I don't have a technology line the way a stock carrier does. Surplus is policyholder money and my board asks about the expense ratio, not about AI.
Rep
Understood — then this isn't a tech spend conversation, it's a combined ratio conversation. Slow files cost you in complaint handling on the expense side and in retention on the top line, and leakage comes straight out of the same surplus. What's the board's expense ratio target for next year?
Buyer
Twenty-eight, and we're not there. Look — send me something and I'll get it in front of our innovation committee.
Rep
Happy to. Though I'll be honest, the innovation committee is where claims vendors go to quietly die, and you know that better than I do. Before I send anything — is cycle time actually the pressure this year, or is it coming from somewhere else? Severity? Retention?
Buyer
It's retention. Two of our largest independent agencies raised claims service at the carrier council in the spring. That's the conversation I keep having.
Rep
Then that's the meeting. Twenty minutes, not a demo, no deck. I'll bring the model empty and you fill it with your paid losses, your ALAE ratio and whatever leakage range your actuary will stand behind — and specifically we'll look at what those two agencies' books look like on days-to-close versus the rest. If the number's not worth a second conversation you tell me on the call. Tuesday at 8:15 before your queue meeting, or Thursday after four?
Buyer
Thursday. Late. And bring the SIU piece too, because he'll be in the room and he's going to be hostile.
Rep
Good, I'd rather have him hostile in the room than polite on email. Sending the invite now — 4:15 Thursday, twenty minutes, you and your SIU Director. Can you tell me it landed?
Objections you will hear
What they say, and what you say back.
| Objection | How to answer it |
|---|---|
| “We run on a 20-year-old core. Integrations die there.” | "You're right, and you've probably got a scar from it. Can I ask what actually broke last time? Nine times out of ten a vendor tried to write back into the PAS. What I'd be proposing is read-only against the claim file — flat file or message queue, no schema change, nothing that touches check issuance or your statutory extracts. And before any production connection at all, one line of business, historical closed claims, scored against outcomes you already know." |
| “Every dollar here goes through actuarial scrutiny. The ROI had better be bulletproof.” | "Good — I'd rather it did. Which is why I'm not bringing a calculator with my assumptions baked in. I'll bring it empty and you put in your paid losses, your ALAE ratio and your leakage estimate. And ask yourself which number your chief actuary would actually book: cycle time is hard to put in a reserve review, but a drop in ALAE per claim or a documented subro recovery lands. We can run the pilot as a back-test on closed files so the savings are calculated against actual settlements, not projections." |
| “We tried a fraud analytics vendor. SIU drowned in false positives and we shut it off.” | "That's the most common way these fail, and it's almost always threshold and workflow rather than the model. What was the precision, and who set the referral threshold — you or the vendor? Here's the inversion I'd suggest: don't score new claims. Score last year's SIU-confirmed files and see whether it would have caught them, and count how many clean files came along for the ride. Your SIU Director sets the weekly alert volume his unit can actually work and we size to that." |
| “We're mid-migration to a new policy admin platform. No IT bandwidth until 2027.” | "That's a reason to talk now, not later. Those projects run twenty-four to thirty-six months and claims service almost always degrades while they're running — what's your days-to-close done since it started? Anything I'd propose sits outside the migration path so it isn't competing for the same integration team, and the pilot gets owned by the claims org, not IT. If it genuinely needs IT, I'll tell you and ask to be on the roadmap conversation for the quarter after go-live." |
| “We can't have a black box making claim decisions. We'd get destroyed in a market conduct exam.” | "Agreed, and you should hold that line. The model recommends, the adjuster decides, and every recommendation drops a reason code into the file notes. If an examiner pulls a file they see the score, the reason, the adjuster's action and the timestamp. It doesn't touch coverage determination — routing and prioritisation only. Do your compliance and legal teams already have a model governance standard? If so, send it and I'll answer against yours rather than against a generic AI objection." |
| “We're a mutual. Surplus is policyholder money — we don't have a tech budget line.” | "Then let's not talk about it as tech spend. Expense ratio and loss ratio come out of the same surplus, and slow claims hit you on both — complaint handling on one side, agent defection and rate adequacy on the other. When does your planning cycle close, and what's the board's expense ratio target for next year? I'd rather size a first phase that fits under whatever threshold doesn't need a board vote than bring you something that needs one." |
| “Send me something and I'll route it to our innovation team.” | "Happy to — though we both know the innovation committee is where claims vendors go to die. Before I send it: is cycle time actually a priority for you this year, or is the pressure coming from somewhere else — severity, retention, the CAT season staffing model? If you name it, I'll book time with you and whoever owns that number. If nothing's pressing, tell me and I'll stop calling." |
| “I'm not interested.” | "Totally fair — you don't know what I do yet. If I'm wrong I'll hang up: is FNOL-to-close on property something your team's actively fighting, or genuinely not a thing at your shop right now?" Once. Never re-run the same objection twice; you'll turn a neutral prospect hostile. |
Questions reps ask about this call
- What should an insurance cold call script open with when calling a Chief Claims Officer or VP of Claims Operations?
Your name, an admission that it's a cold call, a request for thirty seconds, and then a two-second pause. Nothing about your company, your funding, or your platform. Claims leaders field vendor calls constantly and the fastest way to get hung up on is to sound like the last twelve. Naming it as a cold call collapses the 'who is this and how do they have my number' loop and lets them start listening instead of placing you. Then lead with a problem — days-to-close, ALAE, SIU referral rate — not a value proposition.
- Which metrics should actually appear in the script?
Use the ones your buyer's title owns. For an SVP Claims or VP of Claims Operations: average cycle time from FNOL to final payment, by line, and DOI complaint count. For a COO or Chief Claims Officer: combined ratio, loss ratio versus expense ratio, and claims leakage as a percentage of paid losses. For an SIU Director: referral rate and fraud dollars recovered or denied. For a Director of Claims Transformation: ALAE per claim and subrogation recovery rate. Say the number out loud as part of a problem, not as a claim about the market — 'files that should close in twelve days sitting at twenty-six' works; a stat you can't source doesn't.
- How do I handle 'we're mid-migration off our legacy core, there's no bandwidth'?
Don't retreat. Core migrations run two to three years and claims service usually degrades while they're live — so ask what their days-to-close has done since the project started. Most haven't looked, and asking makes them look. Then take the integration objection off the table specifically: read-only against the claim file, message queue or flat file, no schema change, nothing touching check issuance or statutory extracts, pilot owned by the claims org rather than IT. If it truly does need IT, say so and ask to be on the roadmap conversation for the quarter after go-live.
- Is a mutual carrier a different cold call than a stock carrier?
Yes, and the difference shows up in the ask, not the opener. Mutuals will tell you surplus is policyholder money and there's no technology line. Reframe it as a combined ratio conversation — expense ratio and loss ratio draw on the same surplus, and slow claims cost them in complaint handling, agent defection and rate adequacy. Then find out when the planning cycle closes and what the board's expense ratio target is, and size a first phase that stays under the threshold requiring board approval.
- What counts as a successful insurance cold call if they won't book?
A dated reason to call back plus one named pressure. Ask directly: 'Is this a timing thing or a not-a-priority thing?' then 'When does the planning cycle close?' and 'Is the pressure this year severity, retention, or expense?' If you walk away knowing their renewal season, their board's expense ratio target, and the fact that two agencies raised claims service at the carrier council, that's pipeline intelligence. 'Send me an email' with nothing attached to it is a polite hang-up, not a win.
- How do I practise this without burning real carrier prospects?
Run it out loud against a roleplay partner who plays the difficult version: the SVP Claims who interrupts at second nine with the core migration, the SIU Director who names the fraud vendor they shut off two years ago, the COO who wants the number their chief actuary would sign. Drill the pause after the permission ask, drill the downward inflection on 'twenty minutes,' and drill answering the integration objection in under twenty seconds. The words are the easy part; staying slow and flat when someone pushes back is what you actually have to rehearse.