Multilingual Knowledge Base: Write Once, Answer in Many Languages

A multilingual knowledge base does not have to mean writing every page in every language. The Talkmio documentation says that Mio answers in the visitor’s language, only from your content, and that questions in one language find answers written in another, for example a Lithuanian question answered from an English FAQ. That changes how you plan content: you can write once, in the language you know best, and still serve visitors who write in German, Polish, Spanish or Lithuanian. This guide explains what that means in practice, when one source is enough, when to add market-specific pages, how to word content so that it travels well and how to test each language before visitors do.

The facts come from the live documentation and pricing page. Language examples and business advice that go beyond them are general guidance, marked as such, and should be checked against your own market.

What the Documentation Says About Languages

Three statements define the behaviour. First, Mio replies in the language the visitor writes in, and the pricing page lists Lithuanian, English, German, Polish, Russian, Spanish and French, and 30+ others. Second, the chat window itself is translated, so the buttons and labels match the visitor’s language. Third, questions in one language find answers written in another. Together they mean that your multilingual knowledge base can be a single set of sources, and the visitor’s language decides the language of the reply, not the language of the page.

There are two related settings to know. In the widget settings, language can be set to auto-detect or fixed, and in the Inbox, your own tools translate between you and the visitor. The next sections cover both. First, decide how much content you need to write in more than one language, since that is where most of the work lies.

Multilingual Knowledge Base Models: One Source or Many?

There is no single right answer. The table shows three common models with their costs and risks.

Model	How it works	Best for	Main risk
One language	All content in one language; Mio answers visitors in theirs	Businesses with the same offer in every market	Local facts missing; wording that does not travel
One language plus market pages	Main content in one language; extra pages for markets where facts differ	Shops and services with local prices, shipping or rules	Forgetting to update the market pages
Full translations	Parallel content in each language	Businesses with a full website in several languages	Contradictions between versions; double maintenance

Most small businesses do best with the middle model. Write your main content once, and add short pages for the facts that really differ. Full translations are right when you already maintain a translated website, because Mio reads it anyway, but they raise the chance of two versions that disagree. Our guide to how AI chatbots handle multiple languages explains the general options.

Find the Facts That Differ by Market

A multilingual knowledge base is only as correct as its local facts. Before you add anything, list the things that change from one country to another.

• Prices and currency: a price in euros is not a price in zloty, and taxes may differ.
• Delivery: carriers, times, costs and countries served.
• Payment methods: the options that are common in one market may not exist in another.
• Legal and consumer rules: return rights, warranty periods and cancellation rules.
• Support hours and languages: when a person answers, and in which languages.
• Product availability: items sold in one country only.

For each fact that differs, write a short page or a question and answer pair that names the country in its title, such as “Delivery to Germany” or “Returns for customers in Poland”. A visitor’s question usually names the country, and the title helps Mio pick the right source. Keep the country-neutral facts on the main pages, so that you do not repeat them.

Example: A Shop Selling in Three Markets

Imagine a small online shop based in Lithuania that sells in Lithuania, Poland and Germany, and writes its website in English and Lithuanian. The shop keeps its product pages, care instructions and general policies in English as the master. It adds three short market pages: “Delivery and returns in Lithuania”, “Delivery and returns in Poland” and “Delivery and returns in Germany”, each with local carriers, delivery times and return details, and a short note at the top that names the country. It adds a handful of question and answer pairs for the questions that customers in each country ask in their own words. A Polish visitor who writes in Polish about returns is answered in Polish, from the Poland page; a German visitor asking about the warranty finds the master policy and the Germany page. The shop maintains one set of master pages and three small local ones, instead of twelve translated pages. A multilingual audience is served without a multilingual workload.

Write Source Content That Travels Well

Because the visitor’s language and the page’s language can differ, the way you write matters. Plain, concrete sentences are easier to match across languages than clever ones. A few habits help.

• Use full sentences with the subject named. “The standard delivery takes three to five working days” is better than “Usually 3 to 5”.
• Write numbers, units and dates clearly. State the currency, say “working days” and write dates in an unambiguous form such as 5 March 2027.
• Avoid idioms and jokes. They rarely survive a change of language, and they are not what a visitor wants from a support answer.
• Put one fact in one place. If the return period appears on three pages with three wordings, Mio may choose any of them.
• Name things the same way. If a product is called a “bundle” in one place and a “pack” in another, add a short note that they are the same.

These habits help human readers too, and they reduce the number of corrections after you test.

Brand Names, Terms and a Small Glossary

Product names, plan names and technical terms need special care. Do not translate a brand name. If customers in another market use a different word for the same thing, add a question and answer pair that connects them: “What is a flat rate? A flat rate is our fixed-price delivery option.” Keep a small glossary in your own notes, with the term, the meaning and the way you want it to appear in answers. Our guide to an AI chatbot glossary for brand terms shows how to teach Mio your names and jargon.

