Healthcare Renewal Call Script: Saving a Clinical Documentation Account After a Bad Year

1. 1

   Pre-call: the renewal autopsy (do this the day before, not the hour before)

   Pull these six things and read them, don't skim them: 1. Every ticket from the last 12 months — ID, open date, first response time, resolution time. Flag anything over 48 hours to first touch and know your three worst by number, by date, and by what the clinician on the other end was trying to do when it broke. 2. Utilization by department and by pod, month over month. Not "adoption is 41%." You need: "Family medicine is at 88% weekly active across 34 providers. Internal medicine peaked at 61% in May and has drifted to 44%. Ortho, derm and behavioral health were provisioned in June and have never had a session." 3. Their own outcome data, split the same way. After-hours EHR time per provider per day in the pods that adopted versus the ones that didn't. Chart closure rate within 24 hours. If you can't show the audit-log delta for the adopters, you have nothing to rebuild on. 4. CSM and AE turnover on your side. If they've had three account owners in eighteen months, that is your fault and you name it in the first ninety seconds. 5. Every QBR commitment you didn't deliver — the ortho specialty model, the two rescheduled training sessions, the inpatient capture item you said was Q3. 6. Org changes on their side. Did the CMIO who signed still own the budget? Has a new Chief Medical Officer or medical group president come in? Is Revenue Cycle now in the room because denials went the wrong way? Then get internal alignment before you dial. Written confirmation from Support leadership on what actually changed — new tier, named engineer, hard SLA — and from your CS lead on what implementation resource you can commit by name. Do not improvise a remedy on the call. A second broken promise in a health system doesn't just kill the account, it kills you at every system that CMIO ever talks to at their next CHIME event. Decide your floor before you dial: price, term, seat count, and what you will trade for what.

2. 2

   Opening: name it before they have to (first 90 seconds, you go first)

   "Dr. [Name], thank you for the time. I know the agreement ends [date] — I'm not going to talk about the renewal for the first part of this call, because from where I'm sitting this wasn't the year we sold you, and I'd rather we say that out loud than dance around it. Here's what I can see from my side. We went live in March with 34 family medicine and 27 internal medicine providers. Ortho, derm and behavioral health were supposed to onboard in June and never did — you're paying for 140 licenses and 58 are weekly active. Ticket 41-882, the capture dropping on handoff, sat nine days without a first response in June, in the middle of your busiest stretch. Two of your section chiefs escalated to your office rather than to us, which means our escalation path didn't work. And you've had two CSMs in fourteen months. That's on us, not on you. That's what I've got. What am I missing, and what did it actually cost you?" Then stop talking. Do not fill the silence. The meeting is won in the four seconds after that question.

3. 3

   The listening phase: let it be worse than you thought (40-50% of the call)

   No "but." No "to be fair." No defending the incident where their MA never completed training. You may be right and you will lose the renewal being right. Questions to use, in roughly this order: "When it came up at Med Exec — what did the ortho chair actually say, and what happened in the room?" "Who did you have to explain this to? Did this show up in your leadership review or in the CMO's dashboard?" "You said the docs 'gave up on it.' Tell me about that — was it turnaround, note quality, the specialty coverage, or the fact that it was optional?" "During those two weeks in June, what were your providers doing instead?" Follow the emotional word. If they say "we were basically dead in the water for two weeks," you say "tell me about those two weeks" and nothing else. Write it down visibly and read it back: "So: nine-day response on 41-882 during your Q2 surge, the ortho and behavioral health rollout that never happened, the two CSM changes, and you found out about the January degradation from your own informatics analyst rather than from us. Anything else?" Ask "anything else?" twice. The second one is where the real wound comes out.

4. 4

   The apology: once, specific, no hedging

   "The Q2 response times were a failure on our side. We reorganised support in April and your tickets got queued behind enterprise escalations from larger accounts. That's an explanation, not an excuse — you bought a 24-hour first-response SLA and we missed it eleven times between April and July, including on a P1. And the specialty rollout is the bigger one. We onboarded the two service lines that were easiest for us and left the three where your pajama time is worst. Ortho, derm and behavioral health are exactly where your after-hours EHR time is highest and we didn't show up for them." One apology. Do not repeat it later in the call. Repeating it makes it a technique.

