Customer Support Task
Publish incident updates
Assign one communication owner and maintain one current status with impact, phase, and next-update time.
“Duplicate replies consume repair capacity and leave users uncertain about whether the incident is known.”
Outcome
The result to aim for
Give affected users one reliable status through investigating, identified, monitoring, and resolved phases.
Best practices
- Assign the technical incident lead and a separate communication owner when staffing allows.
- Create templates for investigating, identified, monitoring and resolved incidents. Each template must prompt for the affected service, observed impact, confirmed facts, current action and next-update time.
- After the required approvals, publish at the promised time even when the phase is unchanged. Move phases only on confirmed evidence. When the incident is resolved, state the restored service, monitoring state and any approved follow-up.
- Confirm that every update identifies the affected service, observed impact, phase, and next-update time until resolution.
- Use the organisation’s security, legal, regulatory, and contractual incident-notification process where required.
Related sources
Further information
- Documented guidance: Reddit r/SaaS: How do you handle incident communication when your SaaS goes down?
- Related guidance: Atlassian: Learn incident communication with Statuspage