Blog/ Email writing & templates

Outage Email Template: 10 Notifications to Customers

Nafiul HasanNafiul Hasan· 13 min read
Outage notification email to customers — staged service downtime message templates from first notice through resolution and follow-up commitment

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
  1. 01Which outage email template do you need?
  2. 02When to send an outage notification to customers
  3. 03What a good outage notification email should contain
  4. 04Template 1: the system down email when you know nothing
  5. 05Template 2: Unplanned outage notification when the cause is known
  6. 06Template 3: Scheduled outage update with no new information
  7. 07Template 4: Cause identified, fix not yet deployed
  8. 08Template 5: Server down notification, fix in progress
  9. 09Template 6: Service restored / outage resolved email template
  10. 10Template 7: Reason for outage (RFO) follow-up within 24 hours
  11. 11Template 8: SLA credit announcement
  12. 12Template 9: Partial restoration (service interruption message)
  13. 13Template 10: Extended outage when the estimated resolution time is missed
  14. 14Template 11: notify your own team of an IT, internet or power outage
  15. 15How often should you update customers during an outage?
  16. 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.

Copy this now: system down email, cause unknown
Subject[SERVICE] outage — [START TIME UTC]
We are experiencing an outage affecting [IMPACT]. It began at approximately [START TIME UTC].
Our team is investigating. We do not yet have a cause or an estimated fix time.
Next update by [NEXT UPDATE AT UTC]. Live status: [STATUS PAGE URL].
We apologise for the disruption.

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.

Timeline showing outage notification update cadence: first notice at detection, fixed-interval updates during the active incident, a resolved notice at restoration, and a follow-up commitment within 24 hours
Committing to a fixed update cadence in the first notice, and keeping it even when you have nothing new to report, is the most effective thing you can do for customer trust during a live incident.
TemplateStageSend when
1Unplanned outage: first notice, cause unknownOutage confirmed, root cause not yet identified
2Unplanned outage: first notice, cause knownOutage confirmed, root cause already identified
3Scheduled update, no new informationCommitted update time arrives with nothing to report
4Cause identified, fix not yet deployedRoot cause confirmed, remediation not yet started
5Mitigation in progressA fix is being actively deployed
6Service restoredService is fully operational again
7Reason for outage (RFO) follow-upWithin 24 hours of resolution, promise or deliver the incident report
8SLA credit announcementWhen a credit or compensation is being issued
9Partial restorationSome customers or regions are back, others are not
10Extended outage: ETR missedEstimated resolution time passes without a fix
11Internal: IT, internet or power outageYou 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. 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. 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. 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. 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. 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

A first notice that guesses at the cause and guesses wrong needs a correction, which adds noise to an incident and tells customers you do not have a handle on it. Cause belongs in the update where it is confirmed.

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.

Unplanned outage notification — cause known
Subject[SERVICE] outage — [START TIME UTC]
We are experiencing an outage affecting [IMPACT]. The issue began at [START TIME UTC] and has been traced to [CAUSE].
Our team is working on a fix. We expect to provide a resolution update by [NEXT UPDATE AT UTC].
Status updates are available at [STATUS PAGE URL]. We will notify you by email when service is restored.

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.

Scheduled update — no new information
Subject[SERVICE] outage update — [TIMESTAMP UTC]
This is a scheduled update on the [SERVICE] outage that began at [START TIME UTC].
Our team is still investigating. We have not yet identified the root cause and do not have an estimated resolution time to share.
We will send the next update by [NEXT UPDATE AT UTC]. Current status at [STATUS PAGE URL].

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.

Cause identified
Subject[SERVICE] update: cause identified — [TIMESTAMP UTC]
Update on the [SERVICE] outage that began at [START TIME UTC].
We have identified the root cause: [CAUSE]. Our team is now preparing a fix and expects to begin deployment by [TIME UTC].
Next update: [NEXT UPDATE AT UTC]. Status page: [STATUS PAGE URL].

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.