5. 5

   Proof of change: show, don't promise

   Only three things carry weight. Use their data, never a company-wide stat. Structural change with a date: "We split the support queue by segment on September 1 and stood up a clinical escalation tier. Since then your median first response is 3.1 hours across eleven tickets. I've got the list — I'll send it with the recap." Something already done, unasked: "I had the team clear the three open tickets in your queue last week. You should have seen those close Thursday, including the one from your Practice Administrator at [clinic] about the roster sync." Evidence from a comparable system, offered as a call not a slide: "[System] is on the same EHR, similar footprint, and they had the same specialty coverage problem we gave you. Their Director of Clinical Informatics ran the second rollout differently and I'd rather she tell you how than me. Want me to set that up this week?" If nothing has genuinely changed, say so and change what you control instead — your own coverage of the account, a named escalation contact with a direct line, an exec sponsor. Do not manufacture progress. They will check, and their informatics analyst is better at checking than you think.

6. 6

   Rebuild on what works: find the person, not the feature

   "You said the one thing your team would miss is the way the notes are landing in family medicine. Let's stay on that for a minute. Who's actually driving that?" "Dr. [Name] built the smart-phrase set and now 40-odd providers are using his templates — is that fair? If we went away on the 30th, whose Monday breaks?" Quantify it in their language, and make them do the arithmetic, not you: "In family medicine your after-hours EHR time went from 94 minutes a provider per day to 41. Your target is under 30, so we're not done — but that's 53 minutes back per doc per day across 34 providers. What's that worth to you against your turnover number? You told me in the QBR you were running around 13% on physicians and APPs." "And what's your chart closure rate within 24 hours looking like in that pod versus the ones that never went live?" The person who built the workflow is your remaining champion and was almost certainly not invited to this call. Get their name and get them on the next one.

7. 7

   Handling the competitor: surface it yourself

   "I'd assume you've been talking to [Competitor] — I'd be surprised if you hadn't. What did you like about it?" Listen properly. Never disparage. Then find out how far it's gone: "Have they scoped the migration? Is there pricing in writing, or was it a lunch and a demo?" "Have they been through your third-party risk review yet — BAA, SOC 2, HITRUST? How long did we take when we came through, and who owns that review now?" "Would this need to go back to the EHR governance committee, or does it inherit our approval?" Then reframe from price to total switching cost, plainly and without drama: "Here's the honest comparison. Their number is lower. What it doesn't include is: re-running the security review and the BAA, re-presenting to governance — which meets monthly, so that's a two-cycle minimum — re-doing the consent language at rooming across every front desk, retraining the 58 providers who did adopt, and six months where you have no baseline on after-hours time because the audit-log comparison resets. And the risk that you inherit their version of the support problem you just had with us, except without fourteen months of goodwill and a CSM who knows which of your section chiefs to call first. I'm not asking you to weigh that today. I'm asking you to price it before you decide."

8. 8

   The 90-day plan: build it live, four fields per line

   Every line: what, who by name on both sides, by when, and what 'done' looks like. Build it on the call in their words. "Let me put this on the screen and you correct me as I go. One. Specialty rollout. [Named implementation lead] runs onboarding for the 31 ortho, derm and behavioral health providers, sessions week of the 14th and the 21st. Done looks like 22 of 31 weekly active by day 60. On your side I need [VP Clinical Operations] to make the sessions protected time, not lunch-and-learns — the last rollout failed partly because it was optional. Two. Support. Named escalation contact, direct mobile, four-hour SLA on P1, effective at signature. I'll put the SLA credit language in the contract so you can hold us to it. Three. Measurement. Monthly report showing after-hours EHR time per provider per day and 24-hour chart closure rate, split by pod, sent to you and to [CMO] whether it's good or bad. First one dated the 30th. Four. Governance. You told me the committee wants a utilization report at the 90-day mark. [Your named CSM] builds the packet, your team submits it, and I'll join if it helps or stay away if it doesn't. Five — and I want this in writing too. Inpatient capture is not on the roadmap before Q4. I'm not going to pretend otherwise, and I'd rather you plan around that than be told again in March. What's missing, and what does your side need to own?" Then tie a commercial consequence to it: a break clause at day 120 if you're below the utilization threshold, or milestone-linked billing. Signing an SLA credit into the paper is worth more than any discount, because it proves you expect to be held to it.

