The email you send when a client's site goes down matters more than the outage itself. Handled well, downtime becomes proof that you're on top of things. Handled late or vaguely, it becomes the reason a client starts shopping around. These templates assume one thing: you found out about the outage from your monitoring, not from the client. If it's the other way around, no template saves you.
Template 1: the initial notification
Send this as soon as you've confirmed the outage is real. Speed beats completeness; you can follow up with detail.
Subject: [Site name] is currently down. We're on it.
Hi [Name],
Our monitoring detected that [site URL] went down at [time] [timezone]. We were alerted automatically and started investigating right away.
What we know so far: [one sentence, e.g. "the server is not responding" or "the hosting provider is reporting an incident"].
We'll send you an update within [30/60] minutes, or sooner if it's resolved. No action is needed from you.
[Your name]
Template 2: the mid-incident update
Send at the cadence you promised, even if the update is "no change." Silence is what clients punish.
Subject: Update: [Site name] outage
Hi [Name],
Quick update on the outage at [site URL]. [What you've found, in one or two sentences.] [What you're doing about it.]
Current best estimate for restoration: [time or "we expect to know more by X"].
Next update by [time].
[Your name]
Template 3: the all-clear and wrap-up
Send after recovery, once you understand the cause. This is the email that converts a bad afternoon into renewed trust.
Subject: [Site name] is back online
Hi [Name],
[Site URL] came back online at [time] and has been stable since. Total downtime: [duration].
What happened: [plain-language cause, two or three sentences, no jargon].
What we're doing so it doesn't repeat: [one or two concrete steps].
If you'd like, I can walk you through the incident timeline on a quick call.
[Your name]
Why the timeline matters
Every template above leans on facts your monitoring gives you: exact start time, duration, and first-alert evidence. That timeline is also what protects you if the outage touches an SLA. If you don't have that data today, that's the gap to close first, and it's also what makes the numbers in our downtime cost calculator concrete instead of hypothetical. Pair these emails with a monthly uptime report so outage communication isn't the only time clients hear about uptime.