Downtime & Outage Response Email Templates
Copy & paste updates that keep customers informed during incidents
When systems go down, customers need calm, clear communication more than perfect answers. These 10 templates help you acknowledge incidents, share status updates, explain maintenance, and follow up after service is restored.
Downtime changes the tone of a customer relationship fast. A vague or delayed update makes people wonder whether anyone is in control, while a clear message helps them understand what is affected, what your team is doing, and when they will hear from you again.
These 10 downtime and outage response templates give your support team a reliable starting point for the moments that matter: active incidents, scheduled maintenance, service restoration, security alerts, and post-incident follow-ups. Copy them from this page, or save them in Support Toolbox so the right incident update is always ready when pressure is high.
The Anatomy of a Clear Outage Update
Strong incident communication is calm, specific, and predictable. Include these five elements so customers know what is happening, how it affects them, and when they will hear from you next.
The Impact
Tell customers what is affected in plain language. Name the product area, workflow, region, or account type when you can so people can quickly understand whether the incident applies to them.
The Status
Be clear about where things stand right now. Are you investigating, monitoring a fix, restoring service, or fully resolved? Customers should not have to infer the current state from vague wording.
The Ownership
Show that your team is actively handling the incident. Use confident, responsible language without blaming vendors, customers, or invisible internal processes.
The Timeline
Set expectations carefully. Share a confirmed ETA only when you have one, and when you do not, give the time of the next update instead of making promises you may not be able to keep.
The Next Step
Close with the clearest action available: check a status page, use a workaround, wait for the next update, or reply if they are still affected after service is restored.
10 Downtime & Outage Response Email Templates
Ready to copy, paste, and customize for your customers
First Response
Use these when an incident is new, uncertain, or still being investigated and customers need a fast, trustworthy first update.
Initial Outage Acknowledgement
First ResponseHi [Customer Name],
We're currently investigating a service disruption affecting [Product/Feature/Service]. Some customers may be experiencing [brief impact, such as login issues, slow loading, or failed requests].
Our team is actively working to identify the cause and restore normal service as quickly as possible.
We will share another update by [Next Update Time], or sooner if we have meaningful progress before then.
Thank you for your patience while we work on this.
[Your Name]
[Company Name] Support
Investigating Service Disruption
First ResponseHi [Customer Name],
We are still investigating the issue affecting [Product/Feature/Service]. At this stage, we can confirm that [known impact], but we are still working to identify the root cause.
We know this may be interrupting your work, and we're sorry for the disruption.
For now, please [recommended action, such as avoid retrying payments, use the workaround below, or watch the status page]. If a workaround becomes available, we will share it right away.
Our next update will be posted by [Next Update Time].
[Your Name]
[Company Name] Support
Maintenance & Degradation
Planned maintenance notices and partial service disruption updates that set expectations before frustration grows.
Scheduled Maintenance Notice
Maintenance & DegradationHi [Customer Name],
We want to let you know about scheduled maintenance for [Product/Service] on [Date] from [Start Time] to [End Time] [Time Zone].
During this window, [Product/Feature] may be unavailable or slower than usual while our team completes [brief reason, such as infrastructure upgrades or database maintenance].
What to expect:
- Expected impact: [Impact]
- Expected duration: [Duration]
- Status updates: [Status Page Link or Update Channel]
We recommend completing any time-sensitive work before the maintenance window begins.
[Your Name]
[Company Name] Support
Performance Degradation Update
Maintenance & DegradationHi [Customer Name],
We're currently seeing degraded performance in [Product/Feature]. The service is still available, but some actions may be slower than normal or may need to be retried.
Our team is monitoring the issue and working to return performance to normal. At the moment, the known impact is:
- [Impact 1]
- [Impact 2]
- [Any unaffected areas, if helpful]
If your task is time-sensitive, you can try [workaround or alternative path].
We will send another update by [Next Update Time].
[Your Name]
[Company Name] Support
Active Incident Updates
Status updates for major outages, partial recovery, and sensitive incidents where customers need clear facts without speculation.
Major Incident Status Update
Active Incident UpdatesHi [Customer Name],
We want to share the latest update on the outage affecting [Product/Service].
Current status: [Investigating / Identified / Fix in progress / Monitoring]
Customer impact: [Brief description of who is affected and what they may experience]
What we're doing: [Brief description of mitigation or recovery work]
If you are affected, we recommend [recommended action]. You can also follow live updates here: [Status Page Link].
Our next update will be shared by [Next Update Time].
[Your Name]
[Company Name] Support
Partial Service Recovery
Active Incident UpdatesHi [Customer Name],
We're seeing partial recovery for [Product/Service]. Some customers may now be able to use [Feature/Workflow], but the incident is not fully resolved yet.
Our team is continuing to monitor recovery and address the remaining impact. You may still notice [remaining issue, such as delays, intermittent errors, or slower processing].
If the service is working for you now, you can continue using it. If you still see errors, please wait a few minutes and try again, or use [workaround] if available.
We will confirm once service is fully restored.
[Your Name]
[Company Name] Support
Security Alert or Access Concern
Active Incident UpdatesHi [Customer Name],
We're contacting you because we identified a potential issue involving [brief description of security or access concern]. Our team is investigating and taking precautionary steps to protect customer accounts.
At this time, we can confirm:
- [Confirmed fact 1]
- [Confirmed fact 2]
- [What is still being investigated]
As a precaution, please [customer action, such as reset your password, review recent activity, or enable two-factor authentication]. We will never ask you to share your password or verification codes by email.
We will share another update by [Next Update Time] as our investigation continues.
[Your Name]
[Company Name] Support
Resolution & Follow-Up
Messages for service restoration, post-incident follow-up, and account credits after the urgent work is done.
Service Restored Notification
Resolution & Follow-UpHi [Customer Name],
The issue affecting [Product/Service] has been resolved, and service is now restored.
Incident summary:
- Started: [Start Time]
- Resolved: [Resolved Time]
- Impact: [Brief customer impact]
We are continuing to monitor the system to make sure everything remains stable.
We're sorry for the disruption this caused. If you are still experiencing issues, please reply to this email and we will help right away.
[Your Name]
[Company Name] Support
Post-Incident Follow-Up
Resolution & Follow-UpHi [Customer Name],
We wanted to follow up on the [Product/Service] incident that occurred on [Date]. Service has been restored, and our team has completed an initial review of what happened.
What happened: [Plain-language summary]
Customer impact: [Brief summary of affected features, customers, or time window]
What we're changing: [Prevention or monitoring improvement]
We're sorry for the disruption and appreciate your patience while our team worked through the incident.
If you have any remaining questions or are still seeing unexpected behavior, reply here and we will take a closer look.
[Your Name]
[Company Name] Support
SLA Credit or Compensation Follow-Up
Resolution & Follow-UpHi [Customer Name],
We're following up about the [Product/Service] incident on [Date]. Based on the impact to your account and our [SLA/Policy], we are applying [credit/refund/compensation details].
You will see this reflected on [next invoice/account balance/payment method] by [Date]. No action is needed from you.
We know a credit does not erase the disruption, but we want to acknowledge the impact and make this right where we can.
If you have questions about the credit or believe your account was affected differently, reply to this email and we will review it with you.
[Your Name]
[Company Name] Support
Work Smarter: Manage These Templates with Support Toolbox
Incident messages are hard to write when customers are already waiting, internal teams are still investigating, and every word needs to be accurate. Keeping approved templates ready helps support teams respond quickly without inventing phrasing during the most stressful part of an outage.
Support Toolbox helps you store, organize, and instantly copy outage updates, maintenance notices, and post-incident follow-ups from one searchable library.
Organize with tags: Group your templates your way for easy discovery.
Search instantly: Find the right template in milliseconds
Copy in one click: Paste into Zendesk, Gmail, or any tool
Best Practices for Incident Communication
During downtime, customers do not need polished spin. They need accurate facts, predictable updates, and a clear sense that your team is actively handling the problem.
Lead with the current status
Start with what customers need most: whether the service is down, degraded, recovering, or resolved. Background details can come after the status is clear.
Separate facts from investigation
State what you know, what you are still checking, and what you will update later. This keeps the message trustworthy even when the incident is still moving.
Give a next update time
When you cannot give a resolution ETA, give a communication ETA. A reliable next-update time reduces duplicate tickets and helps customers plan.
Keep workarounds visible
If there is any temporary path customers can use, put it near the top of the message. During downtime, a useful workaround is often more valuable than a long explanation.
Follow up after resolution
Do not disappear once service is restored. A short resolution note, apology, and post-incident follow-up helps rebuild trust after a stressful interruption.
Frequently Asked Questions
How quickly should I send a downtime or outage update?
Send an initial acknowledgment as soon as you know customers may be affected, even if you do not have a full diagnosis yet. For active incidents, it is usually better to say you are investigating and will share another update at a specific time than to wait silently for perfect information.
What should an outage email include?
A clear outage email should include what is affected, who may be impacted, the current status, what your team is doing, any workaround if one exists, and when customers should expect the next update. Avoid internal jargon and keep the message easy to scan.
How often should I update customers during an incident?
Set a predictable update cadence based on severity. For a major outage, updates every 30 to 60 minutes are often appropriate, even when there is no major change. For smaller degradations, longer intervals may be fine. The important part is to keep the next update time visible and reliable.
Should I share the root cause before the investigation is complete?
No. Share confirmed facts, not guesses. If the root cause is still under investigation, say that plainly and explain what customers can expect next. Speculating too early can create confusion and force you to correct the record later.
Use these downtime and outage response templates as a starting point, then customize the impact, timeline, and next steps for each incident. Clear communication will not prevent every outage, but it can preserve trust while your team works to bring service back.
Never hunt for templates again
Stop searching the web every time you need a template. Support Toolbox lets you save your favorite templates with instant hotkey access.