9. 9

   Only now: the commercial conversation

   Earn the transition explicitly: "If we can agree that plan is real, can I walk you through what a renewal would look like?" Lead with structure before number: "You're paying for 140 licenses and using 58. I'm not going to discount 140 licenses to make that feel better. I'd rather right-size you to 95 — the 58 active plus the 31 in the specialty rollout, plus a small buffer — with a step-up rate that only triggers when the new pods actually hit utilization. That kills the shelfware line permanently and it means you're paying for what your providers use." On the bad year, use the honest instrument: "For the Q2 SLA misses, service credits for April through July. That's specific, it's finite, and it's tied to what we got wrong. What I'm not going to do is cut your rate as an apology, because that turns a service failure into a pricing dispute and it tells you the original number was never real." Any discount is traded, never given: a case study, a multi-year, a reference call for another system on the same EHR, an earlier signature, or an exec sponsor meeting.

10. 10

    Multi-threading and close: six weeks is tight

    Before you hang up, get all four of these: "Walk me through what happens between now and signature. Does this go back through the EHR governance committee or does the existing approval carry? Does supply chain need to re-bid it? Does Legal need to touch the BAA if we amend the SLA?" "Who signs — you, or does it go up to [CMO / medical group president]? And is Revenue Cycle a stakeholder now that we're talking about downcoding and denial rates?" "I'd like to get you, [VP Clinical Ops], and my VP of Customer Success in a room for a 30-minute plan review. Exec to exec, so you're not the only one carrying this internally. Does the 22nd or the 24th work?" Then the temperature check, and take the honest answer over the polite one: "On a scale where one is you've already decided to leave — where are we right now, and what moves it?" Within 24 hours, send four things: the written 90-day plan with names and dates, the ticket data you cited, the reference intro, and a one-page summary of what went wrong in their words. That last document does more work than any proposal you'll ever write.

1. Rep

   Dr. Reyes, thanks for the half hour. I know the agreement ends April 30 — I'm not going to talk about renewal for the first part of this. From where I sit, this wasn't the year we sold you. We went live with 34 family medicine and 27 internal medicine providers in March. Ortho, derm and behavioral health were meant to onboard in June and never did, so you're paying for 140 licenses and 58 are weekly active. Ticket 41-882 sat nine days without a first response in June. And you've had two CSMs in fourteen months, which is on us, not on you. That's what I can see. What am I missing, and what did it cost you?

2. Buyer

   What it cost me is that I stood up at Med Exec in September and defended this. And then Dr. Kowalczyk from ortho read out a note where the ambient capture put the wrong laterality in the HPI — left knee, right knee — and the room went silent. I don't care about your ticket numbers. That's the meeting I have to walk back into if I renew you.

3. Rep

   Tell me about that meeting. What happened after he read it out?

4. Buyer

   Our CMO asked whether we'd validated it in surgical specialties before we bought it. I said we'd validated in primary care and the specialty models were coming in Q2. He asked me what month it was. It was September. So now I'm the informatics person who bought a tool the surgeons don't trust, and every future clinical tool I bring to that committee starts twenty points down.

5. Rep

   That's the real damage and I'm not going to argue with any of it. The specialty rollout is the failure here — bigger than the ticket response times. We onboarded the two service lines that were easiest for us and left the three where your after-hours EHR time is worst. And we let you carry that in a room we weren't in. What else? Anything I haven't named?

6. Buyer

   The June outage. My clinical informatics director found out from a front desk supervisor in Bellview, not from you. We had docs re-dictating notes at 8pm and nobody could tell them when it would be back. Look, I'll be straight with you — I've got a quote from [Competitor] that's 28% under yours, they say they've got ortho and behavioral health models in production today, and my CFO has seen the number. Our operating margin is 1.8%. I don't have room to be sentimental about this.

