How to translate a client call in real time
For a scheduled high-value call, book an interpreter. For the routine calls that currently happen in approximate English, AI translation is the realistic option — load a glossary of your product terms first, and agree with the client beforehand that translation is running.
The decision is mostly about which call this is. A first meeting with a prospect worth a year’s quota is a different problem from the fourth support check-in this month.
For the high-stakes call
Book a human interpreter. Two weeks’ notice for common language pairs, and brief them with your deck, a glossary and the names of everyone attending.
The reason is not accuracy in the narrow sense — it is judgement. An interpreter hears an ambiguous phrase, resolves it from context or flags it, and reads the room. In a negotiation, that is the whole job.
For the routine call
These are the calls that currently happen in approximate English with nobody translating anything, because booking an interpreter for a Tuesday check-in is not realistic. AI translation is competing with nothing, not with an interpreter, and that changes the standard it has to meet.
Three things to do before the first one:
Load a glossary. Product names, SKUs, contract terms, anything domain-specific. This is the highest-leverage step by a distance — general translation handles ordinary speech well and your product vocabulary badly.
Tell the client. Not just for consent and recording law, which vary by jurisdiction and matter. Also because a client who knows translation is running will pause at clause boundaries instead of talking over the gap, and the quality difference is large.
Agree a fallback. If it fails mid-call, do you switch to English, reschedule, or continue and send a written summary? Decide before, not during.
Change how you run the call
- Pause at clause boundaries. Not mid-sentence — a trailing sentence gives the translation nothing to close on.
- Put numbers, dates and names in the chat. These are the highest-consequence items and the ones most often mangled. Typing a price takes two seconds.
- Confirm commitments explicitly. “So to confirm: forty units, delivered by the fifteenth, at the price we discussed.” Say it, then type it.
- Send a written summary afterwards in both languages. This is where the actual protection against misunderstanding lives.
What your platform will do
- Zoom produces translated captions only — no translated audio. Workable for a call where both sides read comfortably, poor for a negotiation.
- Teams Interpreter does voice-to-voice in 10 languages but excludes external guests and anonymous users and requires Microsoft 365 Copilot. For a client call — where the client is by definition external — this usually rules it out.
- Google Meet handles one English-anchored language pair per meeting with a 90-minute cap.
If your client speaks a language that pairs with English on Meet and the call is under 90 minutes, the native option may be enough. Check before buying anything.
The commercial point
Anything agreed on a translated call should exist in writing, in both languages, within the hour. Not because the translation was bad, but because that is good practice on any call and the language difference removes the excuse for skipping it.