Live chat with real-time translation: how it works, and where it fails

Real-time translation lets a support agent who speaks only English help a customer writing in Arabic, Thai or Portuguese, inside an ordinary chat window. It sounds like magic, and for routine questions it mostly works. This guide explains what happens under the hood, the specific situations where it goes wrong, and a simple playbook that makes translated chat reliable.

How translated chat works

1. Language detection. When the visitor sends a message, the system identifies its language. Detection is reliable for full sentences and less reliable for one-word messages like "hi" or "ok", so good tools also use the browser or page language as a hint.
2. Inbound translation. The message is sent to a machine-translation engine and translated into the agent's working language. The agent sees the translation, ideally with the original text alongside it.
3. Outbound translation. The agent replies in their own language. Before it reaches the visitor, the reply is translated into the visitor's language.
4. Display. The visitor sees only their language. The agent sees both, so the conversation history stays auditable.

The round trip normally adds well under a second or two, so the conversation still feels live.

Where machine translation is reliable

Customer-service chat is close to the ideal case for machine translation: short sentences, common vocabulary and a narrow domain. In practice these message types translate well:

• Order status and tracking ("Where is my order 10482?")
• Shipping options, costs and delivery times
• Sizes, colours, stock availability
• Prices, discounts and payment methods
• Returns and refund steps
• Simple how-to questions about a product or account

Where it fails, and how to handle it

A playbook for agents

1. One idea per sentence. Short sentences survive translation; long ones with several clauses get scrambled.
2. Avoid pronouns that point far back. Repeat the noun: "The blue jacket is in stock," not "It is."
3. Check the original when something looks odd. If a translated message seems rude or strange, read the original and use context before reacting.
4. Confirm key facts. End complex answers with a summary: "To confirm: order 10482, delivery to Madrid, 5–7 days."
5. Build canned replies. Common answers written in clear, simple English translate consistently every time.
6. Know when to escalate. Chargebacks, legal complaints and large B2B contracts deserve a native speaker or written follow-up.

Does translated chat hurt trust?

Customers generally prefer a fast, clear answer in their own language to a perfect answer in a language they struggle with. What damages trust is inconsistency: a widget that greets them in Spanish and then an agent who replies in English. Make sure the widget interface, the greeting and the replies are all in the visitor's language.

Setting it up in ZhiDesk

In ZhiDesk, translation is part of every conversation rather than a separate tool. The widget detects the visitor's language and shows its interface in one of 18 languages. In the agent workspace you choose your working language; messages are translated both ways across 38 languages, and the original text is kept next to the translation. There is no per-message translation fee. You can test it during the 7-day free trial by opening your own site on your phone and writing in another language.

FAQ