7. Rep

   Understood, and I'd have taken that call too. Before we get to the number — what did you like about them? Genuinely. And how far has it gone: is that pricing in writing, have they scoped the migration, have they been through your third-party risk review?

8. Buyer

   Pricing in writing, demo with three of the ortho attendings, they liked it. Security review hasn't started. And honestly, that's the part that makes me tired — the BAA took ninety days with you people, and re-presenting to the EHR governance committee is two monthly cycles minimum. But cheaper is cheaper.

9. Rep

   So the switching cost is ninety days of security review, two governance cycles, re-doing the consent language at rooming across every front desk, retraining the 58 providers who did adopt, and a reporting gap where you lose your after-hours baseline. Say that's four to six months. What happens to your primary care pods during those months? Because right now in family medicine you're at 41 minutes of after-hours EHR time per provider per day, down from 94. Your target's under 30. In the pods that never went live, where is it?

10. Buyer

    Ninety-something. Some of the behavioral health people are worse. I'm not disputing that the family medicine numbers are good — Dr. Okafor built a whole smart-phrase set on top of it and his group won't shut up about it. That's the only reason this meeting is happening instead of a termination email.

11. Rep

    Then let's build around Okafor and around Kowalczyk, and let me tell you what I can and can't commit to. Ortho and derm specialty models are in production now — I'll get you a validation set from a comparable group on your EHR and I'll have their Director of Clinical Informatics call you directly, so it's not me saying it. Inpatient capture is not before Q4; I'm not going to pretend otherwise and I'll put that in writing. And I'd right-size you from 140 licenses to 95 rather than discount shelfware, with service credits for the April-through-July SLA misses. What I won't do is cut the rate as an apology, because that turns this into a pricing conversation and it isn't one.

12. Buyer

    You're still asking me to go back to that committee. What happens if the surgeons try it again and it's still wrong? I've got one shot at this politically.

13. Rep

    Then don't take the shot yet. Two-step it. We run a 45-day validated pilot with six ortho providers — Kowalczyk if he'll do it, because a converted skeptic is worth ten volunteers — measured on note accuracy and 24-hour chart closure, not on adoption. You take results to governance, not a promise. And I'll write a break clause at day 120: if we're not at 22 of 31 specialty providers weekly active, you exit without penalty. Would you rather have a discount, or a contract that lets you walk if we fail again?

14. Buyer

    The break clause is more interesting than the discount, I'll give you that. But my CFO is going to ask why we're paying more than the other quote for a vendor that missed its SLA eleven times.

15. Rep

    Then let's get him in the room and I'll answer it directly, with my VP of Customer Success there so it's not just the sales guy apologising. Thirty minutes, the 22nd or the 24th, and I'll bring the ticket log, the pod-level after-hours data, and the credit schedule. On a scale where one is you've already decided to leave — where are we right now, and what moves it?

16. Buyer

    Four. Get me the ortho validation data and a reference I can call by Friday, and get the break clause in front of Legal. If Kowalczyk comes out of the pilot neutral, I'll take it to governance. If he comes out hostile, we're done and I'll tell you straight.

How is a healthcare renewal call script different from a standard SaaS renewal?

Two differences drive everything. First, the person on the call almost certainly defended you in a clinical governance or Med Exec meeting, and if the tool underperformed they took political damage you didn't see. You have to ask about that room directly — "who did you have to explain this to?" — because the operational complaint is rarely the real wound. Second, switching costs in healthcare are structural, not emotional: a new vendor means a new BAA, a fresh third-party security review that can run 90 days, two monthly cycles of EHR governance, new consent language at rooming if you're in a two-party-consent state, and retraining every provider who did adopt. Price that out loud rather than arguing about license cost.

What data should I pull before a clinical software save call?

