Outage Email Template: 10 Notifications to Customers

The short answer
An outage notification email should name the affected service, say when it started in UTC, describe the impact in plain terms, state what your team is doing and promise a specific time for the next update. Send it as soon as the outage is confirmed, even without a cause, and update on a fixed schedule.
Copy-paste outage email templates: first notice (cause unknown), updates, service restored, partial restoration, SLA credit. Plus update-cadence rules.
On this page
- 01Which outage email template do you need?
- 02When to send an outage notification to customers
- 03What a good outage notification email should contain
- 04Template 1: the system down email when you know nothing
- 05Template 2: Unplanned outage notification when the cause is known
- 06Template 3: Scheduled outage update with no new information
- 07Template 4: Cause identified, fix not yet deployed
- 08Template 5: Server down notification, fix in progress
- 09Template 6: Service restored / outage resolved email template
- 10Template 7: Reason for outage (RFO) follow-up within 24 hours
- 11Template 8: SLA credit announcement
- 12Template 9: Partial restoration (service interruption message)
- 13Template 10: Extended outage when the estimated resolution time is missed
- 14Template 11: notify your own team of an IT, internet or power outage
- 15How often should you update customers during an outage?
- 16Sending outage updates, and where AI Emaily fits
Send the first outage email as soon as you confirm customers are affected, before you know the cause. Copy the system down email below, fill the brackets, and send it. The templates after it cover updates, service restored, partial restoration, SLA credit and a reason for outage (RFO) follow-up, plus a version for your own staff.
Which outage email template do you need?#
Templates 1 to 5 are for an unplanned outage notification while the incident is live, and the rest cover what comes after. Subject lines are deliberately direct, because customers need to recognise an outage email at a glance and softened lines such as "Important service update" slow that down. Most bodies stay under 150 words, since the status page carries the detail.

