Try Omnifox free 7 days free. No credit card required.
Guides

Website Chat in the Visitor's Language: Auto-Detection and Live Translation for Agents

Sell abroad from your website: the chat detects the browser language, the visitor writes in theirs and your agent reads and replies translated.

September 07, 2026
Website Chat in the Visitor's Language: Auto-Detection and Live Translation for Agents
In this article

    A Texas outdoor-gear brand starts getting orders from Monterrey and Guadalajara. A Leeds software company signs its first three customers in São Paulo. In both cases the website is in English, the support team speaks English, and the new customers open the chat and write in Spanish or Portuguese. What happens next decides whether those markets grow or stall.

    The usual answer, "hire a bilingual agent", is slow and does not scale past two languages. The practical answer is website chat in the visitor's language: the widget detects the browser language and shows its interface accordingly, the visitor writes in their own language, and your agent reads and replies in theirs, with the translation happening in the shared inbox. This post explains that mechanism layer by layer, what to switch on, what never to translate, and where the AI agent fits. The strategy side is in multilingual live chat; here we cover the plumbing.

    Layer 1: the widget interface follows the browser

    Before anyone types a word, the widget itself has text: the "Send" button, the pre-chat form labels, the offline notice. In Omnifox that interface is shown in Spanish, English or Portuguese according to the visitor's browser language. A shopper in Guadalajara with Chrome in Spanish sees "Enviar", not "Send", without you doing anything. A visitor who sees an English-only form assumes the support behind it is English-only and often does not start; the interface language is the first signal that they are welcome to write in their own.

    Your custom texts (welcome message, offline message, proactive bubbles) are not auto-translated, because they are yours. Write them for the market the page serves, or keep them short and neutral on pages with mixed traffic.

    Layer 2: conversation translation for the agent

    This is the layer that changes the economics. With conversation translation turned on for the channel:

    • The visitor writes in their language. The language is detected automatically from the message; there is also an optional language selector if you would rather let the visitor choose.
    • The agent sees the message translated into their own language in the shared inbox, next to the original.
    • The agent replies in their language. The visitor receives it translated into theirs.
    • An optional disclaimer tells the visitor that messages are machine-translated.

    Translation consumes AI credits from the plan; each plan includes a monthly allowance you can extend (see the pricing page). Here is what the Texas brand's agent actually sees and sends. The visitor wrote in Spanish; the agent works entirely in English:

    Visitor (original): Hola, quiero saber si envían a Monterrey y cuánto tarda.

    Agent sees: Hi, I want to know if you ship to Monterrey and how long it takes.

    Agent types: Yes, we ship to Monterrey. Delivery is usually 6-9 business days with the international carrier, and duties are calculated at checkout so there are no surprises on arrival.

    Visitor receives: Sí, enviamos a Monterrey. La entrega suele tardar de 6 a 9 días hábiles con el transportista internacional y los impuestos se calculan al pagar, así que no hay sorpresas al recibirlo.

    The agent never switched languages. The customer never noticed a barrier.

    Layer 3: the AI agent answers in whatever language arrives

    If an AI agent is assigned to the chat channel, it responds in the customer's language on its own, drawing on the knowledge base (documents, FAQ, catalog) you built in English. For the Leeds software firm, a Brazilian customer asking "como faço para exportar o relatório?" at 11 pm UK time gets a Portuguese answer from the English help docs, and the human team sees the exchange in English the next morning if it was handed off.

    Two settings decide how much the AI does: the response strategy (never / always / only the first message) and the handoff conditions.

    What not to translate

    Machine translation is good at sentences and bad at proper nouns. Agree on a short "do not translate" list and write it into the knowledge base and the agent guidelines:

    1. Product and plan names. "Impulsa" is a plan name, not the Spanish verb. Keep names as they appear in the catalog.
    2. Amounts and currencies. Write "USD 59/month" or "£45", not "59 dollars", so the number survives translation intact. Say explicitly which currency you bill in.
    3. Order numbers, SKUs, tracking codes, promo codes. Put them on their own line or in code formatting so they are not touched.
    4. Legal wording. Refund terms, warranty conditions and anything your counsel wrote should be linked, not paraphrased across languages. Confirm with your own counsel what needs a formal translation.
    5. Addresses. Street names and postcodes are copied, not translated; "Calle 5 de Mayo" stays as is.

    Agents can help by keeping replies plain: short sentences, no idioms ("we'll sort you out") and no sarcasm. Translation quality drops fastest on the phrases that feel friendliest in English.

    Setup checklist in the shared inbox

    Step Where Setting Why
    1 Channels → your web chat Confirm interface language is automatic Widget shows es/en/pt by browser
    2 Same channel → Translation Turn on conversation translation Agent reads and writes in their language
    3 Same screen Enable the language selector (optional) Useful when detection is ambiguous, e.g. short "ok" messages
    4 Same screen Enable the machine-translation notice Sets expectations; visitors forgive small errors
    5 AI agent → knowledge base Add the "do not translate" list Names, prices, codes stay intact
    6 AI agent → response strategy Choose always / first message only Decide how much the AI handles per market
    7 Business hours Set the time zone per team Mexico and Brazil are not on London time
    8 Reports Watch credit usage weekly Translation spends AI credits

    Step 3 matters because detection works on the content of the message, so a first message like "Hi" gives it nothing to go on; the selector lets the visitor state their language up front.

    Two markets, two different configurations

    US ecommerce brand selling into Mexico. Mobile traffic, questions about shipping, duties and returns, volume peaking in the evening US Central time. Setup: translation on, AI agent "always" with a shipping-and-returns knowledge base, human handoff for damaged items. When the shopper leaves a phone number, the conversation continues by WhatsApp from the same contact record, the channel people in Mexico expect; inside 24 hours the agent replies freely, after that an approved template reopens the thread.

    UK software company with Brazilian customers. Desktop traffic, technical questions, logged-in customers. Setup: translation on, AI agent "only the first message" so it collects the account and the error, then handoff to a support engineer who reads Portuguese as English. Because users are identified through the widget's identify call, the engineer sees the account and history without asking.

    Both pay for the chat channel the same way: it is included in every plan, and only translation and AI replies consume credits.

    Frequently asked questions

    Does the visitor know the replies are machine-translated?

    Only if you turn on the disclaimer, which we recommend. A one-line notice ("Messages are translated automatically") lowers frustration when a phrase comes out slightly off.

    Which languages are supported for the conversation itself?

    The widget interface comes in Spanish, English and Portuguese. Conversation translation and the AI agent work with the language detected in the visitor's message; test your target languages in the AI simulator before launch rather than assuming.

    Can one agent handle chats in several languages at once?

    Yes. Each conversation is translated independently into the agent's language, so an agent in Denver can have a Spanish, a Portuguese and a French chat open in the same shared inbox and reply to all three in English.

    Does translation apply to WhatsApp and email too, or only the website chat?

    The mechanism described here is for the web chat conversation. When the conversation moves to WhatsApp or SMS from the same contact record, check the channel's own translation setting rather than assuming it carries over.

    Start with one market and one week

    Pick the market that already writes to you in another language, turn on translation and the disclaimer for the website chat channel, load the "do not translate" list and run it for a week with the credit report open. Every plan includes the chat channel and a credit allowance, so the 7-day free trial is enough to run that first week on your real site.

    Ready to try it in your business?

    Bring WhatsApp, Instagram, Messenger, email and calls into one inbox, and let AI handle the first reply. Set it up today.

    7 days free. No credit card required.

    Comments (0)

    No comments yet. Be the first to share your thoughts.

    Leave a comment

    Your email is never published. Comments are moderated before appearing.

    Markdown supported. HTML is stripped.

    Read more

    Message us on WhatsApp