Adoomi reads the language of each customer message and replies in that language, drawing on the same approved content you already publish. There is no language list to maintain and no translated copy of your site to keep in sync.
Each message is read in the language it arrives in and answered in that same language, in the same conversation. Detection is per message, so a visitor who switches language mid-chat is followed rather than corrected.
A question asked in French about an English-language site is answered in French, drawn from the English source. Your published pages are never rewritten or duplicated to make that work.
The buttons, labels and input hints around the conversation are localised separately from the answers and are localised separately from the answers themselves, so the interface matches the reply rather than sitting in English around it.
Handover to a named person, refusing to invent a price and regulated-sector limits behave the same way in Polish or Spanish as they do in English. The language changes; the boundaries do not.
Adoomi reads the pages, FAQs and approved content you already publish, in whatever language you publish them in. There is no separate translated import to prepare first.
There is no language list, no per-language content upload and no toggle to switch on. Because detection happens on each message, multilingual answering is live the moment the assistant is.
You approve what the assistant may say before it goes live. Ask it a real question in each language your customers actually use and read the reply — in regulated sectors, make that part of the standard review rather than a one-off.
Paste the single line Adoomi gives you into your site and the chat window goes live, localised interface included. Start to finish, setup runs to about 10 minutes.
Answers in the customer's language and shows its own buttons, labels and input hints localised to match. Limit: the page around the chat window stays in whatever language you published it in — Adoomi does not translate your site.
Carries the customer's original question plus the details captured in the chat across to your team, so the conversation continues without a retelling. Limit: the text arrives in the language the customer wrote it in, and Adoomi does not interpret your team's replies back.
Routes a structured enquiry — contact details, the customer need and the context — to the right teammate when a conversation needs a person. Limit: the customer's own words are passed through as written, so a non-English enquiry lands in your inbox in that language.
CustomerBonjour, je suis à Lille — est-ce que vous ouvrez le samedi ? [French: Hello, I'm in Lille — are you open on Saturday?]
AdoomiOui, nous sommes ouverts le samedi. Si vous souhaitez réserver un créneau, je peux transmettre votre demande à l'équipe. [The assistant replies in French, from the business's English opening-hours page: Yes, we're open on Saturday. If you'd like to book a slot, I can pass your request to the team.]
CustomerDzień dobry, ile kosztuje pierwsza wizyta? [Polish: Hello, how much does a first appointment cost?]
AdoomiNie mam potwierdzonej ceny w zatwierdzonych materiałach, więc jej nie podam. Mogę przekazać pytanie zespołowi — proszę zostawić imię i adres e-mail. [In Polish: I don't have a confirmed price in the approved content, so I won't quote one. I can pass the question to the team — please leave your name and email.]
Your teamWhatsApp handoff: the customer's original Polish message arrives with the name and email captured in the chat. The text reaches the team as the customer wrote it — replying in Polish is the team's job, not the assistant's.
Both replies work off the same English-language pages the business already publishes: Adoomi answered in French from the English page. The price question was refused in Polish exactly as it would have been in English, because no approved price existed to quote.
Adoomi replies in the customer's language, but your published pages, menus and copy stay exactly as they are. If you want a translated site for navigation or search, that is still a separate piece of work.
Machine translation of clinical, legal and other regulated terminology is not always exact. Businesses in regulated sectors should read multilingual answers as part of the normal review step rather than assume the English review covers them.
When a conversation moves to WhatsApp or email, your team receives the customer's original words in the customer's language. Adoomi does not translate the replies your team writes back.
We publish no fixed language list or count — the range follows the model behind the assistant, but we do not publish a fixed language list or a language count, because the range depends on the model behind the assistant rather than something you configure.
The assistant will not produce a regional price, promotion or policy that is not in the content you approved. If a country-specific answer matters, it has to exist in your approved content first.
Whatever language customers write in, hosting stays in the EU, GDPR export and deletion are built in, and the chat window sets no tracking cookies.
Adoomi detects the language of each message and replies in it, covering major European and world languages. We deliberately publish no fixed list, because the range follows the model behind the assistant. The honest test is to ask a question in the languages your customers use before you go live.
No per-language setup exists. There is no language list to maintain, no separate content import and no toggle to switch on — you connect your website once, review the answers, and every reply follows whatever language the customer wrote in.
One credit is one AI answer, whatever language it is written in. Free gives you 50 credits a month at £0, Local is £8 for 200 and Growth £20 for 500, and a French or Polish reply draws on the same allowance as an English one.
Adoomi does not translate your website. Your pages, menus and published copy stay exactly as you wrote them; only the answers inside the chat window change language, along with the chat window's own buttons and labels.
Machine translation of clinical, legal and other specialised wording can be imperfect, so multilingual answers deserve the same scrutiny as English ones. Regulated businesses should read a sample in each customer language before going live and keep it in the normal review cycle.
Your team receives the customer's original words. A WhatsApp handoff carries the message as the customer wrote it, plus the contact details and context captured in the chat, and email alerts do the same. Adoomi does not interpret your team's replies back.
Language detection is automatic and happens per message — there is no manual language switch. A customer who writes in another language mid-conversation gets replies in that language, and the review step is where you check the behaviour suits your audience.
Adoomi starts with your public business knowledge and routes the moments that need a person to your team.