| Template | Stage | Send when |
|---|---|---|
| 1 | Unplanned outage: first notice, cause unknown | Outage confirmed, root cause not yet identified |
| 2 | Unplanned outage: first notice, cause known | Outage confirmed, root cause already identified |
| 3 | Scheduled update, no new information | Committed update time arrives with nothing to report |
| 4 | Cause identified, fix not yet deployed | Root cause confirmed, remediation not yet started |
| 5 | Mitigation in progress | A fix is being actively deployed |
| 6 | Service restored | Service is fully operational again |
| 7 | Reason for outage (RFO) follow-up | Within 24 hours of resolution, promise or deliver the incident report |
| 8 | SLA credit announcement | When a credit or compensation is being issued |
| 9 | Partial restoration | Some customers or regions are back, others are not |
| 10 | Extended outage: ETR missed | Estimated resolution time passes without a fix |
| 11 | Internal: IT, internet or power outage | You need to tell your own staff, not customers |
When to send an outage notification to customers#
The threshold for sending should be low. The cost of an unnecessary update is far smaller than the cost of silence during a real incident.
- Send once an outage is confirmed and customers are affected, even if you only know the impact. Do not wait for a root cause or an ETR.
- Send for a degradation that makes a key workflow unreliable, using the service degradation notice wording instead of "outage".
- Send if an issue has run more than ten minutes without recovery, or if you are unsure. If you are unsure, send.
- For planned work, use a scheduled maintenance notice instead.
What a good outage notification email should contain#
A good outage email is short and structured. The customer is already disrupted, and an infrastructure explanation or a paragraph of apology does not help them in the moment. Include these five elements, in roughly this order.
- 1
What is down and since when
Name the specific service and when the issue started, in UTC. Avoid vague phrases like "intermittent issues" unless the impact is genuinely intermittent.
- 2
Who is affected and how
Describe the impact in customer terms. "Customers cannot submit new orders" is useful. "Pod restart loop in us-east-1" is not.
- 3
What your team is doing
Even if the answer is "our team is investigating," say it explicitly. As you learn more, replace it with "identified the cause" or "applying a fix."
- 4
When the next update will arrive
State a specific time, not "soon." If the time arrives and you have nothing new, send a message saying exactly that. Silence against a committed time is worse than an empty update.
- 5
Where to follow real-time progress
Link to your status page, and to a support channel for affected customers if you have one. Route granular detail to the status page instead of the email.
Template 1: the system down email when you know nothing#
The first-notice box at the top of this page is Template 1, and it is the hardest message to write under pressure. The typical failure is waiting: engineers are diagnosing, nobody wants to send something that may be revised in twenty minutes, and by the time anything goes out, customers have found the problem on a third-party thread or opened a ticket.
Separate what you know from what you do not, then publish what you know. You know the service is down, customers are affected, your team is investigating and when the next update will arrive. None of that needs a root cause or an ETR, so the message is not wrong if the cause turns out to be different. You never stated one.
Publish impact, not speculation
Template 2: Unplanned outage notification when the cause is known#
When you identify the root cause at the same moment as the outage, include it in the first notice. Do not editorialize or explain beyond what is operationally useful to the customer. Save the full technical narrative for the postmortem.
Template 3: Scheduled outage update with no new information#
This is the update you send when the committed time arrives and you still have nothing to report. Do not skip it. An empty update sent on schedule signals that your team is present and in control. A missed committed update time signals the opposite, regardless of what is actually happening on your incident call.
Template 4: Cause identified, fix not yet deployed#
The moment you confirm the root cause, publish it — even if remediation has not started. A confirmed root cause tells customers the problem is understood and bounded, which meaningfully reduces anxiety compared to an ongoing 'we are investigating' message.
Template 5: Server down notification, fix in progress#
When a fix is actively being deployed, say so clearly. This is the message customers most want to see during a prolonged outage — it tells them the incident has an end in sight. Include an estimated resolution time if you have a reasonable basis for one, and caveat it honestly.
Template 6: Service restored / outage resolved email template#
The resolved message is not an apology letter — it is a clear, brief confirmation that service is back. Save the postmortem detail for the follow-up. The customer's first question at this point is whether it is actually fixed, and the first sentence should answer that without delay.
Template 7: Reason for outage (RFO) follow-up within 24 hours#
A reason for outage (RFO) email tells customers what happened and what you are changing. It does not need the full postmortem on day one: confirm the basic facts, name a specific timeframe for the report, and send it. The long version, with timeline and prevention measures, is covered in the incident postmortem email.
Template 8: SLA credit announcement#
If your service level agreement includes credits for downtime, send a separate, plainly worded email that describes what is being issued and when. Do not bury the credit detail inside the resolved message. Enterprise customers expect the credit provision referenced and the application date named. For the longer apology-plus-credit version, see the SLA breach apology email.
Template 9: Partial restoration (service interruption message)#
Partial restoration is a common and underserved scenario: service is back for some customers or regions but not all. The message must be precise about which segment is recovered and which is not, so that customers can self-identify without contacting support to find out whether the update applies to them.
Template 10: Extended outage when the estimated resolution time is missed#
When you have committed to an estimated resolution time and that window passes without a fix, send an update immediately — do not wait for the next scheduled update time. A missed ETR with no explanation is one of the most damaging things that can happen during an incident. This message must acknowledge the miss directly and give a revised estimate.
Template 11: notify your own team of an IT, internet or power outage#
An IT outage notification to employees has a different job: tell people what they can still do and who to contact, not reassure a customer. Keep it to impact, workaround, contact and next update.
How often should you update customers during an outage?#
Commit to a cadence in the first notice and keep it. There is no universal standard. Atlassian's incident communications play suggests an update every 20 to 30 minutes until resolution, and many teams settle on 30 to 60 minutes depending on severity. The cadence matters more than the exact interval: customers who know the next update lands at 14:30 UTC stop refreshing your status page every five minutes.
Outage emails rarely get replies, and that silence is not satisfaction. Customers are watching the status page, support forums or social media instead. Watch support ticket volume in real time, and if it surges while replies stay low, update more often or simplify the status page rather than sending less.
For key accounts, a short personal note from the account manager during a critical outage, separate from the bulk notice, tells a high-value customer they are being treated as one. Decide who owns that call before an incident, not during one.
Sending outage updates, and where AI Emaily fits#
Be realistic about tooling: an outage notice to your whole customer base goes through a status page or an email service provider, not an email client. AI Emaily is not a bulk sender and does not send mass outage notices.
We build AI Emaily, an AI-native email client for Gmail, Outlook and IMAP accounts. Where it helps during an incident is the one-to-one mail around it: drafting replies to customers who write in and key-account notes. In Copilot mode it drafts and you approve every message before it sends, using the voice you set in your Personal Context and per-client profiles, and actions are written to an audit log. The Team plan is the one built for shared inboxes. AI Emaily has a 7-day free trial.
Frequently asked
See it in AI Emaily
Keep reading
Sources

Written by
Nafiul HasanNafiul Hasan is an entrepreneur and AI automation system builder with 10+ years of experience turning messy, manual workflows into reliable automated systems. He designs and ships AI enterprise solutions end-to-end — the agent logic, the data plumbing, and the product people actually use — and founded AI Emaily to give busy professionals their attention back. He writes here from the builder's seat: what works, what breaks, and how to put AI to work without giving up control.