How to Deliver Bad News to a Customer (With Examples)
How to deliver bad news to a customer: say it in the first two sentences, own it, give a plan with a date, then follow up in writing. Scripts and a template.
Quick answer: To deliver bad news to a customer, say it in the first two sentences, explain what it means for them, and give a plan with a date: what you'll do, what they can do in the meantime, and when they'll hear from you next. Don't blame other teams, and confirm it in writing the same day.
Why bad news to customers goes wrong
Bad news rarely ruins a relationship by itself. What does the damage is how it arrives: late, buried under small talk, split across several conversations, or blamed on "the product team". The customer ends up feeling handled instead of helped.
A thread in r/CustomerSuccess this week worked through a hard version: a CSM preparing to tell a key account two pieces of bad news on the same call. One was a delay to a recurring report. The other was a custom view the customer had already promised to their own leadership, which would need paid development. The advice from experienced CSMs was remarkably consistent, and it applies well beyond that scenario.
How to deliver bad news: a five-part structure
- Say it first. Get the bad news out in the first two sentences. A warm-up makes the customer anxious and makes you sound evasive.
- Say what it means for them. Not why it happened internally, but how it affects their work: "This means the October report won't be ready for your board meeting on the 20th."
- Own it. "We missed this" or "I should have flagged this sooner", even if another team caused it. Throwing a colleague under the bus makes your whole company look unreliable.
- Give the plan with a date. What you're doing, when it will be fixed, and what they can do in the meantime. A specific date beats "soon" every time.
- Say when they'll hear next. "I'll update you on Thursday either way, and you'll be the first to know if anything changes."
Keep it short. One CSM in the thread summed it up as: the bad news, the plan, the timeline and the cost. Everything else is padding.
One call or two? Delivering more than one piece of bad news
Deliver everything in one conversation. Every reply in the thread that addressed it agreed: holding one problem back for another call feels kinder, but when the customer finds out you knew, it costs far more trust than the second piece of news would have.
Order matters less than framing, but a useful rule from the thread: lead with the news you can pair with a new date, then move to the harder one. Frame the whole call as a plan, not a list of problems: "I have two updates, and I've got a plan for both."
How to say no to a customer request without losing them
Sometimes the bad news is "we can't do what you asked", or not for free, or not by their deadline. Three moves help:
- Separate the urgent need from the full request. Ask what they actually need to show or do by their deadline, and offer a workaround for that moment, such as a manual export or a simplified version, while the proper build is scoped.
- Use a trade-off, not a refusal. "Timeframe, scope and cost: we can hit two of the three." The customer chooses, instead of hearing a flat no.
- Give a next step with a date. "A proper quote needs a short scoping session. Can we do that on Tuesday?"
If the request is reasonable and the customer is important, advocate for them internally too. Saying "I'm pushing for this, and here's what I can commit to today" is honest and keeps you on their side.
Bad news phrases to use and avoid
| Instead of | Say |
|---|---|
| "Unfortunately, due to circumstances beyond our control..." | "I have bad news: the report will be a week late." |
| "The dev team dropped the ball." | "We missed this, and I'm sorry." |
| "It should be fixed soon." | "It will be fixed by October 22. I'll update you on Thursday either way." |
| "That's not possible." | "We can do it by your deadline at a smaller scope, or in full by November." |
| "Let me know if you have any questions." | "What does your leadership need to see on the 20th? Let's make sure that's covered." |
Bad news email template
Always follow a bad-news call with a short written summary the same day. It gives the customer something to forward, and it stops the plan drifting.
Subject: [Account]: update on [the issue] and next steps
Hi [name],
Thanks for taking the time today. To confirm what we discussed:
- [Bad news, in one sentence]. This affects [what it means for them].
- What we're doing: [action], with [fix / delivery] by [date].
- In the meantime: [workaround or interim option].
- Next update: [day], or sooner if anything changes.
I'm sorry for the disruption. Reply here if I've missed anything.
[your name]
For writing these summaries after every customer call, not just the hard ones, see our guide to customer call recap emails.
How Blip AI helps with difficult customer emails
The written follow-up is where people stall. You know what you said on the call, but finding the right words for an email the customer might forward to their boss takes ages. Blip AI lets you say it instead, at about 150 words per minute rather than the 52 of the average typist.
- Draft by describing it. In Gmail, start with "Hey Blip" and describe the email: "Hey Blip, follow-up to Priya about the report delay, fixed by October 22, manual export as a workaround, next update Thursday, apologetic but confident." Action Mode drafts it instead of transcribing word for word.
- Set your rules once. With Personalized Blip, add your own writing rules, such as "customer emails: own the problem, never blame another team, always include a date." Blip follows them every time it drafts, and signs off with your name.
- Capture the call while it's fresh. Right after the call, click into your CRM notes, hold Fn on Mac, Ctrl + Win on Windows or Ctrl + Super on Linux, and say what was agreed. Blip removes the filler words and fixes punctuation.
Blip works in any app with a text field, including Gmail, Zendesk, Intercom and CRMs in the browser. The free plan includes 2,000 words a month. Download Blip AI for Mac, Windows or Linux, and see how to prepare for a customer call for the conversation before this one.
FAQ
How do you deliver bad news to a customer? Say the bad news in the first two sentences, explain what it means for the customer, own it without blaming other teams, and give a plan with a specific date and an interim workaround. Follow up in writing the same day.
Should you deliver bad news by email or on a call? Deliver significant bad news on a call, especially to a key account, so the customer can ask questions and hear that you're on it. Then confirm the details in a short email the same day.
Should you give a customer two pieces of bad news at once? Yes. Delivering all the bad news in one conversation is better than splitting it, because holding something back damages trust when it comes out. Frame it as a plan, and lead with the news you can pair with a new date.
How do you say no to a customer politely? Separate their urgent need from the full request, offer a workaround for the deadline, and present a trade-off between timeframe, scope and cost instead of a flat refusal. End with a next step and a date.
What should a bad news email to a customer include? A bad news email should state the problem in one sentence, what it means for the customer, what you're doing and by when, any workaround in the meantime, and when they'll hear from you next, plus a short apology.