Practice writing external incident updates, status page entries, and resolution summaries for customers.
0 / 10 completed
1 / 10
An ongoing incident is affecting 30% of API calls. Which status page update is most appropriate?
Status updates should include impact scope, current investigation status, who is working on it, and when the next update is expected.
2 / 10
The incident is resolved after 45 minutes. How do you close the status page incident?
Resolution notices should specify the resolution time, confirm normal operation, and set expectations for a post-incident review.
3 / 10
A customer emails asking whether the incident affected their data. How do you respond?
Data safety questions require a direct, clear statement: what the incident was limited to and explicit confirmation that data was not affected.
4 / 10
Which phrase best describes the current state of an incident that is partially mitigated?
Partial mitigation updates should quantify the improvement, distinguish mitigation from resolution, and confirm ongoing investigation.
5 / 10
You need to describe the impact of the incident in business terms for a customer executive. Which sentence is best?
Business-language incident communication describes impact in user-facing terms (transaction failures), duration, and the key customer concern (billing).
6 / 10
Sarah, a Support Engineer, is drafting a Slack message to update the team about an ongoing incident impacting user authentication. The current status is 'investigating'. Which of the following messages is most professional and informative? /slack/incident-update
Option B provides a clear and concise update, acknowledging the problem and setting expectations for delays. It's more informative than simply stating 'we're looking into it,' which lacks detail and doesn't manage user expectations effectively. Options A and D are too informal for internal communication, while option C is overly technical for a general team update.
7 / 10
You're reviewing a code change that fixed an incident causing intermittent errors in the payment processing microservice. The commit message reads: 'Fixed bug'. What additional information should be included to provide context for other developers and future troubleshooting? //code-review
Option A provides crucial context by stating that the issue was 'critical' and related to 'transaction failures'. This immediately flags the severity and the affected area. The other options are too vague and don't convey the impact or technical details needed for effective collaboration. Including specific terminology like 'race condition' isn't always necessary in a commit message – focus on the *effect* of the change.
8 / 10
You're submitting a pull request to resolve an incident where users couldn't access the reporting dashboard. The PR description should clearly communicate the problem and solution. Which of the following descriptions is MOST effective? //pr-description
Option C is the strongest because it clearly states the problem (users couldn't access the dashboard), describes the root cause (database connection issue), and details the solution (retry logic). This provides valuable context for reviewers and future troubleshooting. Options A, B, and D are too generic and don't explain *why* the change was made.
9 / 10
The API endpoint for monitoring incident status returns the following JSON: { "status": "active", "severity": "high", "description": "Service degradation impacting user login.", "resolution_time": 90}. A customer support agent needs to quickly understand the situation. Which single sentence best summarizes this response for a client? //api-response
Option B provides a concise and accurate summary of the key details: 'Login services are currently degraded.' This is more informative than simply stating 'the service is experiencing a high severity issue' (option A), which lacks specifics. Option C emphasizes the duration, while option D is too vague.
10 / 10
During your daily stand-up, you need to update the team on an incident that's being addressed. The incident caused a brief outage of the image upload service. Which statement would be most appropriate for your update? //standup
Option B provides a balanced update – acknowledging the outage, stating that you're investigating, and conveying the seriousness of the issue without alarming the team. Options A and D are too vague for a stand-up setting. Option C is overly dramatic and doesn't offer any information about the current state.
This exercise, "Customer-Facing Incident Communication", tests your understanding of technical support vocabulary and phrasing through 10 multiple-choice questions drawn from real workplace scenarios.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is completely free — no account, sign-up, or payment required.
How many questions does this exercise have?
This exercise has 10 questions. Each one presents a realistic sentence or scenario with multiple-choice options and an explanation once you answer.
What happens after I answer a question?
You'll see immediate feedback showing whether your answer was correct, along with a short explanation of why — then a button to move to the next question.
Can I retry the exercise if I get questions wrong?
Yes. Once you reach the results screen, click "Try again" to reset your answers and go through the exercise from the start as many times as you like.
Do I need to create an account to take this exercise?
No account is needed. Your answers are scored in your browser during the session — nothing is saved to a server, so you can jump straight in.
Is my progress saved if I leave the page?
No — progress within an exercise resets if you navigate away or reload. Each exercise is short enough to complete in a few minutes in one sitting.
Who is this Technical Support exercise for?
It's designed for IT professionals and learners who want to sound natural discussing technical support topics in English — useful for meetings, documentation, interviews, and day-to-day communication with English-speaking teams.
How is this different from reading a glossary or blog article?
Exercises like this one are active recall drills — you have to choose the correct term or phrasing yourself, which builds retention faster than passively reading a definition.
Where can I find more Technical Support exercises?
Browse the full Technical Support exercises hub for more practice, or explore other exercise categories covering vocabulary, grammar, interviews, and workplace communication.