Goal
Keep customers informed during an outage with short, honest updates at every stage, so support is not flooded with "is it down?" tickets.
Inputs
- Service and affected features: [for example payments and login, mobile app only]
- Who is affected: [all users, a region, one plan]
- Start time and time zone: [time]
- What is known so far: [cause, if known]
- Workaround, if any: [describe, or "none"]
- Next update interval: [for example every 30 minutes]
- Channels: [status page, email, X, in-app banner]
Messages to write
- Investigating: the problem is confirmed and being looked at
- Identified: the cause is found and a fix is in progress
- Monitoring: the fix is out and being watched
- Resolved: service is back, with start and end times
- Social post under 250 characters for the first alert
- Post-incident summary under 200 words: what happened, impact, what was done, what changes next
Check before answering
- Every update says which features are affected and when the next update comes.
- Times include the time zone.
- No update guesses a fix time unless one is given in the inputs.
- No blame on a named vendor or employee.
- Language is plain; no "degraded performance" without saying what customers will notice.
- The summary mentions any credit or compensation only if listed in the inputs.






