Status Page and Customer Incident Communication (English)
Practice the English used for public status pages and customer-facing incident updates: translating technical failures into clear, professional customer communication.
0 / 8 completed
1 / 8
What is the most important principle when writing customer-facing incident communication?
Customer incident communication must be timely (early, before customers report it), clear (no jargon), honest (acknowledge real impact), and regular (silence is worse than 'we are still investigating').
2 / 8
Which sentence is the best example of a first incident notification on a status page?
The first notification should: acknowledge the problem in plain language, describe the user impact (unable to sign in), and commit to a next update time. Technical internal terms (P1, 503, auth endpoint) belong in internal channels.
3 / 8
What is the correct status page progression for an incident?
Standard incident lifecycle on status pages: Investigating (we see a problem), Identified (we know the cause), Monitoring (fix deployed, watching), Resolved (confirmed fixed). Each state change should include an update.
4 / 8
How would you write the 'Identified' status update?
An 'Identified' update tells customers: what the problem is (in plain language), when it started, what the fix is, and when they can expect resolution. It builds confidence that the team is in control.
5 / 8
What is a 'postmortem' and how should it be communicated to customers?
Public postmortems demonstrate accountability and build trust. Companies like Cloudflare and GitLab publish detailed incident reports. They describe the timeline, root cause, impact, and concrete remediation steps.
6 / 8
Which sentence is an example of professional 'Resolved' status update language?
A resolved update includes: confirmation of resolution, the time resolved, expected behavior (sign in normally), promise of follow-up (incident report), and an apology. This closes the loop with customers professionally.
7 / 8
How should an SLA breach be communicated to affected customers?
SLA breaches require proactive, personalized communication. Waiting for customers to raise it violates the spirit of the SLA. Proactive communication with concrete remediation (credits) demonstrates accountability.
8 / 8
What is 'maintenance window' language on a status page?
Maintenance windows are communicated in advance (24-72h notice) with clear start/end times, expected impact (e.g., 'login will be unavailable for up to 10 minutes'), and contact info for urgent issues.