Handling Misunderstandings Gracefully on International Video Calls

When the Conversation Breaks Down

Three minutes into a video call with a Singapore-based procurement team, a sales professional in Ho Chi Minh City realizes she has misunderstood the proposal. The other speaker said they would "park" the pricing question, but she heard it as a request to prepare a revised quote immediately. Meanwhile, the audio has started cutting out, and everyone is nodding as if the discussion is clear.

This is the moment many Vietnamese professionals try to hide. They keep listening, hoping the meaning will become obvious. Sometimes it does. More often, the misunderstanding grows quietly until someone asks for a decision.

Recovering from a misunderstanding is a separate workplace skill from understanding English in the first place. You may miss a word because of background noise, an unfamiliar accent, an idiom, a fast explanation, or a technical term. The professional response is not to pretend you heard everything. It is to signal the problem early, ask for the smallest clarification you need, and confirm the point before the conversation moves on.

In practice sessions with adult learners, this recovery sequence is often more useful than memorizing another list of business vocabulary.

Signal the Problem Without Apologizing for Existing

A useful clarification phrase does two things: it stops the conversation politely and tells the other person what kind of help you need. A long apology often does the opposite. It makes the moment sound more serious than it is and can cause you to lose your turn.

Try these openings:

• "Sorry, I missed the last part. Could you say that again?"
• "I caught the first point, but I missed the detail about the timeline."
• "The audio dropped for a moment. Could you repeat the decision?"
• "I'm not familiar with that expression. What does 'park this' mean here?"
• "Could you speak a little more slowly for that last point?"

Notice the difference between "My English is bad" and "I missed the last part." The second sentence describes a temporary communication problem. It gives your colleague a practical next step. It also avoids making the other person reassure you when the real need is simply repetition.

For Vietnamese professionals, "Sorry" can feel necessary because it softens a request. It is fine to use it once. The goal is not to remove politeness. The goal is to stop politeness from taking over the message.

Avoid stacking several softeners together:

"Sorry, I'm really sorry, maybe if you don't mind, could you possibly repeat that one more time?"

A shorter version is clearer:

"Sorry, I missed that. Could you repeat the last sentence?"

Ask for the Specific Piece You Missed

"I don't understand" is honest, but it is usually too broad. The other person does not know whether to repeat the whole explanation, define one term, or answer a hidden question. More precise requests reduce the amount of speaking both people have to do.

If you missed a word, ask about the word:

• "What does 'rollout' mean in this context?"
• "Did you say Thursday or Tuesday?"
• "Could you spell the client's name?"

If you missed the relationship between two ideas, ask for the connection:

• "How does that change the onboarding plan?"
• "Are you saying the delay is caused by the approval process?"
• "Which part should we prioritize first?"

If the explanation was too fast, do not ask someone to repeat everything automatically. Name the section:

• "Could you go back to the second step?"
• "I followed the background, but I lost the recommendation. What would you like us to do?"
• "Could you repeat the numbers from the last slide?"

This is especially important on international calls, where a request such as "Can you explain again?" may lead to another long explanation at the same speed. A narrower request gives the speaker a better chance of helping you.

Confirm Understanding Without Repeating the Whole Sentence

After clarification, many learners make a second mistake: they repeat the other person's entire explanation word for word. This can sound hesitant, and it uses valuable meeting time. Confirmation should test the decision, responsibility, or next action, not reproduce every sentence.

Use a short check such as:

• "So the deadline is Friday, correct?"
• "Just to confirm, you need the revised figures, not a new presentation."
• "Let me check I have the action right: I'll send the draft, and you'll review the pricing."
• "The priority is the Australian launch first, then the Singapore materials. Is that right?"
• "When you say 'later this week,' do you mean Thursday or Friday?"

There are three useful patterns here. First, confirm a concrete fact, such as a date or number. Second, confirm a contrast, especially when two similar options are involved. Third, confirm ownership, meaning who will do what next.