Mitigation in progress
Subject[SERVICE] update: fix being deployed — [TIMESTAMP UTC]
Update on the [SERVICE] outage that began at [START TIME UTC].
We are actively deploying a fix for the root cause ([CAUSE]). Mitigation began at [TIME UTC]. We expect [IMPACT] to be resolved by approximately [ETR UTC], though this estimate may change as the deployment progresses.
We will notify you by email once service is fully restored. Status page: [STATUS PAGE URL].

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.

Service restored
Subject[SERVICE] restored — [RESOLVED TIME UTC]
[SERVICE] is now fully operational. Service was restored at [RESOLVED TIME UTC] after an outage of approximately [DURATION].
The issue was caused by [CAUSE]. We have applied [brief description of the fix] and are monitoring to confirm stability.
We apologise for the disruption. A full incident report will follow within 24 hours. If you continue to experience issues, contact us at [SUPPORT LINK].

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.

Reason for outage (RFO) follow-up
SubjectReason for outage: [SERVICE] outage of [DATE]
Following yesterday's outage, we want to confirm what happened and what we are doing to prevent a recurrence.
Root cause: [CAUSE]. Duration: [DURATION]. Scope of impact: [AFFECTED CUSTOMER SCOPE].
We are publishing a full incident report at [POSTMORTEM URL] within [TIMEFRAME]. That report will cover the timeline, the root cause in detail, and the specific measures we are implementing to prevent this class of failure from recurring.
Thank you for your patience during this incident.

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.

SLA credit announcement
SubjectService credit for [SERVICE] outage of [DATE]
Following the [SERVICE] outage on [DATE], we are issuing service credits to affected accounts in accordance with our Service Level Agreement.
The outage duration of [DURATION] falls under the [SLA TIER] credit provision. Credits equivalent to [CREDIT DESCRIPTION] will be applied to your account by [DATE].
No action is required on your part. The credit will appear on your next billing statement. Questions about your account's credit can be directed to [BILLING SUPPORT LINK].

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.

Partial restoration
Subject[SERVICE] partially restored — [TIMESTAMP UTC]
Update on the [SERVICE] outage that began at [START TIME UTC].
Service has been restored for [RECOVERED SEGMENT — e.g. customers on our EU infrastructure]. Customers on [STILL-AFFECTED SEGMENT] are still experiencing [IMPACT]. We expect to complete the remaining restoration by approximately [ETR UTC].
Next update: [NEXT UPDATE AT UTC]. Status page: [STATUS PAGE URL]. If you are unsure which segment applies to your account, check your region settings or contact support.

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.

Extended outage — ETR missed
Subject[SERVICE] outage extended — update [TIMESTAMP UTC]
We want to update you on the [SERVICE] outage that began at [START TIME UTC]. Our earlier estimate of [PREVIOUS ETR UTC] was not met.
[Briefly explain why — e.g. the initial fix did not perform as expected and we have reverted to an alternative approach.] We are now targeting [NEW ETR UTC], though we will update you immediately if that changes.
We understand this is causing significant disruption. Our team is treating this at its highest priority. Next update: [NEXT UPDATE AT UTC].

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.

Internal IT outage notification
Subject[SYSTEM / INTERNET / POWER] outage — what you need to know
[SYSTEM] has been unavailable since approximately [START TIME]. This affects [TEAMS OR TASKS AFFECTED].
Workaround: [WHAT PEOPLE CAN DO, e.g. use mobile hotspot, work from the shared drive, log tickets on paper]. Please avoid [ACTION THAT MAKES IT WORSE].
For urgent issues contact [NAME / CHANNEL / PHONE]. Next update by [NEXT UPDATE AT].

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

Nafiul Hasan

Written by

Nafiul Hasan

Nafiul 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.

EntrepreneurAI Automation System BuilderAI EnthusiastBuilds AI Enterprise Solutions10+ years experience
More from Nafiul
Ready when you are

Draft the replies around an outage faster.

AI Emaily drafts one-to-one replies and key-account notes in the voice you set, and nothing sends until you approve it. Start a 7-day free trial.

  • 7-day free trial
  • Cancel anytime
  • Every provider