# Multilingual AI assistant: answer in your customer's language

Source: https://busymate.ai/articles/multilingual-ai-assistant-customers-own-language
Last modified: 2026-09-07
Published: 2026-09-07 · Busymate AI team · 6 min read

> The reply is the easy half. What actually decides whether a multilingual assistant helps or misleads is what it knows — and three site habits that undo it.

Most owners think the multilingual question is "does it speak Spanish". It does. The interesting question is the one underneath: **what does it know, and in which language was that written?**

An assistant reads your pages, understands them, and replies in whatever language the visitor typed. That part is nearly free now. The part that decides whether it helps or quietly misleads is the source material — and a handful of habits on your own site that undo the whole thing.

## The easy half: the reply

A visitor writes in Portuguese, the answer comes back in Portuguese. Nobody picks a flag from a dropdown, and the customer never sees the machinery. On our own surfaces the site chrome and docs exist in 14 languages including right-to-left Arabic, and the chat follows the customer's language rather than the site's — the storefront setup is in the [Shopify guide](https://busymate.ai/docs/guides/shopify), and the same rule holds for the [embedded chat](https://busymate.ai/solutions/site-knowledge).

So the reply is solved. Hold on to the scepticism for what follows.

## The hard half: what it knows

Your knowledge is almost certainly written in one language. That is fine for explanation and dangerous for specifics.

| Answer type | Travels well? | Why |
|---|---|---|
| How something works | yes | it is explanation, and paraphrase is harmless |
| Tone, reassurance, next step | yes | nothing factual is at stake |
| Price, delivery window, stock | **no** | a paraphrase becomes a quote you did not give |
| Warranty, refund, legal wording | **no** | translated terms are not your terms |

The fix is not more translation. It is instructing the assistant to quote the specifics verbatim from your source, and to say plainly when it is unsure rather than produce a fluent guess — the pattern in the [knowledge guide](https://busymate.ai/docs/guides/knowledge), and the same honesty rule the [hand-off triggers](https://busymate.ai/articles/when-should-ai-hand-off-to-a-human) exist to enforce.

## Three site habits that undo it

**Do not auto-redirect by browser language.** Google's guidance is explicit: "Avoid automatically redirecting users from one language version of a site to a different language version" ([Google Search Central](https://developers.google.com/search/docs/specialty/international/managing-multi-regional-sites)) — it stops people and crawlers reaching your other versions. Offer the switch; never take the choice.

**One language per page.** The same guidance asks you to "use a single language for content and navigation on each page" and to avoid side-by-side translations. Half-translated pages confuse the crawler and the assistant equally.

**Put direction in the markup, not the stylesheet.** For Arabic, Hebrew or Persian, the base direction belongs on the element: "Do *not* use CSS to apply base direction in HTML pages", because "the directional information can affect the semantics of your content, and so should be part of the markup" ([W3C Internationalization](https://www.w3.org/International/questions/qa-html-dir)). `dir="auto"` is the honest choice for anything a customer types.

## Actions have to translate too

Answering is half a conversation; doing is the other half. When your site publishes its actions — check availability, start a return, book — as named tools an assistant can run, those tool labels, confirmations and error messages are customer-facing strings in exactly the way your page copy is. Chrome's [WebMCP](https://busymate.ai/webmcp) proposal is built around a human confirming each step, so the words on that confirmation are the words your customer decides on. The setup is in the [page tools guide](https://busymate.ai/docs/guides/page-tools); the same registration is what an assistant a visitor brings with them will read, alongside your [/llms.txt](https://busymate.ai/llms.txt).

## The language policy worth writing down

Add this to your assistant's instructions once:

```markdown
Reply in the language the customer wrote in. Match their formality.

Quote prices, delivery windows, warranty terms and refund policy VERBATIM
from [your source page], in the original language, with a short translation
after it — never a translated number on its own.

If a policy exists only in [English] and the customer writes in another
language, say which language the original is in and offer the exact wording.

If you are not certain of a translated specific, mark it [CHECK] and offer
a person instead of guessing.

Escalate to a human when: the customer asks in a language you answer with
low confidence, or the question is about [contracts / regulated advice].
```

Then ask your assistant to check its own coverage:

```text
Review my knowledge sources and list every page that states a price, a
delivery time or a refund term. For each one, tell me which language it is
written in and whether a customer writing in [Spanish] would get that answer
accurately. Show me the gaps before you change anything.
```

## What to measure

Two numbers, per language: how many conversations start, and how many reach an outcome instead of a dead end. A language with traffic and no outcomes is usually a knowledge gap, not a translation problem. You can watch the same split on [pricing](https://busymate.ai/pricing) tiers as volume grows, and you can see how any site reads to an assistant today — in any language — with the free preview at [/try](https://busymate.ai/try).

Being understood is not the same as being right. Get the reply in their language, then make very sure the specifics are yours.

## Questions

### Do I have to translate my whole website first?

No. The assistant answers in the visitor's language from whatever it has, so a German visitor gets a German reply from English source pages. Translating the site is an SEO decision about being found; it is not a precondition for being understood.

### What breaks first when an assistant works across languages?

Specifics. Tone and general explanation travel well, but prices, delivery windows, warranty terms and legal wording are exactly where a translated paraphrase becomes a promise you did not make. Pin those to your source wording.

### Is right-to-left Arabic just a font and a mirrored layout?

It is a markup decision. The base direction belongs in the HTML dir attribute, not in CSS, because the direction carries meaning and has to survive when your stylesheet does not load.

### Should I redirect visitors to a language version based on their browser?

Google advises against it. Automatic redirection stops both people and crawlers from reaching your other versions, and a visitor whose browser language is not their reading language ends up somewhere they did not choose.

### How do I check the quality of a language I do not read?

Test the three answers that cost money if they are wrong — price, delivery, refund — and have one customer or supplier who speaks it read those replies. Five minutes of a native reader beats any amount of guessing.