Pre-conversation checklist, script, and post-conversation checklist. Use this any time you have to tell a customer something they don't want to hear, an outage, a delay, a bug, a price or contract change, a mistake your team made. The specifics change, the discipline doesn't.
What this is for
The customer forgives problems far more often than they forgive how the problem was handled.
Before you reach out
☐ You have the facts straight internally, before you talk to the customer
What happened, who's affected, and how badly. Don't call with half the picture, that gets corrected in real time in front of the customer.
☐ You have a next step, even if you don't have a full fix
Never deliver bad news with nothing after it. "Here's what we're doing right now" is the minimum bar.
☐ The right internal people are looped in before the customer is
Support lead, the engineer or team closest to the issue, and anyone whose name you might commit to a timeline.
☐ Legal or compliance is looped in if this touches regulated data or a contractual commitment
If this touches PHI, uptime SLAs, or a signed contract term, that needs a check before the customer hears anything.
☐ You know exactly who to tell on the customer side
If there are multiple stakeholders, decide now who hears it first and who else needs it same day.
☐ You've chosen the channel
Live, by phone or video, for anything serious. Follow up in writing after. Email alone is for smaller, lower-stakes news.
☐ You're reaching out now, not waiting for a cleaner answer
The delay causes more damage than the news itself. If you know today, they hear it today.
☐ You've thought through the two or three questions they're most likely to ask
So you're not visibly thinking for the first time on the call.
The script
State it plainly. Don't bury it in a paragraph of context first.
1. Say it directly
"I'm calling with some news you're not going to love, so I want to get right to it. [The specific thing that happened.]"
Why: Burying bad news in a long setup reads as avoidance, and makes the moment worse, not softer.
Why: Burying bad news in a long setup reads as avoidance, and makes the moment worse, not softer.
2. Own it, without over-explaining the chain of blame
"This is on us. Here's what happened, in plain terms."
Why: Customers forgive mistakes. They don't forgive being handed excuses.
Tip: Don't name a specific internal team, vendor, or person as the cause, even if it's accurate. "This is on us" as a company is the right altitude.
Why: Customers forgive mistakes. They don't forgive being handed excuses.
Tip: Don't name a specific internal team, vendor, or person as the cause, even if it's accurate. "This is on us" as a company is the right altitude.
3. Give the plan
"Here's what we're doing right now, and here's what happens next, by when."
Why: Bad news without a next step leaves the customer holding all the anxiety with nowhere to put it.
Why: Bad news without a next step leaves the customer holding all the anxiety with nowhere to put it.
4. Make space for their reaction
"I want to hear how this is affecting you on your end, so I understand the full impact."
Why: This isn't rhetorical. What they tell you here often changes what the right resolution actually is.
Why: This isn't rhetorical. What they tell you here often changes what the right resolution actually is.
5. Confirm the next touchpoint
"You'll hear from me by [specific date/time], whether or not it's fully resolved by then."
Why: A specific promise to check back in, even with no news, prevents the silence that turns frustration into distrust.
Why: A specific promise to check back in, even with no news, prevents the silence that turns frustration into distrust.
What to say, what never to say
| Say this | Never say this |
|---|---|
| "Here's exactly what happened and here's what we're doing about it." | "It's out of our hands," or blaming a vendor, another team, or the customer. |
| "I don't have that answer yet. I'll have it for you by [specific time]." | Guessing at a cause, a fix date, or a resolution you're not certain of. |
| Specific, factual language about impact and scope. | Euphemisms or soft language that hides how serious it actually is. |
| "I understand this is affecting [specific thing they care about], and I'm not going to pretend it isn't." | "It's not that big of a deal," or any version of minimizing their experience. |
| "Let me check what I'm able to offer and get back to you by [time]." | Promising a credit, refund, discount, or SLA concession on the spot if you're not authorized to. |
Why it matters
Shifting blame doesn't reduce your responsibility in the customer's eyes, it just makes you look like you're not in control of your own product.
A wrong guess costs you twice, once when it's wrong, and again for eroding trust in whatever you say next.
Vague language reads as spin. If it's bad, say how it's bad, the customer will find out the real scope eventually either way.
Only the customer gets to decide how big a deal it is to them.
A verbal promise on a call is still a commitment. Don't make one you or your company can't keep. Know your authority level before the call, if you can't approve a remedy yourself, say you'll follow up with an answer, don't improvise a number.
A wrong guess costs you twice, once when it's wrong, and again for eroding trust in whatever you say next.
Vague language reads as spin. If it's bad, say how it's bad, the customer will find out the real scope eventually either way.
Only the customer gets to decide how big a deal it is to them.
A verbal promise on a call is still a commitment. Don't make one you or your company can't keep. Know your authority level before the call, if you can't approve a remedy yourself, say you'll follow up with an answer, don't improvise a number.
After the conversation
☐ Send a written recap the same day
What was said, what you committed to, and by when. This becomes the record if anything is disputed later.
☐ Log it internally: what happened, what was communicated, to whom, and when
Same discipline as any other high-stakes conversation, if it's not written down, you can't prove it happened.
☐ Set your own reminder for the follow-up date you gave them
Don't rely on memory. A missed self-imposed deadline is worse than the original bad news.
☐ Loop in your leadership or account team on where things stand
Especially if this is a strategic account or the issue could escalate.
☐ Confirm any required compliance or regulatory notifications are handled separately
A customer conversation does not substitute for a formal notification if one is legally required.
☐ Close the loop explicitly once it's resolved
Tell them plainly it's done. Don't let a resolved issue fade out without confirmation, that's how trust actually gets rebuilt.