Multilingual AI Customer Service: 8 Languages, One Team
An e-bike brand selling through nine storefronts receives customer messages in German, Italian, French, Spanish, Dutch, Polish and English, and the support team writes Chinese and English. Hiring native speakers for every market was never realistic. This is how the AI system in our case study handles eight languages with one team: 15,445 chat conversations and 36,294 customer emails in the last 30 days.
Reply in the customer's language, think in one language
The model reads the email in whatever language it arrives in. The facts it works from are written in one working language: what the customer wants, the order and shipping status, what was promised before. The reply is then written in the customer's language. Keeping the facts in one language means the rules, the knowledge base and the reviewers all work from the same version of the truth, and only the final text changes language.
One knowledge base, searched across languages
Product facts, policies, troubleshooting steps and video guides live in one knowledge base maintained by the team. A German customer's question about a battery lock has to find an entry written in Chinese or English. Two things made this work:
- Search with short questions in the knowledge base's language. The system rewrites each question in the email as a short, single-topic query in the working language. In our tests the phrasing of the query decided the result far more than the search engine did: one short question put the right FAQ entry first.
- Search every time. The system retrieves before every draft, rather than letting the model decide whether it needs to. The model then decides how to use what it found.
Reviewers work in their own language
An agent who reads Chinese cannot check a Polish draft by reading it. So the review screen shows the agent the facts, the proposed solution and the draft, with a translation into the agent's language. The agent approves the substance, the solution and the facts, and the system keeps the customer-facing text in the customer's language. In the last 30 days agents sent 3,463 AI drafts without a single edit and edited 19,357 before sending; edits concentrate on substance such as promises and stock status, not on grammar.
Chat answers instantly, in every language
Chat cannot wait for a reviewer, so the chat AI answers facts and published policy directly in the customer's language: product questions, stock, shipping status, how to use and troubleshoot. Anything that needs a person to act becomes a ticket, and the customer receives the ticket number and the follow-up email address in their own language. Agents stepped into the chat window zero times in the last 30 days.
Language rules belong in one place
Language bugs hide in small rules. A customer typing in Chinese to a Philippine storefront still expects an English reply; a customer who explicitly asks for another language should get it. Rules like these live in one shared set of reply principles that every step reads, so the email drafter, the chat and the final check never disagree about which language to use.
Where multilingual systems break
- Punctuation in extractors. A full-width colon in Chinese text once made an extractor drop a whole email. Accept both full-width and half-width forms.
- Translated knowledge drifting apart. Keep one source per fact and translate at reply time instead of maintaining eight copies.
- Literal translation of internal wording. Internal labels and status names must be rewritten for the customer, not translated word for word.
Getting started
Start with the language that brings the most volume, connect the order and shipping lookups, put the knowledge base in one working language and turn on drafts for every email before any automatic sending. For the review loop itself see human-in-the-loop AI agents. The free plan maps this to your markets and languages in two working days.