Customer Outage Announcement — Writing Vocabulary
Write professional, empathetic outage announcements for customers.
0 / 26 completed
1 / 26
Which element is essential in a major outage announcement email to customers?
An outage announcement must clearly state what is affected, the current timeline, and what actions customers should or should not take — this is what they need.
2 / 26
Which phrase is the most appropriate opening for a major outage announcement?
A clear, direct opening ('We are experiencing a significant service disruption') immediately communicates the key fact. Vague phrases like 'inconvenience' understate the impact.
3 / 26
What is 'structured apology language' in crisis communication?
Structured apology language acknowledges impact ('We understand this has affected your work'), takes responsibility without deflecting, and commits to specific action.
4 / 26
When should you send an outage announcement email to customers?
Customers should be notified as soon as a significant impact is detected — even without root cause identified. Delayed communication erodes trust.
5 / 26
Which closing sentence is most appropriate for an outage announcement?
A clear closing gives a specific next-update time and a support contact — setting expectations and maintaining communication continuity.
6 / 26
John from the Incident Management team just posted this comment on a PR describing an outage impacting the user authentication service:
"@Sarah, can you please add more detail about the root cause? We need to understand why this happened and what steps are being taken to prevent recurrence. Also, include estimated time to resolution."This scenario requires understanding how developers communicate during an outage. The comment isn't simply asking for information; it frames the request as part of an investigation into the 'root cause,' which is standard practice in incident management. Importantly, it also requests a timeline (estimated time to resolution), demonstrating awareness of customer expectations and proactive communication. Option A misinterprets the tone as lacking proactivity when it's actually focused on critical troubleshooting steps.
7 / 26
Sarah from the DevOps team is drafting a PR description for a widespread outage affecting the payment processing API. She's struggling to articulate the impact clearly and concisely to her team. Here's what she's drafted:
"API impacted. Users experiencing issues. Investigating."This option is correct because Sarah needs to move beyond a simple statement of fact and provide context. The PR description should clearly state the *severity* of the outage (e.g., 'significant impact on users'), identify *which users* are affected, and briefly outline the steps being taken. Simply stating 'API impacted' doesn't convey this vital information to her team who need to prioritize and address the problem effectively; options B, C, and D all fail to address this core need.
8 / 26
David posted this comment on a PR regarding a recent outage affecting the user profile service:
"Okay team, we've identified a transient spike in database queries as the likely cause. We're implementing caching and rate limiting to mitigate future occurrences. Let's monitor performance closely over the next hour."The correct answer highlights that David's comment is appropriate because it provides concrete technical details (database queries, caching, rate limiting) and outlines clear actions being taken. A key element of developer communication during outages is to be both technically accurate and demonstrate a proactive approach. Options A and C miss this focus, while option D incorrectly frames the comment as lacking empathy – David's response *does* acknowledge the issue in a technical manner.
9 / 26
Mark from Support is drafting a Slack message to update the engineering team about a critical outage affecting the user dashboard. He wants to convey urgency and provide a clear next step. Which of the following options best reflects professional communication in this situation?
Option A: "Hey team, dashboard down! Fix it ASAP."
Option B: "We're experiencing an outage impacting the user dashboard. The On-Call engineer,
David, is investigating and working to restore service. Please stand by for updates."
Option C: "Dashboard issues reported. Running diagnostics. Will let you know when it's fixed."
Option D: "Just a heads up, the dashboard is temporarily unavailable. We're aware and monitoring the situation."
The correct answer, Option B, demonstrates professional communication by acknowledging the issue clearly, identifying who is responsible (
David), outlining their actions (investigating and restoring service), and requesting patience with updates. Options A and C are too informal and lack crucial details for conveying urgency to a technical audience. Option D is vague and doesn't provide any information about next steps or responsibility.10 / 26
John from the Incident Management team just posted this comment on a PR describing an outage impacting the user authentication service:
"@Sarah, can you please add more detail about the root cause? We need to understand why this happened and what steps are being taken to prevent recurrence. Also, include estimated time to resolution."This scenario requires understanding how developers communicate during an outage. The comment isn't simply asking for information; it frames the request as part of an investigation into the 'root cause,' which is standard practice in incident management. Importantly, it also requests a timeline (estimated time to resolution), demonstrating awareness of customer expectations and proactive communication. Option A misinterprets the tone as lacking proactivity when it's actually focused on critical troubleshooting steps.
11 / 26
Sarah from the DevOps team is drafting a PR description for a widespread outage affecting the payment processing API. She's struggling to articulate the impact clearly and concisely to her team. Here's what she's drafted:
"API impacted. Users experiencing issues. Investigating."This option is correct because Sarah needs to move beyond a simple statement of fact and provide context. The PR description should clearly state the *severity* of the outage (e.g., 'significant impact on users'), identify *which users* are affected, and briefly outline the steps being taken. Simply stating 'API impacted' doesn't convey this vital information to her team who need to prioritize and address the problem effectively; options B, C, and D all fail to address this core need.
12 / 26
David posted this comment on a PR regarding a recent outage affecting the user profile service:
"Okay team, we've identified a transient spike in database queries as the likely cause. We're implementing caching and rate limiting to mitigate future occurrences. Let's monitor performance closely over the next hour."The correct answer highlights that David's comment is appropriate because it provides concrete technical details (database queries, caching, rate limiting) and outlines clear actions being taken. A key element of developer communication during outages is to be both technically accurate and demonstrate a proactive approach. Options A and C miss this focus, while option D incorrectly frames the comment as lacking empathy – David's response *does* acknowledge the issue in a technical manner.
13 / 26
Mark from Support is drafting a Slack message to update the engineering team about a critical outage affecting the user dashboard. He wants to convey urgency and provide a clear next step. Which of the following options best reflects professional communication in this situation?
Option A: "Hey team, dashboard down! Fix it ASAP."
Option B: "We're experiencing an outage impacting the user dashboard. The On-Call engineer,
David, is investigating and working to restore service. Please stand by for updates."
Option C: "Dashboard issues reported. Running diagnostics. Will let you know when it's fixed."
Option D: "Just a heads up, the dashboard is temporarily unavailable. We're aware and monitoring the situation."
The correct answer, Option B, demonstrates professional communication by acknowledging the issue clearly, identifying who is responsible (
David), outlining their actions (investigating and restoring service), and requesting patience with updates. Options A and C are too informal and lack crucial details for conveying urgency to a technical audience. Option D is vague and doesn't provide any information about next steps or responsibility.14 / 26
John from the Incident Management team just posted this comment on a PR describing an outage impacting the user authentication service:
"@Sarah, can you please add more detail about the root cause? We need to understand why this happened and what steps are being taken to prevent recurrence. Also, include estimated time to resolution."This scenario requires understanding how developers communicate during an outage. The comment isn't simply asking for information; it frames the request as part of an investigation into the 'root cause,' which is standard practice in incident management. Importantly, it also requests a timeline (estimated time to resolution), demonstrating awareness of customer expectations and proactive communication. Option A misinterprets the tone as lacking proactivity when it's actually focused on critical troubleshooting steps.
15 / 26
Sarah from the DevOps team is drafting a PR description for a widespread outage affecting the payment processing API. She's struggling to articulate the impact clearly and concisely to her team. Here's what she's drafted:
"API impacted. Users experiencing issues. Investigating."This option is correct because Sarah needs to move beyond a simple statement of fact and provide context. The PR description should clearly state the *severity* of the outage (e.g., 'significant impact on users'), identify *which users* are affected, and briefly outline the steps being taken. Simply stating 'API impacted' doesn't convey this vital information to her team who need to prioritize and address the problem effectively; options B, C, and D all fail to address this core need.
16 / 26
David posted this comment on a PR regarding a recent outage affecting the user profile service:
"Okay team, we've identified a transient spike in database queries as the likely cause. We're implementing caching and rate limiting to mitigate future occurrences. Let's monitor performance closely over the next hour."The correct answer highlights that David's comment is appropriate because it provides concrete technical details (database queries, caching, rate limiting) and outlines clear actions being taken. A key element of developer communication during outages is to be both technically accurate and demonstrate a proactive approach. Options A and C miss this focus, while option D incorrectly frames the comment as lacking empathy – David's response *does* acknowledge the issue in a technical manner.
17 / 26
Mark from Support is drafting a Slack message to update the engineering team about a critical outage affecting the user dashboard. He wants to convey urgency and provide a clear next step. Which of the following options best reflects professional communication in this situation?
Option A: "Hey team, dashboard down! Fix it ASAP."
Option B: "We're experiencing an outage impacting the user dashboard. The On-Call engineer,
David, is investigating and working to restore service. Please stand by for updates."
Option C: "Dashboard issues reported. Running diagnostics. Will let you know when it's fixed."
Option D: "Just a heads up, the dashboard is temporarily unavailable. We're aware and monitoring the situation."
The correct answer, Option B, demonstrates professional communication by acknowledging the issue clearly, identifying who is responsible (
David), outlining their actions (investigating and restoring service), and requesting patience with updates. Options A and C are too informal and lack crucial details for conveying urgency to a technical audience. Option D is vague and doesn't provide any information about next steps or responsibility.18 / 26
John from the Incident Management team just posted this comment on a PR describing an outage impacting the user authentication service:
"@Sarah, can you please add more detail about the root cause? We need to understand why this happened and what steps are being taken to prevent recurrence. Also, include estimated time to resolution."This scenario requires understanding how developers communicate during an outage. The comment isn't simply asking for information; it frames the request as part of an investigation into the 'root cause,' which is standard practice in incident management. Importantly, it also requests a timeline (estimated time to resolution), demonstrating awareness of customer expectations and proactive communication. Option A misinterprets the tone as lacking proactivity when it's actually focused on critical troubleshooting steps.
19 / 26
Sarah from the DevOps team is drafting a PR description for a widespread outage affecting the payment processing API. She's struggling to articulate the impact clearly and concisely to her team. Here's what she's drafted:
"API impacted. Users experiencing issues. Investigating."This option is correct because Sarah needs to move beyond a simple statement of fact and provide context. The PR description should clearly state the *severity* of the outage (e.g., 'significant impact on users'), identify *which users* are affected, and briefly outline the steps being taken. Simply stating 'API impacted' doesn't convey this vital information to her team who need to prioritize and address the problem effectively; options B, C, and D all fail to address this core need.
20 / 26
David posted this comment on a PR regarding a recent outage affecting the user profile service:
"Okay team, we've identified a transient spike in database queries as the likely cause. We're implementing caching and rate limiting to mitigate future occurrences. Let's monitor performance closely over the next hour."The correct answer highlights that David's comment is appropriate because it provides concrete technical details (database queries, caching, rate limiting) and outlines clear actions being taken. A key element of developer communication during outages is to be both technically accurate and demonstrate a proactive approach. Options A and C miss this focus, while option D incorrectly frames the comment as lacking empathy – David's response *does* acknowledge the issue in a technical manner.
21 / 26
Mark from Support is drafting a Slack message to update the engineering team about a critical outage affecting the user dashboard. He wants to convey urgency and provide a clear next step. Which of the following options best reflects professional communication in this situation?
Option A: "Hey team, dashboard down! Fix it ASAP."
Option B: "We're experiencing an outage impacting the user dashboard. The On-Call engineer,
David, is investigating and working to restore service. Please stand by for updates."
Option C: "Dashboard issues reported. Running diagnostics. Will let you know when it's fixed."
Option D: "Just a heads up, the dashboard is temporarily unavailable. We're aware and monitoring the situation."
The correct answer, Option B, demonstrates professional communication by acknowledging the issue clearly, identifying who is responsible (
David), outlining their actions (investigating and restoring service), and requesting patience with updates. Options A and C are too informal and lack crucial details for conveying urgency to a technical audience. Option D is vague and doesn't provide any information about next steps or responsibility.22 / 26
Elena, a SRE, is drafting an API response to communicate the outage affecting the inventory service. The response needs to be concise and informative for developers who need to integrate with the affected system. Which of the following options best reflects this requirement?
HTTP/1.1 503 Service Unavailable
Content-Type: application/json
{"status": "error", "message": "Inventory service unavailable."}The correct response uses a standard HTTP status code (503) and provides a clear, concise error message. It avoids vague terms like 'warning' or subjective descriptions ('temporary outage'). Option A is incorrect because it indicates success when the service is unavailable. The key here is to align with RESTful API conventions for error responses.
23 / 26
During a live outage of the user authentication service, Ben from Incident Management needs to update the team during a daily standup. Which of the following statements would be MOST effective in conveying the severity and next steps?
'We're seeing some intermittent issues with login rates.'
The best option directly states the outage's impact (all users impacted) and outlines immediate actions (investigation & workaround). Options B and C are too vague or suggest unrelated problems. Option D is far too understated for a critical outage situation requiring immediate attention.
24 / 26
Maria, a developer reviewing a PR that resolves an outage in the payment processing system, notices the commit message. The message reads: 'Fixed bug'. What additional information should Maria request to fully understand the situation and ensure proper monitoring?
'Can you elaborate on the nature of the bug?'
The most crucial information is the root cause and preventative measures. Simply stating 'fixed bug' doesn't provide context for monitoring or understanding potential recurrence. Knowing *why* the bug occurred is essential for proactive mitigation and preventing future outages.
25 / 26
Liam from Support is drafting a Slack message to inform the engineering team about a critical outage affecting the user dashboard. He needs to quickly communicate the problem and request assistance. Which of the following messages best achieves this?
'Hey team, we're experiencing some issues with the user dashboard. Please investigate.'
This option uses strong language ('URGENT') and clearly states the problem (dashboard down) and the required action (support). Option A is too vague; options B and C imply a less severe issue, while option D suggests planned downtime.
26 / 26
Chloe is writing a PR description for an outage affecting the shipping API. She's trying to explain the impact to her team. Which of the following phrases BEST describes the effect on downstream systems?
'The system was temporarily unavailable.'
This option accurately describes the cascading effect of an outage – delayed and failed responses in connected services. It highlights the *consequences* of the disruption, which is vital for developers needing to understand how to handle the situation. Options A and B are too vague; Option D distracts from the core issue.
Frequently Asked Questions
What does the "Customer Outage Announcement — Writing Vocabulary" exercise cover?
Write professional, empathetic outage announcements for customers.
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.
How many questions are in "Customer Outage Announcement — Writing Vocabulary"?
This exercise has 26 questions. Each one gives instant feedback with an explanation, so you can see exactly why an answer is right or wrong.
Do I need to create an account to save my progress?
No account is required. The progress bar and score are tracked in your browser for the current session -- the exercise is designed to be a quick, repeatable drill rather than something you resume later.
What happens if I get an answer wrong?
You'll see the correct answer highlighted immediately, along with a short explanation of why it's correct. Wrong answers aren't penalized beyond your score, and you can keep going through every question.
How is this exercise different from reading an article?
Articles explain vocabulary and concepts through prose, while exercises like this one are interactive drills -- multiple-choice questions -- that test and reinforce your recall of specific terms and phrasing.
Can I retry this exercise?
Yes -- use the "Try again" button on the results screen to reset your score and go through all the questions again from the start.
Where can I find more External Crisis Communication exercises?
Browse the full External Crisis Communication hub for related drills, or check the site-wide exercises index for other IT English topics.
Is this exercise suitable for beginners?
This exercise assumes basic familiarity with IT terminology. If a term feels unfamiliar, check the site Glossary for a plain-English definition before attempting the questions.
How often is new content like this published?
New exercises are added regularly across all categories, alongside new vocabulary sets and articles. Check back on the exercises hub to see what's new.