These checks do not make you sound incompetent. They show that you care about carrying out the correct action. In professional English, confidence is not always speaking without hesitation. It can also mean identifying the point that must be accurate.

One phrase deserves careful use: "Do you mean...?" It can sound direct, but it is often the fastest way to resolve ambiguity.

"Do you mean we should delay the launch, or continue with the current version while the issue is fixed?"

This gives the other person two possible meanings to choose from. It is more efficient than asking an open question and hoping the answer addresses your concern.

Handle Idioms, Accents, and Audio Problems Directly

Not every misunderstanding is a language knowledge problem. An Australian colleague may use a familiar expression differently from a colleague in Singapore. A speaker with a strong regional accent may be perfectly understandable in a quiet room but difficult to follow through a laptop microphone. It is useful to separate those causes because each needs a different response.

For an unfamiliar idiom, ask for the workplace meaning rather than the dictionary meaning:

• "When you say we should 'circle back,' do you mean we should discuss it again next week?"
• "In this project, what does 'quick win' refer to?"

For an accent or speed issue, avoid labeling the person. Describe the listening condition:

• "I'm having trouble hearing the last few words. Could you say that once more?"
• "The connection is breaking up slightly. Could you pause after each step?"
• "I want to make sure I heard the amount correctly. Was it fifteen or fifty?"

For a connection failure, say exactly what disappeared:

• "Your audio cut out after 'the revised contract.' What came next?"
• "I lost the final instruction. Could you put it in the chat as well?"
• "Could we pause for a moment? I can see the slides, but I cannot hear you clearly."

Asking someone to repeat a number, name, or deadline is not the same as asking them to repeat an entire explanation. On a difficult call, the smallest useful request is usually the strongest one.

A Recovery Routine for a Real Call

Consider the sales professional who hears that the procurement team will "park" pricing until the next meeting. She is unsure whether this means the team has rejected the current quote or simply wants to postpone that part of the discussion.

She could say:

"Sorry, I want to check one phrase. When you say we should park pricing, do you mean we should discuss it at the next meeting rather than change the quote today?"

The procurement lead clarifies that the quote should remain unchanged for now. The professional then confirms:

"Understood. I'll keep the current quote and prepare the implementation details for Thursday. Is that the right next step?"

This exchange is short because it follows a clear routine:

1. Identify the problem: "I want to check one phrase."
2. Ask about the exact ambiguity: "Do you mean...?"
3. Confirm the action: "I'll keep the current quote..."
4. Check ownership and timing: "Is that the right next step?"

NativeX practice focuses on this kind of sequence because the learner needs more than a correct sentence in isolation. They need to choose a recovery phrase while another person is waiting, then continue the conversation after the clarification. A language coach that talks with a learner every day can revisit the mistakes that keep recurring and rehearse the conversations a new job will demand.

When Clarification Is Not the Best Next Move

Asking for clarification is valuable, but it should not become a reflex that interrupts every unfamiliar phrase. Sometimes you can infer the meaning from the next sentence, the slide, or the decision being discussed. If the detail is not relevant to your work, you may not need to stop the meeting.

There is also a boundary: do not use "Just to confirm" to reopen a decision that was already settled, or to make another person repeat information you could check in the meeting notes. Use it when an error would affect your work, a deadline, a customer, or another person's responsibility.

When the discussion is moving quickly, write down the uncertain item and ask at the next natural pause. When the uncertainty affects an immediate decision, interrupt politely and ask at once. The skill is not asking more questions. It is judging which misunderstanding needs recovery now.

After the call, send a short written confirmation if the issue involved dates, numbers, or ownership:

"Thanks for clarifying on the call. My understanding is that I'll send the revised implementation plan by Thursday, while the current pricing remains unchanged."

This message is not a substitute for speaking up. It is a second check that protects everyone when the call was noisy or complicated.

NativeX pilots cover this kind of recovery practice directly. Email [email protected] to join the next cohort.