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 / 15 completed
1 / 15
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 / 15
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 / 15
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 / 15
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 / 15
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 / 15
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 / 15
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 / 15
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.
9 / 15
Alex from Support is drafting a Slack message to inform the team about a degraded API endpoint. Which of the following options best reflects the tone and information he should include?
Alex should prioritize clear, factual communication. Option 1 describes the issue and its impact (user login times) without assigning blame. Options 2 is professional, providing details about monitoring and investigation. Options 3 and 4 are overly critical and lack essential information for a team response.
10 / 15
Alex from Support is drafting a Slack message to inform the team about a degraded API endpoint. Which of the following options best reflects the tone and information he should include?
Alex should prioritize clear, factual communication. Option 1 describes the issue and its impact (user login times) without assigning blame. Options 2 is professional, providing details about monitoring and investigation. Options 3 and 4 are overly critical and lack essential information for a team response.
11 / 15
Sarah, a Developer Advocate, is writing a PR description to announce an outage affecting the user authentication service. Which of the following statements best reflects the appropriate level of detail and tone for this communication?
The key principle here is transparency. A PR description for an outage needs a brief summary of the impact and a clear indication of what's being done to resolve it. Providing technical details in a public-facing document isn't necessary; focus on communicating the *effect* on users and the team's response.
12 / 15
You are drafting an automated status page update when a critical database server has failed. Which of the following sentences is MOST appropriate for capturing this event in the 'Incident Status' field?
Clear and concise language is paramount in incident communications. This status update needs to immediately convey the severity (Critical), what failed (Database Server Failure), and the impact (Impacting Production Services). Avoid jargon or overly technical descriptions that won't be understood by non-technical users.
13 / 15
Mark from Operations is preparing a Slack message to inform the team about a planned maintenance window for updating a key API endpoint. Which of the following options presents the MOST effective way to communicate this information?
Providing specific details is crucial for minimizing disruption and managing expectations. Mark's message should clearly state the endpoint being updated, the exact date and time of the maintenance window, and an estimate of the downtime users can anticipate. This allows teams to prepare and users to plan accordingly.
14 / 15
Emily, a Customer Support Engineer, is responding to a customer's inquiry about an ongoing incident impacting their application. Which of the following phrases BEST reflects her response?
Empathy and proactive communication are key to managing customer frustration during outages. Emily's response acknowledges the customer's experience, assures them that resolution is a priority, and provides a clear commitment to regular updates – demonstrating transparency and keeping the customer informed.
15 / 15
David, a Senior Engineer, is drafting a postmortem report following an incident. Which of the following statements BEST describes its primary purpose and intended audience?
Postmortems aren't about blame; they're about learning. The primary goal is to analyze *what* went wrong, *why*, and *how* to improve processes and systems – providing actionable insights for the development team. This report should be for internal consumption only.
What will I practise in "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.
How many exercises are in this module?
This module has 15 multiple-choice exercises, each with instant feedback and a full explanation of the correct answer.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account, sign-up, or paywall.
Do I need to create an account to do these exercises?
No account is required. Just click an option to answer — your score for this session is tracked automatically in the progress bar above.
What happens if I choose the wrong answer?
You'll immediately see which answer was correct, plus a full explanation covering the vocabulary and reasoning behind it — mistakes are where most of the learning happens.
Can I retry the exercises if I want a higher score?
Yes — use the "Try again" button on the results screen to reset and go through all the questions again.
Is my progress saved if I close the page?
No. Progress is tracked only for your current visit; reloading or leaving the page resets the counter. This keeps the exercise simple and account-free.
Where can I find more Incident Response exercises?
Browse the full Incident Response hub for related drills, or check the "Next up" link below to continue with a connected topic.
How is this different from reading an article on the same topic?
Articles explain vocabulary and concepts in prose; this exercise tests and reinforces that vocabulary through active recall with immediate feedback — the two work best together.
Who writes these exercises?
Every exercise is written by the CoderSlingo team, drawing on real workplace English used in IT roles, then reviewed for accuracy and clarity.