4 exercises — handling audio failures, bridging silence, managing connection problems, and sending professional follow-up summaries after remote calls.
0 / 39 completed
1 / 39
Your audio cuts out in the middle of you speaking during a video call. You can see people looking confused. What do you type in the chat?
Option C is the professional response to a technical failure in a remote meeting:
Apologises concisely: "Sorry — audio dropped" — brief; doesn't over-apologise Sets a time expectation: "Back in 30 seconds" — the group knows how long to wait Preserves continuity: Summarises in one line what you were saying — the team doesn't lose the thread while you reconnect
Why C is important: When audio fails mid-sentence, the most disruptive thing is ambiguity — nobody knows if you're still talking (but they can't hear), if you noticed the failure, or when you'll be back. A chat message resolves all three in seconds.
Remote meeting tech-failure phrases: • "Sorry — dropped. [One-line context]. Back in 30." • "Echo on my end — muting and reconnecting." • "Had a freeze — did you get the last 30 seconds?" • "Reconnecting — please continue, I'll catch up."
What not to say: • "brb" — too casual; tells the group nothing about what happened or when you'll return • "I have internet problems" — obvious; doesn't help the meeting move forward
2 / 39
You asked the group a question in a remote meeting and there is 20 seconds of silence. Nobody is responding. What do you say?
Option C handles remote silence with the wait → normalise → named invite technique:
Waits: "I'll give it another moment" — demonstrates patience; doesn't panic at silence Normalises: "it's a tricky question" — removes social pressure; everyone is allowed to not know instantly Gives a named prompt: "Pedro, what's your instinct?" — in remote meetings, a named invite almost always gets a response, because a direct question is much harder to ignore Lowers the bar: "doesn't have to be a final answer" — removes the pressure of needing to give the perfect response
Why remote silence is different from in-person silence: In a physical room, people can see each other hesitating — that visual feedback creates social pressure to speak. On a video call with cameras off (or low-quality video), people can hide behind silence much more easily. Named invites are essential in remote meetings.
Remote silence-breaking phrases: • "I'll give it another few seconds — it's a complex question." • "[Name], you've been thinking about this — what's your take?" • "Let's do a quick round — I'll call on each of you." • Polls/reactions: "Thumbs up if you agree with Option A, thumbs down for Option B."
3 / 39
A colleague's voice keeps breaking up and you're missing key information. Which phrase handles this most professionally?
Option C handles this technically and professionally:
"Sorry to interrupt" — acknowledges you're cutting in; respectful even in a frustrating situation "breaking up on our end" — key phrasing: "on our end" suggests the problem could be your connection, not necessarily theirs; removes blame "We're missing the last 30 seconds" — specific about what was lost, which helps them know where to resume Two options offered: repeat OR drop in chat — gives the speaker flexibility based on what's easier for them
Why "speak louder" is wrong: Audio breaking up is usually a bandwidth or codec issue — speaking louder doesn't fix packet loss. Asking someone to speak louder when they have a connection problem suggests you don't understand the technology.
Remote meeting audio issue phrases: • "[Name], you're breaking up — could you reconnect or drop it in the chat?" • "Audio quality dropped there — we missed [X]. Quick summary in text?" • "I think there might be an echo — could you mute and rejoin?" • "Sorry — we're getting some lag. Could you repeat from [last point]?"
4 / 39
A colleague you needed at a meeting couldn't attend. You want to send them a useful follow-up summary. Which message is best?
Option C is the model follow-up message for a missed meeting:
Acknowledges the absence gracefully: "since you couldn't be there" — no judgment, just context Leads with the decision: The most important information first — the decision and its rationale Includes a clear action item: "review the proposed schema and flag any concerns before Friday EOD" — Irina knows exactly what she needs to do and by when Provides the full notes link: "for full notes: [link]" — she can go deeper if needed without being forced to Opens the door: "Let me know if you have questions" — collaborative, not closed
Structure of a good meeting summary message: 1. One-line context ("you couldn't make it today") 2. The key decision(s) — with brief rationale 3. Any action items for the recipient specifically 4. Link to full notes 5. Offer to answer questions
What not to do: • Just send the link — people who missed the meeting need a summary, not a scavenger hunt • Lead with "you missed a great meeting" — irrelevant and slightly passive-aggressive
5 / 39
Sarah: "I'm having trouble with the audio during this call. It keeps cutting out."
Sarah is politely requesting assistance by framing the issue as an ongoing technical difficulty. Option A directly asks if others can hear her, which might put her on the defensive. Options C and D shift responsibility without acknowledging Sarah's specific problem. Asking for clarification is a standard professional approach.
6 / 39
You're submitting a PR with several changes related to the new authentication flow. During code review, Mark comments: 'I'm not sure I understand the rationale behind this approach. Can you elaborate?' What is the best response to Mark?
Mark is requesting clarification and a justification for the change. Option A dismisses the request with an unhelpful statement. Option C provides a professional explanation of the decision-making process. Options B and D are unprofessional and avoid addressing Mark's concern.
7 / 39
You're in a daily standup meeting and need to update the team on your progress. You've been blocked waiting for data from a third-party API. What would be an appropriate statement to make?
This statement directly addresses the blocker without over- or under-reporting progress. It's honest and informative, highlighting a dependency that needs attention. Options A and B are vague or misleading. Option D is inaccurate.
8 / 39
David sends you this Slack message: 'Just wanted to quickly recap the meeting notes – key decisions were X, Y, and Z.' You need to respond to acknowledge receipt. Which response is most appropriate?
Acknowledging receipt is a standard polite response in Slack. Option A expresses gratitude for the summary. Options B and D are overly inquisitive or demonstrate disinterest. Option C is impolite and dismissive.
9 / 39
You've just finished a complex API integration. You need to write a PR description that clearly explains the changes. Which sentence is most effective at the beginning of your description?
Starting with a concise statement of purpose—the core functionality being implemented—provides immediate context for reviewers. Option A clearly describes the primary goal. Options B and D are too technical or vague. Option C is celebratory and doesn't explain the changes.
10 / 39
Sarah: "I'm having trouble with the audio during this call. It keeps cutting out."
Sarah is politely requesting assistance by framing the issue as an ongoing technical difficulty. Option A directly asks if others can hear her, which might put her on the defensive. Options C and D shift responsibility without acknowledging Sarah's specific problem. Asking for clarification is a standard professional approach.
11 / 39
You're submitting a PR with several changes related to the new authentication flow. During code review, Mark comments: 'I'm not sure I understand the rationale behind this approach. Can you elaborate?' What is the best response to Mark?
Mark is requesting clarification and a justification for the change. Option A dismisses the request with an unhelpful statement. Option C provides a professional explanation of the decision-making process. Options B and D are unprofessional and avoid addressing Mark's concern.
12 / 39
You're in a daily standup meeting and need to update the team on your progress. You've been blocked waiting for data from a third-party API. What would be an appropriate statement to make?
This statement directly addresses the blocker without over- or under-reporting progress. It's honest and informative, highlighting a dependency that needs attention. Options A and B are vague or misleading. Option D is inaccurate.
13 / 39
David sends you this Slack message: 'Just wanted to quickly recap the meeting notes – key decisions were X, Y, and Z.' You need to respond to acknowledge receipt. Which response is most appropriate?
Acknowledging receipt is a standard polite response in Slack. Option A expresses gratitude for the summary. Options B and D are overly inquisitive or demonstrate disinterest. Option C is impolite and dismissive.
14 / 39
You've just finished a complex API integration. You need to write a PR description that clearly explains the changes. Which sentence is most effective at the beginning of your description?
Starting with a concise statement of purpose—the core functionality being implemented—provides immediate context for reviewers. Option A clearly describes the primary goal. Options B and D are too technical or vague. Option C is celebratory and doesn't explain the changes.
15 / 39
Sarah: "I'm having trouble with the audio during this call. It keeps cutting out."
Sarah is politely requesting assistance by framing the issue as an ongoing technical difficulty. Option A directly asks if others can hear her, which might put her on the defensive. Options C and D shift responsibility without acknowledging Sarah's specific problem. Asking for clarification is a standard professional approach.
16 / 39
You're submitting a PR with several changes related to the new authentication flow. During code review, Mark comments: 'I'm not sure I understand the rationale behind this approach. Can you elaborate?' What is the best response to Mark?
Mark is requesting clarification and a justification for the change. Option A dismisses the request with an unhelpful statement. Option C provides a professional explanation of the decision-making process. Options B and D are unprofessional and avoid addressing Mark's concern.
17 / 39
You're in a daily standup meeting and need to update the team on your progress. You've been blocked waiting for data from a third-party API. What would be an appropriate statement to make?
This statement directly addresses the blocker without over- or under-reporting progress. It's honest and informative, highlighting a dependency that needs attention. Options A and B are vague or misleading. Option D is inaccurate.
18 / 39
David sends you this Slack message: 'Just wanted to quickly recap the meeting notes – key decisions were X, Y, and Z.' You need to respond to acknowledge receipt. Which response is most appropriate?
Acknowledging receipt is a standard polite response in Slack. Option A expresses gratitude for the summary. Options B and D are overly inquisitive or demonstrate disinterest. Option C is impolite and dismissive.
19 / 39
You've just finished a complex API integration. You need to write a PR description that clearly explains the changes. Which sentence is most effective at the beginning of your description?
Starting with a concise statement of purpose—the core functionality being implemented—provides immediate context for reviewers. Option A clearly describes the primary goal. Options B and D are too technical or vague. Option C is celebratory and doesn't explain the changes.
20 / 39
Sarah: "I'm having trouble with the audio during this call. It keeps cutting out."
Sarah is politely requesting assistance by framing the issue as an ongoing technical difficulty. Option A directly asks if others can hear her, which might put her on the defensive. Options C and D shift responsibility without acknowledging Sarah's specific problem. Asking for clarification is a standard professional approach.
21 / 39
You're submitting a PR with several changes related to the new authentication flow. During code review, Mark comments: 'I'm not sure I understand the rationale behind this approach. Can you elaborate?' What is the best response to Mark?
Mark is requesting clarification and a justification for the change. Option A dismisses the request with an unhelpful statement. Option C provides a professional explanation of the decision-making process. Options B and D are unprofessional and avoid addressing Mark's concern.
22 / 39
You're in a daily standup meeting and need to update the team on your progress. You've been blocked waiting for data from a third-party API. What would be an appropriate statement to make?
This statement directly addresses the blocker without over- or under-reporting progress. It's honest and informative, highlighting a dependency that needs attention. Options A and B are vague or misleading. Option D is inaccurate.
23 / 39
David sends you this Slack message: 'Just wanted to quickly recap the meeting notes – key decisions were X, Y, and Z.' You need to respond to acknowledge receipt. Which response is most appropriate?
Acknowledging receipt is a standard polite response in Slack. Option A expresses gratitude for the summary. Options B and D are overly inquisitive or demonstrate disinterest. Option C is impolite and dismissive.
24 / 39
You've just finished a complex API integration. You need to write a PR description that clearly explains the changes. Which sentence is most effective at the beginning of your description?
Starting with a concise statement of purpose—the core functionality being implemented—provides immediate context for reviewers. Option A clearly describes the primary goal. Options B and D are too technical or vague. Option C is celebratory and doesn't explain the changes.
25 / 39
Sarah: "I'm having trouble with the audio during this call. It keeps cutting out."
Sarah is politely requesting assistance by framing the issue as an ongoing technical difficulty. Option A directly asks if others can hear her, which might put her on the defensive. Options C and D shift responsibility without acknowledging Sarah's specific problem. Asking for clarification is a standard professional approach.
26 / 39
You're submitting a PR with several changes related to the new authentication flow. During code review, Mark comments: 'I'm not sure I understand the rationale behind this approach. Can you elaborate?' What is the best response to Mark?
Mark is requesting clarification and a justification for the change. Option A dismisses the request with an unhelpful statement. Option C provides a professional explanation of the decision-making process. Options B and D are unprofessional and avoid addressing Mark's concern.
27 / 39
You're in a daily standup meeting and need to update the team on your progress. You've been blocked waiting for data from a third-party API. What would be an appropriate statement to make?
This statement directly addresses the blocker without over- or under-reporting progress. It's honest and informative, highlighting a dependency that needs attention. Options A and B are vague or misleading. Option D is inaccurate.
28 / 39
David sends you this Slack message: 'Just wanted to quickly recap the meeting notes – key decisions were X, Y, and Z.' You need to respond to acknowledge receipt. Which response is most appropriate?
Acknowledging receipt is a standard polite response in Slack. Option A expresses gratitude for the summary. Options B and D are overly inquisitive or demonstrate disinterest. Option C is impolite and dismissive.
29 / 39
You've just finished a complex API integration. You need to write a PR description that clearly explains the changes. Which sentence is most effective at the beginning of your description?
Starting with a concise statement of purpose—the core functionality being implemented—provides immediate context for reviewers. Option A clearly describes the primary goal. Options B and D are too technical or vague. Option C is celebratory and doesn't explain the changes.
30 / 39
Sarah: "I'm having trouble with the audio during this call. It keeps cutting out."
Sarah is politely requesting assistance by framing the issue as an ongoing technical difficulty. Option A directly asks if others can hear her, which might put her on the defensive. Options C and D shift responsibility without acknowledging Sarah's specific problem. Asking for clarification is a standard professional approach.
31 / 39
You're submitting a PR with several changes related to the new authentication flow. During code review, Mark comments: 'I'm not sure I understand the rationale behind this approach. Can you elaborate?' What is the best response to Mark?
Mark is requesting clarification and a justification for the change. Option A dismisses the request with an unhelpful statement. Option C provides a professional explanation of the decision-making process. Options B and D are unprofessional and avoid addressing Mark's concern.
32 / 39
You're in a daily standup meeting and need to update the team on your progress. You've been blocked waiting for data from a third-party API. What would be an appropriate statement to make?
This statement directly addresses the blocker without over- or under-reporting progress. It's honest and informative, highlighting a dependency that needs attention. Options A and B are vague or misleading. Option D is inaccurate.
33 / 39
David sends you this Slack message: 'Just wanted to quickly recap the meeting notes – key decisions were X, Y, and Z.' You need to respond to acknowledge receipt. Which response is most appropriate?
Acknowledging receipt is a standard polite response in Slack. Option A expresses gratitude for the summary. Options B and D are overly inquisitive or demonstrate disinterest. Option C is impolite and dismissive.
34 / 39
You've just finished a complex API integration. You need to write a PR description that clearly explains the changes. Which sentence is most effective at the beginning of your description?
Starting with a concise statement of purpose—the core functionality being implemented—provides immediate context for reviewers. Option A clearly describes the primary goal. Options B and D are too technical or vague. Option C is celebratory and doesn't explain the changes.
35 / 39
Sarah: "I'm having trouble with the audio during this call. It keeps cutting out."
Sarah is politely requesting assistance by framing the issue as an ongoing technical difficulty. Option A directly asks if others can hear her, which might put her on the defensive. Options C and D shift responsibility without acknowledging Sarah's specific problem. Asking for clarification is a standard professional approach.
36 / 39
You're submitting a PR with several changes related to the new authentication flow. During code review, Mark comments: 'I'm not sure I understand the rationale behind this approach. Can you elaborate?' What is the best response to Mark?
Mark is requesting clarification and a justification for the change. Option A dismisses the request with an unhelpful statement. Option C provides a professional explanation of the decision-making process. Options B and D are unprofessional and avoid addressing Mark's concern.
37 / 39
You're in a daily standup meeting and need to update the team on your progress. You've been blocked waiting for data from a third-party API. What would be an appropriate statement to make?
This statement directly addresses the blocker without over- or under-reporting progress. It's honest and informative, highlighting a dependency that needs attention. Options A and B are vague or misleading. Option D is inaccurate.
38 / 39
David sends you this Slack message: 'Just wanted to quickly recap the meeting notes – key decisions were X, Y, and Z.' You need to respond to acknowledge receipt. Which response is most appropriate?
Acknowledging receipt is a standard polite response in Slack. Option A expresses gratitude for the summary. Options B and D are overly inquisitive or demonstrate disinterest. Option C is impolite and dismissive.
39 / 39
You've just finished a complex API integration. You need to write a PR description that clearly explains the changes. Which sentence is most effective at the beginning of your description?
Starting with a concise statement of purpose—the core functionality being implemented—provides immediate context for reviewers. Option A clearly describes the primary goal. Options B and D are too technical or vague. Option C is celebratory and doesn't explain the changes.
What will I practise in "Remote Meeting Challenges"?
This module focuses on Meetings & Collaboration — real workplace phrasing you'll use on the job. It contains 39 scenario-based multiple-choice questions with instant feedback.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account or sign-up required.
How many questions does this exercise have?
This module includes 39 questions. Each one gives an immediate right/wrong result plus a full explanation of the correct phrasing.
What happens if I answer a question incorrectly?
You'll see the correct answer highlighted straight away, along with a plain-English explanation of why it's right and why the other options don't fit — mistakes are part of the learning here.
Can I retry the exercise if I want a better score?
Yes — use the 'Try again' button on the results screen to reset your score and go through the questions again. There's no limit on attempts.
Who is this Meetings & Collaboration exercise for?
It's aimed at IT professionals with working English who want to sound more natural and precise around meetings & collaboration — useful whether you're preparing for real conversations at work or just building confidence with the vocabulary.
Do I need an account to track my progress?
No account is needed. Your progress through the exercise is tracked locally in your browser for the current session, and you can replay the module at any time.
How is this different from reading a blog article?
This exercise is an interactive drill that tests and reinforces specific phrasing through multiple-choice questions with instant feedback, while blog articles explain concepts and vocabulary in prose. The two work well together.
Where can I find more Meetings & Collaboration exercises?
See the Meetings & Collaboration hub for more modules like this one, or browse the full Exercises page for other IT-English topics.
Can I complete this exercise on my phone?
Yes — every exercise on CoderSlingo is fully responsive and works on phones and tablets, so you can practise anywhere.