Ticket-level detail with IDs, open dates and first-response times — know your three worst by number. Utilization split by department and by pod, not a single blended adoption percentage. Their outcome metrics for the pods that did adopt versus those that didn't: after-hours EHR time per provider per day against their under-30-minute target, chart closure rate within 24 or 72 hours, and if you can get it, wRVUs per FTE or visits per provider per day. Also pull your own CSM and AE turnover, every QBR commitment you missed, and any org changes on their side — a new CMO or medical group president changes who actually signs.

Should I discount to save a healthcare renewal after a bad service year?

No. A price cut is not an apology and a CMIO will read it as one — it reframes a clinical service failure as a pricing dispute and permanently resets your floor. The honest instruments are service credits for the specific months you missed SLA, right-sizing licenses to actual weekly active users rather than discounting shelfware, and a break clause tied to a utilization threshold. Given operating margins that often sit between 1 and 3%, a CFO will respect a credit schedule tied to documented SLA misses far more than a round-number discount that arrives six weeks before the contract ends.

Who else needs to be in the room besides the CMIO?

The CMIO or Director of Clinical Informatics usually owns the clinical case but rarely owns the money alone. Bring in the VP of Clinical Operations for adoption commitments and protected training time, the Director of Revenue Cycle Management if documentation quality is affecting denial rates or downcoding, and the CFO or CMO if the competitor's quote is already circulating. Also identify your power user — the physician who built the workflow everyone else copied. They're your remaining champion and they were almost certainly not invited to the renewal meeting. Ask "if we went away, whose Monday breaks?" and get that name.

How do I handle it when the EHR vendor is promising the same capability natively?

Concede the point and change the timeframe. Native capability will arrive and it'll handle the average primary care note fine — the live question is what their ortho, derm and behavioral health providers do for the next eighteen months while it's in early adopter release. Ask which of their sites is in that wave, on what version, and whether their informatics analyst has confirmed it or whether it's a roadmap slide. Then offer a shorter or quarterly-reviewed term so the timing risk sits on your side of the table rather than theirs.

What goes in the 90-day plan, and what happens if I can't deliver something they want?

Four fields on every line: what, who by name on both sides, by when, and what "done" looks like — for example, "22 of 31 specialty providers weekly active by day 60," not "improve adoption." Include measurement they'll actually see: a monthly pod-level report on after-hours EHR time and 24-hour chart closure sent to them and their CMO whether it's good or bad. And write down the thing you can't do. If inpatient capture isn't shipping before Q4, say so in the document. A CMIO who has been burned by a scribe vendor and an EHR conversion will trust the vendor who names a limitation far more than the one who promises everything and misses one thing in March.

• All Healthcare playbooksEvery call type for Healthcare, in one place.

Other Healthcare calls

• Cold CallHealthcare Cold Call Script: Getting a CMIO or VP of Clinical Operations to Give You 20 Minutes
• Demo CallHealthcare Product Demo Script: Running a Clinical Demo for a CMIO Who's Already Killed Two Vendors
• Discovery CallDiscovery Call Questions for Healthcare: A 25-Minute Playbook for CMIO and Clinical Ops Calls
• Manager Coaching CallSales Coaching Roleplay for Healthcare Teams: The 1:1 After Two Missed Quarters
• Pricing Negotiation CallHealthcare Pricing Negotiation Script: Holding Your Number After the CMIO Has Already Chosen You
• Upsell CallUpsell Script for Healthcare Customers: Expanding an Ambient Documentation Deal Without Burning the Account
• Warm CallWarm Call Script for Healthcare: Cashing a Peer Referral with a CMIO in Ninety Seconds

The same call in a neighbouring market

• Renewal Call for SaaSThe SaaS Renewal Call Script for a Save Call You're Six Weeks From Losing
• Renewal Call for InsuranceInsurance Renewal Call Script: Saving a Claims Platform Account at a Carrier That's Already Halfway Out

Related reading

• Renewal Call vs Upsell Call: Running Both at Once Is How You Lose BothRenewals restore confidence, upsells extend it. Run them on the same call and the customer hears you asking for more money for the thing that already disappointed them.
• The 90-Day Renewal Health Check: Catching the Churn Before It's a Save CallThe renewal risk checklist I run ninety days out on every account, the five red flags it catches, and the specific call to make the week you find each one.