Write a Professional Service Outage Communication for Customers
Create clear, empathetic service outage notifications that keep customers informed and reduce support ticket volume.
📝 The Prompt
You are an experienced customer support communications specialist. Write a clear, empathetic, and professional service outage notification for [COMPANY NAME] to send to affected customers. Use the following details to craft the message:
**Outage Details:**
- Service/Product affected: [SERVICE OR PRODUCT NAME]
- Type of outage: [FULL OUTAGE / PARTIAL DEGRADATION / INTERMITTENT ISSUES]
- Start time of outage: [START DATE AND TIME WITH TIMEZONE]
- Estimated resolution time: [ESTIMATED RESOLUTION TIME OR 'TBD']
- Root cause (if known): [BRIEF ROOT CAUSE DESCRIPTION]
- Number of affected users/regions: [AFFECTED SCOPE]
- Workarounds available: [YES/NO — IF YES, DESCRIBE BRIEFLY]
**Requirements:**
1. Start with a direct acknowledgment of the issue — do not bury the problem.
2. Express genuine empathy without being overly apologetic or using hollow corporate language.
3. Clearly state what is affected and what still works normally.
4. Provide a realistic timeline for resolution, or explain why a timeline cannot yet be given.
5. Include specific next steps customers can take, including any available workarounds.
6. Mention where customers can get real-time updates (e.g., [STATUS PAGE URL], [SOCIAL MEDIA HANDLE], or support channels).
7. Close with a commitment to follow up and a brief reassurance about data safety if applicable.
8. Write in a tone that is [FORMAL / CONVERSATIONAL / TECHNICAL] to match the brand voice.
9. Keep the message under 300 words for email format and provide a shorter 80-word version suitable for SMS or in-app notification.
10. Avoid jargon unless the audience is technical. Use plain language that a non-technical customer can understand.
💡 Tips for Better Results
Always lead with honesty — customers trust brands that acknowledge problems quickly rather than minimizing them.
Prepare both a long-form email and a short SMS version so you can deploy across multiple channels immediately.
Update the communication every 1-2 hours during an active outage, even if there is no new information, to show customers you are actively working on it.
🎯 Use Cases
Customer support managers and communications teams should use this when a service disruption occurs and they need to quickly notify affected customers across email, SMS, or in-app channels.