Service Outage Communication Prompt Templates
AI prompt templates for service outage communications. Keep customers informed during incidents.
Overview
When your service goes down, how you communicate matters almost as much as how fast you fix it. Silence makes customers anxious and angry. Vague updates make them feel ignored. Good outage communication is honest, timely, and specific. These templates help you keep customers informed without overpromising or creating more confusion.
Best Practices
Acknowledge outages quickly, even if you don't know the cause yet. Silence is worse than 'we're investigating'
Update regularly, even if there's no new information. 'Still working on it' is better than nothing
Be specific about what's affected. 'Some users experiencing issues' is frustrating. Tell them what's broken
Give realistic timelines or say you don't have one. Don't promise 'back soon' and miss it
Follow up after resolution with what happened and what you're doing to prevent it
Prompt Templates
1. Initial Outage Announcement
Write an initial outage announcement. Service affected: [WHAT'S_DOWN] Scope: [WHO'S_AFFECTED] Known cause: [CAUSE_IF_KNOWN] Estimated fix time: [ETA_OR_UNKNOWN] Workaround available: [IF_ANY] Write an announcement that: 1. Clearly states what's not working 2. Acknowledges the impact 3. Explains what you know (even if it's limited) 4. Sets expectations for updates Honest and calm.
Service affected: File uploads and downloads Scope: All users Known cause: Investigating, likely storage provider issue Estimated fix time: Unknown Workaround available: None
We're aware that file uploads and downloads are currently not working. This is affecting all users. Our team is investigating. Early signs point to an issue with our storage provider, but we're still confirming the root cause. We don't have an ETA yet, but we'll post updates every 30 minutes until this is resolved. We know this is disruptive. Thanks for your patience while we work on it.
First announcement when you detect or confirm a service outage
- •Post this as soon as you confirm the issue. Don't wait until you have all the answers
- •Commit to an update schedule and stick to it
2. Outage Status Update
Write a status update during an ongoing outage. Original issue: [WHAT'S_DOWN] Time since outage started: [DURATION] Current status: [WHAT'S_HAPPENING_NOW] New information: [ANYTHING_LEARNED] New ETA: [UPDATED_ESTIMATE] Write an update that: 1. Reminds them what the issue is 2. Shares what you've learned or done 3. Updates the timeline if possible 4. Maintains trust even if news isn't great Progress-focused, not excuse-focused.
Original issue: File uploads and downloads failing Time since outage started: 2 hours Current status: Identified root cause, implementing fix New information: Third-party storage API had a configuration error after their update New ETA: Expecting resolution within 1 hour
Update on file upload/download outage (2 hours in): We've identified the cause. Our storage provider pushed an update that changed an API configuration, which broke our connection to their service. We're implementing a fix now and coordinating with their team. We expect uploads and downloads to be working again within the next hour. We'll confirm once everything is back to normal. Thanks for bearing with us.
Providing updates during an ongoing service disruption
- •Even if there's no progress, post an update. 'Still working, no new info' is better than silence
- •If your ETA changes, say so directly. Don't pretend you didn't give one before
3. Outage Resolution Announcement
Write a resolution announcement when service is restored. What was affected: [SERVICE] Total downtime: [DURATION] What caused it: [ROOT_CAUSE] What you're doing to prevent recurrence: [PREVENTION_STEPS] Any customer action needed: [IF_ANY] Write a resolution message that: 1. Confirms service is restored 2. Briefly explains what happened 3. Acknowledges the impact 4. Mentions what you're doing to prevent this in the future Accountable and forward-looking.
What was affected: File uploads and downloads Total downtime: 3 hours What caused it: Storage provider API change broke authentication What you're doing to prevent recurrence: Adding monitoring for API changes, setting up backup storage failover Any customer action needed: None, should work normally now
File uploads and downloads are back online. The outage lasted approximately 3 hours. What happened: Our storage provider pushed an update that changed how API authentication works. Our system didn't adapt to the change, which caused the connection to fail. We're adding automated monitoring to catch these changes faster. We're also setting up a backup storage system so future issues with one provider won't take down the feature entirely. You shouldn't need to do anything on your end. Everything should work normally now. If you're still seeing issues, contact support. We're sorry for the disruption and appreciate your patience.
Announcing that a service outage has been resolved
- •Don't over-explain. Customers want to know it's fixed, not every technical detail
- •Mentioning prevention steps shows you're taking it seriously, not just moving on
4. Proactive Maintenance Notice
Write a notice for planned maintenance or downtime. What's happening: [MAINTENANCE_TYPE] When: [DATE_AND_TIME_WITH_TIMEZONE] Expected duration: [HOW_LONG] Services affected: [WHAT_WON'T_WORK] Customer action needed: [PREPARATION_STEPS] Write a notice that: 1. Clearly states when and what 2. Explains why (briefly) 3. Tells them what to expect 4. Gives advance warning appropriate to the impact Helpful, not alarming.
What's happening: Database migration to improve performance When: Saturday, March 15 at 2:00 AM EST Expected duration: 2 hours Services affected: Entire platform will be in read-only mode (no saves, no new uploads) Customer action needed: Save any work before 2 AM
Scheduled maintenance: Saturday, March 15, 2:00-4:00 AM EST We're upgrading our database to improve performance and reliability. During this window, the platform will be in read-only mode. You can view your content, but you won't be able to save changes or upload new files. What to do: Make sure any work is saved before 2:00 AM EST on Saturday. We scheduled this for overnight hours to minimize disruption. If you have questions, reply to this email. Thanks for your patience. The upgrade will make things faster once it's done.
Notifying customers about planned downtime or maintenance windows
- •Always include timezone. Your 2 AM might be someone else's 2 PM
- •Explain the benefit. 'To improve performance' helps them understand why you're disrupting them
Common Mistakes to Avoid
Waiting too long to acknowledge an outage. Customers find out from each other and lose trust
Using vague language like 'some users may experience issues' when the service is clearly down for everyone
Going silent during a long outage. Regular updates, even without new info, show you're still working on it
Frequently Asked Questions
When your service goes down, how you communicate matters almost as much as how fast you fix it. Silence makes customers anxious and angry. Vague updates make them feel ignored. Good outage communication is honest, timely, and specific. These templates help you keep customers informed without overpromising or creating more confusion.
Related Templates
Support Ticket Response Prompt Templates
AI prompt templates for support ticket responses. Handle customer inquiries efficiently and professionally.
FAQ Response Prompt Templates
AI prompt templates for FAQ responses. Create comprehensive answers to frequently asked questions.
Chatbot Script Prompt Templates
AI prompt templates for chatbot scripts. Design conversational flows for automated customer support.
Have your own prompt to optimize?