Handling a customer support call in another language
Route to a native speaker when one is available and the issue is complex. When one is not, live translation beats forcing the customer into a second language while they are already frustrated — and always send the resolution in writing, in their language.
Support has a constraint other call types do not: the customer is already unhappy, and asking them to also operate in a second language compounds it.
Route first, translate second
If you have a native speaker available and the issue is non-trivial, route to them. Live translation is the answer when routing is not possible — not a replacement for a support team that covers your customers’ languages.
Where routing usually beats translation:
- Emotionally charged calls. Complaints, escalations, cancellations. Tone carries most of the resolution and it is the first thing lost in translation.
- Long diagnostic conversations, where accumulated small ambiguities compound.
- Anything with a commercial outcome — refunds, credits, contract changes.
Where translation is fine or better:
- Short, factual issues — status, how-to, configuration
- Out-of-hours coverage, where the alternative is nobody
- Long-tail languages you will never staff
Set it up properly
Load a glossary of product names, feature names, error codes and plan names. Support vocabulary is proper nouns and jargon, which is exactly where general translation fails and where a wrong rendering sends the customer to the wrong place.
Tell the customer translation is running, briefly and without ceremony. It sets expectations for the pause and lets them slow down.
Never translate error codes or identifiers. Put them in the chat, in the original.
During the call
- Confirm the problem by restatement before proposing a fix. Half of support failures across a language barrier are solving the wrong problem confidently.
- One step at a time. Multi-step instructions given in a burst do not survive translation or stress.
- Use the chat for anything to be typed or clicked. Menu paths, URLs, settings names.
- Check after each step, not at the end.
Always follow up in writing
The single highest-return practice in multilingual support: send the resolution in writing, in the customer’s language, before you close.
It gives them something to re-read and act on later, it reduces repeat contacts, and it protects both sides if the verbal exchange was ambiguous. It also means a customer who did not fully follow the call is not left guessing — they will not say so on the phone.
Platform note
Support calls are external and often ad hoc, which is the hardest case for native tooling.
Teams Interpreter excludes external guests and anonymous users, requires Microsoft 365 Copilot, and is unavailable in ad hoc meetings — three separate disqualifications for inbound support. Google Meet does one English-anchored language pair per meeting. Zoom offers translated captions only, which is awkward when the customer is following instructions on the same screen.
A note on measurement
If you introduce translation in support, watch repeat contact rate rather than handle time. Translation lengthens calls, and that is not a failure — a longer call that resolves the issue is cheaper than a short one that does not.