Every business eventually has to tell a customer something they don't want to hear: the shipment slipped, the feature isn't ready, the outage lasted longer than promised. The delay itself rarely destroys the relationship. The message about the delay often does. Customers forgive problems; they don't forgive feeling managed, misled, or ignored.
The anatomy of a good bad-news message
The structure that works, in order:
- The news, plainly, first. "Your order will arrive on June 24 instead of June 19." No throat-clearing, no "we pride ourselves on service" preamble. Burying the news reads as evasion.
- A brief, honest reason. One or two sentences. "A supplier shortage delayed a component" is plenty. Over-explaining reads as excuse-making; refusing any reason reads as stonewalling.
- What you're doing about it. The recovery action, concretely. Expedited shipping, a workaround, a credit — whatever is true.
- What the customer should expect next, and when. Ideally with the next update scheduled: "We'll email you again by Friday with tracking."
- A genuine acknowledgment. One sentence that treats the inconvenience as real. Not three paragraphs of apology — one sentence that doesn't sound like a template.
Timing beats polish
An imperfect message today beats a perfect one on Thursday. Customers judge silence more harshly than bad news; they fill the vacuum with worst cases. The operating rule: tell them as soon as you'd want to know, which is now — even if the message is "we're aware, we're investigating, next update by 3pm."
Words that make it worse
A few phrases reliably inflame a delay message:
- "Due to circumstances beyond our control" — reads as responsibility-dodging even when true.
- "We apologize for any inconvenience this may cause" — the conditional "may" tells the customer you haven't imagined their situation.
- "As per our policy" — policy is your problem, not theirs.
- Over-cheerful sign-offs on bad news ("Have a great day!") — tonal whiplash.
Plain, specific, first-person language does better everywhere: "We got this wrong and here's what we're doing."
Tone is the hard part — treat it as a real task
The same facts can read as accountable or as defensive depending on word choice, and it's genuinely hard to hear your own message the way an annoyed customer will. This is a case where a rewriting pass earns its time: teams that send a lot of customer updates often keep reusable framings for recurring situations, and a tool like Wrivio supports exactly that pattern — saved contexts like "customer delay" that rewrite a rough draft into the tone you've decided such messages should have, with a word-level diff so you approve every change before it ships.
After the message: close the loop
The delay message is step one. The trust repair happens at step two — actually sending the promised follow-up, on time, even if the update is "still on track for the 24th." A customer who gets proactive updates through a problem frequently ends up more loyal than one who never hit the problem at all. The message is not the recovery; the follow-through is.
