Remote Meetings: Phrases for Video Calls & Virtual Collaboration
5 exercises on essential video call phrases. Choose the most natural and professional option.
0 / 10 completed
1 / 10
A colleague starts speaking and nobody can hear them. You need to let them know quickly and politely. What do you say?
"You're on mute": This is the single most recognised phrase in remote work culture — short, unambiguous, and completely non-embarrassing. It names the problem and implies the fix without being condescending. Real examples: "Hey, you're on mute!" (informal daily standup); "Just to flag — you're on mute, could you unmute?" (client call). Option A is technically accurate but blunt and slightly accusatory. Option C is over-engineered for a simple fix — nobody wants a tutorial mid-meeting. Option D vaguely implies blame without giving actionable information. "You're on mute" is the universal shorthand; everyone knows exactly what to do.
2 / 10
You've just started sharing your screen during a demo. You want to confirm everyone can see it before continuing. What do you say?
"Can everyone see my screen?": Direct, inclusive, and the standard phrase in professional video calls. It invites a quick yes/no from the group and creates a natural pause before you proceed. Real examples: "Before I dive in — can everyone see my screen?"; "Can everyone see my screen? Give me a thumbs up if so." Option B is grammatically fine but feels overly formal and slightly awkward — nobody says "participants" in a casual standup. Option C is a reasonable workaround but slower; it adds a step and fragments attention. Option D is a statement, not a check — it doesn't invite confirmation, so you may spend five minutes demoing a blank screen. Option A is concise and universally understood.
3 / 10
You want to share a resource during a call without interrupting the presenter. How do you let the group know?
"I'll share the link in chat": Crisp, actionable, and the standard micro-phrase used during live calls. It signals what you're doing without making a production of it, letting the meeting flow. Real examples: "I'll share the link in chat — feel free to open it while we talk"; "One sec, I'll share the link in chat." Option A ("post the link") is also natural but slightly wordier — "share" is the more idiomatic verb in this context. Option C is wordy and almost instructional, as if the listener doesn't know what a chat window is. Option D breaks the flow entirely by deferring action; if something is useful right now, share it now. "I'll share the link in chat" is the leanest, most common form.
4 / 10
Someone asks you a question in a meeting but you need a moment to find the relevant document. What do you say?
"Could you give me a moment to pull that up?": Polite, professional, and signals a short, purposeful pause rather than confusion or unpreparedness. "Pull that up" is the standard idiom for opening/finding a document or screen during a live session. Real examples: "Bear with me — could you give me a moment to pull that up?"; "Sure, just give me a moment to pull that up." Option A ("Wait a second") is too casual and can sound abrupt in a professional setting. Option C is mechanical and over-explains the action. Option D suggests you don't have the information at all, which kills momentum; Option B signals you have it, just need a beat. It keeps the audience's confidence intact.
5 / 10
Two people started talking at the same time due to video call lag. You want to acknowledge it and move on gracefully. What do you say?
"Sorry, go ahead — I think we had a bit of overlap there": This phrase defuses the collision gracefully by yielding the floor and naming the cause lightly ("overlap") without technical jargon or blame. It keeps energy positive and conversation moving. Real examples: "Sorry, go ahead — I think we had a bit of overlap there with the lag"; "Ha, after you — we seem to have overlapped." Option A is accurate but clinical and slightly blaming — it points a finger at "lag" instead of moving on. Option C is overly technical and slows the meeting further. Option D is a procedural suggestion that changes the meeting format — useful sometimes, but not the natural first response to a momentary collision. Option B is the most human, efficient, and warm recovery phrase.
6 / 10
During a remote code review, Sarah says, 'This function is a bit confusing. Could you explain the logic?' David replies with: 'I've added detailed comments throughout the code to clarify the flow.' What's the best follow-up comment for David to make?
This scenario tests proactive communication during a code review. While acknowledging gratitude (option A) or offering general assistance (option D) isn't bad, David needs to delve deeper into Sarah's confusion. Option C directly asks for clarification, and option B is passive and doesn't address the core issue of understanding the logic.
7 / 10
You're leading a Slack channel discussing a new API endpoint. A developer, Mark, posts: 'Just tested this endpoint – seems to be returning 500 errors for some requests.' What's the most helpful and professional response you could send to Mark?
This question assesses response skills in Slack. Simply acknowledging (option A) or dismissing the issue (option C) is unhelpful. Option D suggests a generic troubleshooting step without seeking specific information. The best approach—asking for an example request (option B)—allows you to diagnose the problem efficiently and collaboratively.
8 / 10
During a standup meeting, you're asked about your progress on Task X. You reply: 'I'm still working through the initial setup and facing some challenges with integrating the database.' What is the most effective way to follow this up to ensure clarity and get support?
This tests proactive engagement in a standup. While simply stating progress (option A) or offering general support (option B) is polite, it doesn't address the core issue of needing assistance. Option C requests specific details about the challenges, prompting further discussion and potentially identifying solutions. Option D avoids acknowledging the need for help.
9 / 10
You're preparing a pull request with several changes to a complex module. Before submitting, you want to ensure your team is aware of the key modifications. Which statement would be most appropriate for your PR description?
This focuses on effective communication within a Pull Request description. A vague statement (option A) or overly casual phrasing (options C & D) doesn't convey the importance of the changes. Option B clearly highlights the magnitude and requests careful review, setting expectations for the reviewers.
10 / 10
During a video call, two developers, Alex and Ben, are discussing a design decision. They both start speaking at nearly the same time due to network latency. How should Alex respond to acknowledge Ben's input gracefully?
This addresses the issue of overlapping speech in video calls. Option A is passive and doesn't address the interruption. Option C suggests abandoning the discussion, which isn't ideal. Option D is overly assertive. The best approach—acknowledging Ben's input (option B)—shows respect and allows for a smoother conversation flow.
What will I practise in "Remote Meetings: Phrases for Video Calls & Virtual Collaboration"?
This module focuses on Phrasebook — real workplace phrasing you'll use on the job. It contains 10 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 10 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 Phrasebook exercise for?
It's aimed at IT professionals with working English who want to sound more natural and precise around phrasebook — 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 Phrasebook exercises?
See the Phrasebook 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.