Test Every Language With Try Mio

Try Mio shows the answer, which knowledge pieces were used and how long it took. Use it to test your multilingual knowledge base as a visitor would. Build a small matrix: choose ten key questions, and ask each in each language that matters to you. Compare three things: whether the facts are the same in every language, whether the source pieces are the ones you expect and whether the tone is right.

Question	English	German	Polish	Verdict
Delivery time	Check answer and source	Check answer and source	Check answer and source	Same fact in all three?
Return period	Check answer and source	Check answer and source	Check answer and source	Same fact in all three?
Price of the main product	Check answer and source	Check answer and source	Check answer and source	Currency correct?

If a fact changes with the language, look at the knowledge pieces. Usually one language has a more complete source than another. Fix the source and ask again. Then test in a private window with the real chat, because the widget and the hand-off behave in the visitor’s language too. Our guide to multilingual live chat covers the experience from the visitor’s side.

Widget Language: Auto-Detect or Fixed

Under Websites, the widget’s language can be auto-detect or fixed. Auto-detect suits sites with visitors from many countries, since the chat window adapts to the visitor. A fixed language suits a site that serves one market and wants a consistent look. The welcome and offline texts are yours to write, so check them in each language that you support, and keep them short. Changes apply within five minutes. Our guide to chat widget language settings explains how to choose.

Replying in the Inbox in Many Languages

Mio is not the only one who needs to cope with languages. When a conversation is handed to your team, a person writes the reply. The Inbox helps: Translate turns your draft into the visitor’s language, Polish fixes grammar and tone, and a “translate” link under a visitor message shows it in your language. Use them as aids, not as replacements for judgment. For an important message, such as a complaint or a legal question, have a colleague who speaks the language read the reply. Our guide to live chat translation in the Talkmio Inbox shows the workflow.

Which Languages Do Your Visitors Actually Use?

Do not guess which languages matter. The Visitors page shows country, city, page, device, browser and source for people on your site right now, and Reports show countries over time. Look at the countries, and think about the languages that go with them. Start your tests with the three or four languages that bring most visitors. Add others when the numbers justify it. A language that brings two visits a month does not need a dedicated market page, though Mio will still answer in it from your main content.

Keep One Place to Update

The great advantage of a multilingual knowledge base built on one source is maintenance. When a price changes, you change it once, use Re-read so that Mio reads the new version and run one or two test questions in other languages. With full translations, every change has to be made several times, and a missed one produces contradictions. Whatever model you choose, make one person responsible for updates, and write the rule down: the main language is the master, and other versions follow. Review the market pages every quarter and before each season, and add the date of the last review to your own notes. When you launch in a new country, start with the delivery, returns and payment pages for that country, test ten questions in the local language and only then announce the chat to local customers. The study of language localisation teaches the same lesson: separate content that is the same everywhere from content that is local, and manage each on its own terms.

Frequently Asked Questions

Do I need to write my knowledge base in every language?

No. The documentation says that Mio replies in the visitor’s language and that questions in one language find answers written in another, for example a Lithuanian question and an English FAQ. Write your main content once, and add market-specific pages only where facts differ.

Which languages can Mio answer in?

The pricing page lists Lithuanian, English, German, Polish, Russian, Spanish and French, and 30+ others, and says that Mio replies in the language the visitor writes in. The chat window itself is translated too. Test the languages that matter to you in Try Mio, with real questions, before you rely on them.

How do I handle prices in different currencies?

Write a short page or a question and answer pair for each market that names the country and the currency, such as delivery or prices for Poland. Keep country-neutral facts on the main pages, and test the answers in the matching language.

What should I translate and what should I not?

Do not translate brand and plan names. Translate or add local versions of facts that differ by market, such as prices, delivery and legal rules. If customers use another word for a product, add a pair that connects the two terms.

How do I test a multilingual knowledge base?

Choose ten key questions and ask each in each language in Try Mio, which shows the answer, the knowledge pieces used and the time taken. Compare facts, sources and tone. Then test the real chat in a private browser window.

What language does the widget use?

Under Websites, the widget language can be set to auto-detect or to a fixed language. Auto-detect adapts to each visitor, and a fixed language keeps one consistent look. Welcome and offline texts are written by you, so check them in each language.

The Bottom Line

A multilingual knowledge base for Mio can be small: one well-written main source, a few market pages for the facts that differ and a short test routine in each language. Write plainly, keep one fact in one place and let the visitor’s language decide the language of the answer. Start free with Talkmio, add your website and ask your ten key questions in a second language today.