Handoff & service · Explore this field ↗ · Practice · 2 min read
Multilingual service is not a translation switch
Language changes sources, policy interpretation, tone, evaluation, routing, and staffing.
Define equivalence
A multilingual service needs more than grammatical output. Determine whether policies are identical across regions, which language version is authoritative, and whether links, forms, attachments, and error messages are localized. Preserve product names and legal terms consistently. Let users choose language rather than relying only on detection.
Evaluate each language
Performance differs by language, dialect, code-switching, speech quality, and script. Build native test sets from real user goals. Review safety classifications and retrieval separately. Do not infer quality from the flagship language. Where the knowledge base lacks a matching language, decide whether translation is allowed and disclose it.
Handoff must remain real
A bot that speaks a language the human queue cannot support may deepen the failure. State availability and expected response language before transfer. Pass both original text and any machine translation, clearly labeled, so an operator can avoid treating the translation as ground truth.
Operator note
Maintain a language readiness matrix covering interface, source corpus, generation, speech, moderation, tools, legal text, human staffing, and evaluation. Launch only the combinations that work end to end.
Localize the service contract
For each supported language, name the authoritative policy source, translation owner, human queue, hours, and fallback language. Test mixed-language turns, regional date and number formats, names, product terms, and legal wording. Ask native reviewers to score meaning and service outcome, not just fluency. If a translated source lags the official version, the interface should disclose the date and route high-consequence questions. A smaller set of genuinely supported languages is more respectful than broad generation paired with an English-only operation.
Respect language choice
Do not keep switching back to a detected language after the user chooses one. Preserve that preference only with an appropriate scope and control. Names, addresses, and quoted material may legitimately use another script; code-switching is not evidence that the conversation should be rerouted.
Primary reading
Sources and limits
These links support the architecture, policy, or product behavior discussed above. Vendor documentation describes vendor features; it is not independent proof of performance. Current details should be rechecked before a production decision.