Service outage apology email
After an outage, customers want facts more than remorse: what broke, whether their data was affected, and what you changed. A good outage email is honest about impact and specific about prevention — vague reassurance reads worse than the outage itself.
Subject: [Product name] outage on [date] — what happened
Hi [first name], On [date], [product name] was down for [duration] between [start time] and [end time] [timezone]. During that window, [plain-language description of what customers experienced, e.g. "you couldn't log in or send messages"]. Your data was not affected. [Adjust or remove if untrue — never claim this without confirming.] What happened: [one or two sentences of plain-language cause, e.g. "a database migration locked a table that handles sign-ins"]. What we've changed: [specific prevention step, e.g. "migrations of this type now run against a replica first"]. I'm sorry for the disruption. If the outage caused a problem on your side that we can help untangle, reply here and we'll prioritize it. [your name] [role], [company]
Replace every [bracketed] placeholder before sending — the brackets are there so an unfilled field is impossible to miss.
How to use this template well
- Send this after resolution, not during. Status updates during the incident belong on a status page, not in apology email.
- State whether data was affected even when the answer is no — it's the first question every customer silently asks.
- Explain the cause in plain language. "A database migration locked sign-ins" builds more trust than "an infrastructure issue".
- Name one concrete prevention change. "We take reliability seriously" is not a change.
Related templates
Apology email to an unhappy customerDe-escalate by restating their complaint accurately before defending anything.Escalation status update emailThe unprompted check-in that keeps an escalated customer from having to chase you.Billing error apology emailFor overcharges: the wrong amount, the right amount, and the correction — already done.
Your team's replies, one snippet away.
Repliqo turns templates like this one into shared snippets your whole team inserts in two keystrokes — with variables that fill in the customer's name automatically.