Milly Software
Insights›Knowledge base›Your Knowledge Base, for Shoppers Who Don't Write in English
Knowledge base··5 min read

Your Knowledge Base, for Shoppers Who Don't Write in English

A shopper asks in Spanish and your shipping policy is written in English. How Milly Chat searches your knowledge base in the language it is written in and answers in the shopper's own, with nothing to set up, and why it translates instead of adding keywords.

V
Viet Le
co-founder · Milly Software

A shopper on your store types "¿Cuánto tarda el envío a Canadá?" Your shipping page answers that question, in English, and it's in your knowledge base. Whether the shopper gets the answer comes down to one step most people don't see: what the assistant types into the search.

This post covers how Milly Chat handles a shopper who writes in a different language from your documentation. Short version: you don't translate anything, and there's no setting for it. Cross-language knowledge base search shipped on September 10, 2026.

Replies in the shopper's language

The assistant is instructed to reply in the language of the shopper's most recent message, and to switch with them if they change languages halfway through. Your product data and knowledge base arrive in your store's own language, and the assistant is told not to treat that as a reason to answer in it.

Names are the exception. Product, collection and brand names are kept as they appear in your catalogue, because a title is how your store's own pages are found. Translate it and the shopper is looking for a product that doesn't exist under that name. The text around the names (features, availability, policy details) is in the shopper's language.

Some messages have no language of their own: a greeting, an email address, a bare SKU or model number. For those the assistant is instructed to carry on in the language the conversation has been using. If it's the first message, it uses the language your storefront appears to be in, worked out from the page address (a localized domain or a language path).

Searching in the language you wrote it in

Replying in Spanish is the easy half. The harder half is finding the answer. A knowledge base search compares the question with your entries. A question asked in Spanish, searched against entries written in English, can come back with nothing close enough, and then the assistant tells the shopper it doesn't know something you documented months ago.

So when a shopper writes in a different language from your knowledge base, the assistant is instructed to translate their question into your knowledge base's language first, search with that translation, then answer the shopper in their own language. The translation is only for the search, and it isn't part of the reply.

You don't declare a language anywhere. The assistant reads it off your own documentation and product descriptions, so an English knowledge base is searched in English and a Spanish one in Spanish. It doesn't assume English.

Why it translates instead of adding keywords

There's a shortcut that looks like it does the same job: keep the shopper's wording and staple a few English keywords onto it. We tested that approach, and it finds documented answers well. It also finds something for almost any question, including topics your store hasn't documented. A padded query scrapes up a loosely related entry, and a loosely related entry is how an undocumented topic comes back looking answered.

A faithful translation doesn't have that problem. It asks your knowledge base the question the shopper asked, in the words your documentation uses. That's why the assistant is told to translate the whole question, and not to mix languages or pad it.

The honest tradeoff

Translating isn't free. A question in your documentation's language matches generic policy text more easily than the same question in another language. For a topic you haven't written about, that means the search is more likely to return something weakly related instead of nothing.

That's acceptable because of a rule in the assistant's instructions: a result that doesn't address what the shopper asked is still a miss, and it shouldn't answer from whatever the search happened to surface. A translated result is held to the same rule as any other.

Two limits worth knowing. This is about the knowledge base: product search isn't part of it, and product names are kept as written anyway. And it's built for a knowledge base written in one language, which is the usual setup. If you keep parallel entries in several languages, that isn't the case it was designed for, and I'd check a few conversations in Replay before relying on it.

Checking it on your own store

Open a conversation in another language in Conversation Replay. The knowledge sources panel at the top lists each search the assistant ran, with the exact query it searched with. For a shopper writing in German against an English knowledge base, you'll see an English query there and a German reply below it. If the entries that came back look wrong, the fix is in your knowledge base, the same as it would be for an English question.

This shipped in v2.10.4 and needs no setup. If most of your traffic is in one language and your documentation is in another, I'd spend ten minutes in Replay reading a few of those conversations. It's the quickest way to see what your international shoppers are asking.

Frequently Asked Questions

Do I need to translate my knowledge base for Milly Chat?

No. Keep your knowledge base in the language you write it in. When a shopper asks in another language, the assistant is instructed to translate their question into your knowledge base's language before it searches, and to answer the shopper in their own language.

Is there a setting to turn on for multilingual shoppers?

No. There's no setting for it. The assistant works out which language to search in from your own documentation, so an English knowledge base is searched in English and a Spanish one in Spanish.

Will the assistant translate my product names?

It's instructed not to. Product, collection and brand names are kept as they appear in your catalogue, because a title is how a shopper finds that product on your store. The text around the names (features, availability, policy details) is written in the shopper's language.

Try Milly Chat

Want to see how this fits your store?
We'll set up a working session.

Get it on Shopify →Talk to sales →