Healthcare · Warm Call
Warm Call Script for Healthcare: Cashing a Peer Referral with a CMIO in Ninety Seconds
A physician executive at a peer system forwarded your name to a CMIO, and now the CMIO has picked up. That pickup is the entire gift. They can probably name the referrer. They almost certainly cannot name what you sell, and they have four minutes before their 11:00 with the clinical informatics committee prep. Somewhere in the back of their head is a list: the Epic upgrade, the scribe vendor that half the family medicine docs abandoned in month two, the ortho group threatening to go independent, and the after-hours EHR time report that lands in their inbox every Monday with the same four names at the top.
Warmth in healthcare decays faster than anywhere else, because these buyers have sat through more vendor overviews than any other executive population in the economy. Two generic sentences — "so just to give you a bit of background on us" — and you have converted a warm call into a cold call that the CMIO now feels vaguely embarrassed to be on, and they will mention that to the person who referred you. The job on this call is narrow: cash the referral in twenty-five seconds, convert it into one specific and testable reason you are relevant to their medical group rather than the referrer's, ask three questions in their metrics, and leave with a date, a length, and a second name on the invite.
The two-sponsor problem is the thing that makes this industry different. Documentation burden lives with the CMIO. Downcoding and prior-auth denials live with the Director of Revenue Cycle Management. Slot fill and third-next-available live with the VP of Clinical Operations or the Practice Administrator. Whoever answered your call owns half the problem, which means the single most valuable thing you can extract in four minutes — more valuable than a pain, more valuable than a budget signal — is the name of the person who owns the other half.
The warm call script
Say it in your own words. The structure is the part that matters.
- 1
Pre-call: write the provenance line out loud
One sentence, checkable, small. Not "Dr. Alvarez thought you'd be interested in what we do." That's nothing. "Dr. Alvarez mentioned you because [specific, checkable reason]." Good versions: - "She said you'd just taken the CMIO seat after the Sutter Ridge acquisition and inherited two instances of Epic." - "He said you two were comparing after-hours EHR time numbers at the state medical group meeting and yours were the ones that made him wince." - "She pulled down our documentation-burden write-up and said you were the one running the scribe evaluation over there." Also pre-decide three things: 1. **Exactly what the referrer said.** If Dr. Alvarez said "you should call Priya," you say that. Never inflate it to "she said you'd be really interested." Physician executives in the same market talk at CMIO council meetings, and getting caught embellishing costs you two relationships in one move. 2. **Your relevance hypothesis about their shop, not the referrer's.** Epic vs. Cerner/Oracle Health vs. athena vs. eCW changes the entire conversation. New CMIO in seat, a recent acquisition of an independent group, a job posting for four MAs at one clinic, a health system press release about a value-based contract — any of those is a hypothesis. 3. **The 15-second re-brief.** Assume the intro email was skimmed on a phone between clinic sessions and archived.
- 2
The open (target: 25 seconds)
Four beats. Name, referrer, provenance, permission with a time box. "Dr. Reyes — Sam Whitfield, from [Company]. Maria Alvarez suggested I call. She said you'd taken over informatics for the whole medical group after the Sutter Ridge deal and you're now running two Epic builds that don't agree with each other. She may have oversold my usefulness here. Have you got four minutes for me to find out whether that's actually true, or should I come back?" If they say "yes, Maria said you'd call" — that is your entire warmth budget being handed over. Do not spend it on "so how do you know Maria?" Five words and move: "Good, she said she'd flag it. Then I'll be quick."
- 3
If they can't place the referrer
Extremely common. Do not argue them into remembering. "No reason you would — it was a two-line intro on a Friday afternoon. Short version: we work on after-hours documentation time. Maria's group had primary care averaging well over an hour of pajama time a day and a couple of family medicine docs on the way out the door. She thought your situation was similar enough to be worth a phone call. Is it worth four minutes, or not really?" No product name, no category positioning, no "AI-powered." One sentence about the world they live in, then hand them the exit.
- 4
The relevance bridge — the move the call lives or dies on
Referrer's world → the specific difference at *their* shop → a question that hands them control. Inside the first minute. "What Maria was dealing with was a 22-provider primary care footprint, all one Epic instance, and the after-hours EHR time report showing north of ninety minutes a day for the family medicine group. That's her shop. Yours is bigger, you've got a lot more specialty, and from what I can tell you're mid-integration on two builds — so honestly I don't know whether this lands the same way. Where does your after-hours time actually sit right now, and is it primary care or is it the specialists?" Why this works: naming a reason you might be irrelevant is the fastest credibility move available on a warm call, and it disarms the "here comes the pitch" brace that every CMIO holds by default. What kills the call: "Maria was drowning in pajama time, so I imagine you are too." Different panel sizes, different specialty mix, different EHR governance. They hear that you researched the referrer and not them.
- 5
Three questions, in their metrics — maximum four
This is not a discovery meeting. You have four to twelve minutes and no agenda they agreed to. Eleven qualification questions reads as an abuse of the referral. **1. Current state, mechanical.** "When a family medicine doc finishes a 22-patient day, where does the note actually get written — in the room, between patients, or at nine o'clock from the kitchen table? And what's your chart closure rate at 24 hours look like?" **2. Cost or friction, in their numbers.** "Your target for after-hours EHR time — is it the thirty-minute mark? How far off are you, and which service lines are the worst?" Then: "What did provider turnover run last year across the medical group?" **3. Priority test — the question that saves you a wasted follow-up.** "Is that a this-fiscal-year problem with someone's name on it, or is it a known-annoyance-we-live-with problem?" **Optional fourth — the two-sponsor question.** In healthcare this has an unusually high hit rate on a warm call, because you're already a known quantity by association. "Who else in the building cares about note quality? I ask because the CMIO usually owns the burnout half and revenue cycle owns the downcoding and denial half, and I don't want to build a case that only covers one of them." Write their phrasing down verbatim. If they say "it's less the volume of notes, it's the in-basket," that's the call working, and that sentence goes in the follow-up email and the second-meeting agenda.
- 6
Reading the cool-off
Warmth withdraws politely. In healthcare it sounds like this: - Answers shorten. "Yeah. Yeah, that's fair." - They narrate logistics: "Can you send something over and I'll route it to informatics?" - They ask about price or FTE savings before you've established a problem. - They reference the referrer as an exit: "Well, if Maria rates you." Stop and name it: "I'm getting the feeling this isn't the pressing thing on your list this quarter — which is completely fine, Maria was guessing. Is it not the problem, or not the moment?" A clean "not the problem" protects the referral relationship and saves you a quarter of chasing. "Not the moment" is a real answer too — ask what has to happen first, and whether that's the Epic integration cutover or the budget cycle.
- 7
The close: a date, a length, a reason in their words, and a second name
The number one warm-call failure in this industry is a pleasant twelve minutes with a CMIO that ends in "send me a deck for the governance packet." "Then here's what I'd suggest. You said the problem isn't the primary care docs, it's ortho and behavioral health where the note structures are all different and your last vendor had no specialty coverage. Give me thirty minutes and I'll show you exactly what those two specialties look like at [comparable system on the same EHR] — and I'd want your Director of Clinical Informatics on it, because the first question is going to be the SMART on FHIR launch and I'd rather she interrogate that live than read it. Thursday morning or Monday afternoon?" If they genuinely can't commit, take the smaller real commitment with a date on your side, not theirs: "I'll send you two paragraphs and one screenshot of the note output for an ortho follow-up. Tell me Thursday whether it's worth thirty minutes." And while you're there, ask the governance question early — it sets your close date: "When does the EHR governance committee meet, and what do they need in a submission packet?"
- 8
Close the loop with the referrer, same day
Non-negotiable and routinely skipped. "Maria — spoke to Priya Reyes, thanks for that. Turns out her issue is different to yours; primary care is actually in decent shape, it's ortho and behavioral health where the notes are falling apart. Meeting her and her informatics director Thursday. Appreciate the intro." Three jobs: it thanks them, it tells you whether you can use their name again in that market, and it is the only reliable way a referral source produces a second referral. Sources who never hear back stop referring.
How the call actually sounds
Prospect on the left, the rep on the right.
Rep
Dr. Reyes — Sam Whitfield, from Corva. Maria Alvarez suggested I call you. She said you'd picked up informatics for the whole medical group after the Sutter Ridge deal and you're now running two Epic builds that don't talk to each other. She may have oversold my usefulness. Four minutes to find out if that's true, or should I come back?
Buyer
Four minutes. I've got a governance prep at eleven. Maria did email me, I'll be honest, I skimmed it. You're the scribe people?
Rep
Ambient documentation, yes — and the word scribe is probably doing you a disservice given you've been through one. Quick context so I don't waste the four: what Maria was dealing with was a 22-provider primary care footprint, single Epic instance, after-hours EHR time running well over ninety minutes a day in family medicine and two docs already interviewing elsewhere. That's her shop. Yours is bigger and a lot more specialty-heavy, so I genuinely don't know if this lands the same way. Where does your after-hours time sit — is it primary care or the specialists?
Buyer
Primary care we actually cleaned up. We restructured the in-basket pools and we're close to the thirty-minute target for most of them. It's ortho and behavioral health that are ugly. And before you get excited — we ran a scribe vendor two years ago. Half the docs stopped using it inside a month. I'm not doing that to my medical staff again.
Rep
What killed it? Turnaround, note quality, specialty coverage, or was it optional?
Buyer
All four honestly, but mostly it was built for primary care. The ortho guys got a note back that didn't have a proper exam structure and they weren't going to fix it themselves at seven at night. And yes, it was optional, so it just quietly died.
Rep
That's the pattern. Specialty coverage plus optional is a guaranteed month-two collapse. Let me ask you the thing I actually need to know: when an ortho follow-up finishes a clinic day, where does the note get written, and what's chart closure at 24 hours looking like for that group?
Buyer
Kitchen table, mostly. 24-hour closure for ortho is somewhere in the sixties. Behavioral health is worse and their notes are longer. But here's my problem with this whole conversation — Epic's told us they've got ambient coming natively. Why would I put my medical staff through another vendor when it's in the roadmap?
Rep
They will ship it, and it'll probably be fine for the average primary care note. Two honest questions back. First: do you know which of your sites is in the release wave, and when? Second: when it lands, is ortho and behavioral health in the first version or the third?
Buyer
...I don't know either of those, to be fair. Our rep said next year, which in Epic time means somewhere between next year and never for us specifically.
Rep
Right. So the real question isn't Epic versus us, it's what your ortho and behavioral health docs are doing for the next eighteen months while it's in early adopter. And I'd add one more thing, which is that documentation quality isn't only a burnout number for you — if ortho notes are getting written at eleven at night, someone in revenue cycle is seeing downcoded E&M levels and medical necessity denials off the back of it. Who owns that side over there?
Buyer
That's Dale Kwon, our RCM director. And you're not wrong, he's been complaining about the ortho documentation for a year. But look — even if I liked this, anything touching clinical workflow goes to the EHR governance committee, they meet monthly, and my legal team will want a BAA and a full third-party security review before I can even pilot. That's a long runway.
Rep
Understood, and I'd rather start that clock now than after we've had a nice conversation. We sign BAAs as standard, SOC 2 Type II and HITRUST documentation are ready to go, and we've got a completed security questionnaire already submitted at two other Epic systems. Two things I'd want to know: who owns third-party risk review at your shop, and how long did your last clinical vendor take to get through it?
Buyer
Ninety days-ish, and it's our CISO's team. Which is exactly why I'm not signing up for another pilot that dies in month two after all that effort.
Rep
Then let's put the adoption risk on us, not you. We define a utilization threshold up front, measure it weekly, and if active use is below it at day 60 we pull the product out — that's in writing. Here's what I'd suggest: thirty minutes, and I'll show you the actual note output for an ortho follow-up and a 60-minute behavioral health intake at a system on the same Epic version as you. I'd want Dale on it, because the denial and downcoding piece is half your business case and I don't want to build it without him. Thursday morning or Monday afternoon?
Buyer
Thursday's clinic. Monday at two, and bring the specialty examples — if the ortho note looks like the last vendor's, I'll tell you in five minutes and we're done.
Rep
Fair deal. Monday at two, thirty minutes, you, me and Dale. I'll send the ortho and behavioral health samples Friday so you can look before we're on the call, and I'll include the security questionnaire so your CISO's team can start their clock in parallel rather than after. And I'll let Maria know she wasn't wasting your time.
Objections you will hear
What they say, and what you say back.
| Objection | How to answer it |
|---|---|
| “"If it doesn't live inside Epic, my clinicians won't touch it. Nobody's toggling to another window in a 15-minute visit."” | Agree immediately — anything that adds a login is a dead product. Then be specific enough that they can check you: name the mechanism (SMART on FHIR launch, sidebar embed, whatever yours actually is), name the health systems on that EHR where you're live in production, and offer to walk their Director of Clinical Informatics through the build on a technical call rather than debating it with the CMIO. Then flip it: "What's the last third-party tool that actually got adopted inside the chart there, and what made that one stick?" Their answer tells you the real integration bar, which is nearly always cultural rather than technical. |
| “"We'll need a BAA and you'll have to go through a full security review before anything touches PHI."” | Never resist this — it's a qualification signal, not a stall. "Of course. We sign BAAs as standard, here's SOC 2 Type II and our HITRUST status, and here's the completed vendor questionnaire we've already submitted at two other systems on your EHR." Then ask the question that actually moves the deal: "Who owns third-party risk review, and how long did your last clinical vendor take to clear it?" If the answer is ninety days, you now know your close date, and you can run the review in parallel with the pilot conversation instead of after it. |
| “"Our operating margin is under two percent. There's no budget for anything that isn't billing or compliance."” | Stop selling software and start on a P&L line they already own. Two levers: provider retention — one avoided departure in a specialty line often covers a multi-clinic contract once you count recruitment plus 12–18 months of ramp — and throughput. Make them do the arithmetic out loud with their numbers: "How many providers in that service line, and what's your contribution margin per encounter? If a provider recovers 45 minutes a day, what does that look like in visits?" The business case has to be in their handwriting, not yours. And on a warm call, don't finish the maths for them — get the inputs and bring the model to the second meeting. |
| “"We tried a scribe vendor two years ago and half the docs stopped using it after a month."” | Ask what killed it — turnaround time, note quality, specialty coverage, or that it was optional. It's almost always one of those four and the answer is diagnostic. Then reframe adoption as something you own jointly: name a utilization threshold, propose measuring it weekly through the pilot, and offer a clause that says if active use is below X% at day 60, you pull it out. Physicians and the executives who protect them trust a vendor that volunteers an exit far more than one that promises success. |
| “"Anything touching clinical workflow has to go through EHR governance, and they meet monthly."” | Don't route around it — get on the agenda with your sponsor co-presenting. Ask what the committee has approved and rejected in the last two cycles and why, what the submission packet requires, and who the known skeptic is. Then arm your champion with the one-pager and a reference call from a peer system before the meeting. Deals die in governance because the sponsor turned up alone holding a vendor slide deck. |
| “"We'd need patient consent to record, and we're a two-party consent state."” | Have the answer ready before they raise it, because fumbling this one is fatal. Know the standard consent language other systems use, whether it's delivered verbally at rooming or added to the intake packet, and exactly what your product does when a patient declines. Offer to share how two or three comparable systems operationalized it — most treated it as a one-line addition to the existing consent-to-treat and the front desk barely noticed. It's usually a legal reflex rather than a blocker. |
| “"Send me something and I'll route it to informatics."” | That's the polite exit, and on a warm call it feels rude to push — push anyway, but small. "Happy to. Before I do — is it not the problem, or not the moment?" If they engage, close on their words. If they don't, take the micro-commitment with a date on your side: "I'll send two paragraphs and one screenshot of an ortho note. Tell me Thursday whether it's worth thirty minutes with you and your RCM director." A deck sent into a health system inbox with no diarised follow-up is a closed-lost you haven't recorded yet. |
Questions reps ask about this call
- How is a warm call script for healthcare different from a cold call script?
A cold call earns the right to speak in the first ten seconds. A warm call already has it and can lose it just as fast. The difference is where the risk sits: on a warm call your risk is generic. A CMIO who took the call because a peer physician executive vouched for you will sit through about ninety seconds before deciding whether the referrer wasted their time. That means no company overview, no category education, and no transplanting the referrer's pain — "Maria was drowning in pajama time so I imagine you are too" tells a CMIO you researched Maria and not them. Spend the ninety seconds on one checkable reason you're relevant to their specific service-line mix and EHR situation, then ask a question.
- Who should I call first — the CMIO, the VP of Clinical Operations, or the Director of Revenue Cycle Management?
Call whoever the referral actually points at, and then use the call to find the other sponsor. Documentation burden deals in healthcare almost always need two: the CMIO or Chief Medical Officer owns the burnout and after-hours EHR time half, while the Director of Revenue Cycle Management owns the downcoding, HCC recapture and denial half. If the pain is slot fill, third-next-available or no-show rate, your sponsor is the VP of Clinical Operations or the Practice Administrator, and the CMIO is a stakeholder rather than a buyer. The highest-value question you can ask in four warm minutes is "who else in the building cares about this?" — warm calls have an unusually high hit rate on it because you arrive pre-vouched.
- What do I say when the buyer can't remember who referred me?
Assume it from the start — most intro emails are skimmed between clinic sessions and archived. Don't make them work to remember. "No reason you would, it was two lines on a Friday. Short version: we work on after-hours documentation time. Dr. Alvarez's group had family medicine well over an hour a day and two physicians already interviewing. She thought your situation was close enough to be worth a call. Worth four minutes or not really?" Fifteen seconds, no product name, in their language, and it ends by handing them the exit — which is precisely what makes them stay.
- How much discovery should I run on a warm call in healthcare?
Three questions, four at the absolute outside. Full qualification on an unscheduled call reads as an abuse of the referral and gets shut down with "can you just send me a deck." Use one mechanical current-state question ("where does the note actually get written after a 22-patient day?"), one that surfaces their own numbers (after-hours EHR time against the thirty-minute target, chart closure at 24 or 72 hours, provider turnover, denial rate), and one priority test — "is that a this-fiscal-year problem with a name on it, or a live-with-it problem?" That third question saves more wasted follow-up meetings than anything else in the script.
- Should I bring up BAAs, HIPAA and security before the buyer does?
On a warm first call, don't lead with it — but have it fully loaded for the moment it comes up, which is usually within the first five minutes with a CMIO or Director of Clinical Informatics. Treat it as a qualification signal rather than a stall: confirm you sign BAAs as standard, name your SOC 2 Type II and HITRUST status, mention that a completed questionnaire already exists at other systems on their EHR, and then ask who owns third-party risk review and how long the last clinical vendor took. A ninety-day answer isn't bad news; it's your close date, and it tells you to start the review in parallel with the pilot conversation rather than after it.
- How do I close a warm call without a full demo or business case?
Close on a sentence they said, not on your product. Name the specific gap they described — ortho and behavioral health notes, chart closure in the sixties, the scribe vendor that had no specialty coverage — and offer thirty minutes to show that exact thing at a comparable system on their EHR. Then attach a second name: the Director of Clinical Informatics for the SMART on FHIR question, or the RCM director for the denial half of the business case. Date, length, reason in their words, and who else attends. If they genuinely can't commit, take a smaller real commitment with a date on your calendar, not theirs — and message the referrer the same day, or you'll never get a second introduction from them.