Kann ich meine Bestellung noch ändern?
Bestellungen können bis zum Versand geändert werden — in der Regel innerhalb von zwei Stunden nach der Bestellung.
retrieved from: shipping-policy (English)
The assistant detects the language of every message and replies in it, reading from content you only maintain in one language. No translated help centre, no second bot, no language selector for the visitor to find.
Kann ich meine Bestellung noch ändern?
Bestellungen können bis zum Versand geändert werden — in der Regel innerhalb von zwei Stunden nach der Bestellung.
retrieved from: shipping-policy (English)
返品にはどれくらい時間がかかりますか?
返品が届いてから5営業日以内に返金処理を行います。
retrieved from: returns-page (English)
Vocês entregam no Brasil?
Sim, enviamos para o Brasil. O prazo estimado é de 7 a 12 dias úteis.
retrieved from: delivery-zones (English)
هل يمكنني الدفع عند الاستلام؟
الدفع عند الاستلام متاح في مناطق محددة فقط، ويظهر الخيار عند إتمام الطلب.
retrieved from: payment-methods (English)
Every answer above came from the same English source pages.
Every multilingual chatbot is one of these three shapes underneath. The choice is not about answer quality on day one — it is about what you are maintaining in a year.
Build the flows, then rebuild them in French, German and Spanish.
Your maintenance multiplies by the number of markets, and the fifth language never happens.
Machine-translate every page into every language and index all the copies.
You now have four sources of truth. One of them will drift, and you will find out from a customer.
Keep your content in one language. Detect the visitor’s language per message, retrieve from your originals, answer in theirs.
One thing to maintain, and languages you never planned for are covered anyway.
Maintaining parallel help centres is how policies quietly go out of sync. One source of truth is not just cheaper — it is more accurate.
Not per session and not per visitor. Someone who opens in English and switches to French mid-conversation gets French from that point, which is exactly what happens when a person is more comfortable in their own language once the conversation gets technical.
The passages retrieved are your own English ones. The model reads them and composes the answer in the visitor’s language — so the fact being conveyed is always the fact you wrote, not a fact from a translated copy that drifted.
Modern models carry register across languages reasonably well. A support voice that is warm and direct in English does not come out stiff in German. It is worth testing with a native speaker before launch, in the two or three languages that matter most to you.
Four steps, and the first one is mostly about what not to do.
Do not translate anything first. Train the assistant on your existing pages in whatever language you wrote them — this is the step people over-prepare for and do not need to.
Ask a question in a language your content is not written in, and confirm the answer contains the right fact. This is the part that actually has to work; the translation is the easy half.
The first message and the handover text are yours, so decide whether they sit in your main language or read naturally to an international visitor.
Twenty minutes with a native speaker, before launch, on the markets you actually sell to. Pin the assistant to one language in the system prompt if a market is too sensitive to risk.
Answers in widely spoken languages are consistently strong. Further down the list, phrasing gets more literal and idiom is less reliable. If a language is commercially important to you, spend twenty minutes testing it with a native speaker before you launch — and remember you can always pin the assistant to a single language in the system prompt if that is the safer choice.
A multilingual chatbot is an assistant that understands and replies in more than one language. The better ones detect the language of each incoming message and respond in it automatically, rather than making the visitor pick from a menu. The distinction that matters is architectural: some are several bots in a trench coat, one per language, each needing its own content and upkeep; others keep a single knowledge base and handle the language at the moment of answering. Only the second stays maintainable past two or three markets.
Train an assistant on your existing content in whatever language you already have it, then check that a question asked in another language still retrieves the right passage and comes back correctly. Set your welcome and handover copy, and test the two or three languages that matter commercially with a native speaker before launch. What you should not do is translate your whole site first — that is the expensive step, and with this approach it is unnecessary.
Not on its own. That instruction handles composing the reply, but the harder half happens earlier: the assistant still has to find the right passage in your content, and the question arrives in a different language from the pages it is searching. If the retrieval step cannot bridge that gap it will fetch the wrong passage and then translate it beautifully, which is worse than saying nothing. Test by asking in another language and checking the fact, not the fluency.
Ours works across all supported languages on the free plan — there is no language tier and no per-language charge. One assistant and 50 conversations a month is enough to test how it handles the markets you care about before spending anything.
No. That is the point. The assistant reads your existing content in whatever language it is written and produces the answer in the visitor’s language. Translating your site is still worth doing for SEO and for the reading experience, but it is not a prerequisite for multilingual support.
From the message itself. Each message is assessed independently, so a mid-conversation switch is handled naturally and no visitor has to find a language selector.
More than 95, covering every widely spoken language and a long tail of smaller ones. The practical limit is the underlying model, and the models available in CustomerBot span the major frontier and open families — several of which are notably strong on non-European languages.
Honestly, no. Quality is best in high-resource languages — English, Spanish, French, German, Portuguese, Japanese, Chinese — and gets more variable further down the list. If a specific language is commercially important to you, test it properly with a speaker rather than assuming parity.
Yes. The system prompt is yours to write, so an instruction to always reply in a particular language regardless of input is respected. Some regulated businesses need exactly that.
No. Pricing is per conversation and per model tier, not per language. A conversation in Korean costs what the same conversation would cost in English.
Train it on your English pages, then test it the way your customers will. It is the fastest way to judge this properly.
Start free