He never selected Italian. The website spoke Italian anyway.

A multilingual website assistant answers your visitors in their own language, so a visitor who doesn't read your site's language comfortably doesn't bounce before they understand what you offer. Maya does that by detecting the language each visitor arrives in and replying in it — by voice or text, from the first word — and, when your site already has that language version, switching the page to it. No language selector, no plugin translation layer, no friction.

Last updated 2026-07-16

Where a translate button stops

The usual answer is a flag dropdown or a machine-translate widget. Both put the work on the visitor: spot the selector, pick a language, wait for a clunky auto-translation, then still hit a form or chat that only speaks your language. Most foreign visitors don't bother — they land, feel the friction, and leave. The site never even learns it lost them at the language wall.

Maya removes the wall entirely. It notices the visitor arrived from Italy and greets them in Italian before they touch anything — the moment that tells them the site noticed who arrived. A translate button is a one-language phrasebook the visitor has to operate; Maya is a fluent local who greets them, understands them, and walks them through — even when they switch language mid-sentence.

What Maya does for a multilingual audience

It greets each visitor in their own language, from the first word — the visitor's device is set to French, your site is in English — Maya opens in French anyway, no selector clicked. That first attentive moment is the difference between a visitor who stays and one who bounces to a competitor who felt more welcoming.

It follows the visitor even when they switch language mid-conversation — a visitor can start in English, slip into German, then ask the next thing in French — Maya follows without missing a beat and without losing the thread of what they wanted. The understanding doesn't reset when the language changes. Almost nothing else does this.

It switches your site to the language version you already have — when your site already has, say, a French version, Maya switches the visitor to it live — no reload, no hunting for the flag. So the foreign visitor reads the real, human-written pages, not a machine translation. (Honest limit below: it switches among the languages your site already has; it doesn't translate your site into brand-new languages.)

It answers and guides in their language — by voice or text — the visitor can talk to Maya or type, and either way it answers from your real content and moves them to the right page in their own words. A visitor who couldn't have navigated an English-only site still finds what they came for.

It captures the foreign visitor who'd have bounced — as a real lead — instead of an anonymous non-English bounce, you get a named lead with what they wanted, in a language your team can follow up on. The traffic you were paying to attract but silently losing at the language wall starts converting.

What happens when Maya doesn't know the answer?

This matters as much across languages as within one. Maya checks its answers against your approved site content before it responds, in whatever language the visitor is using. When it can't verify something, it says so instead of guessing, offers the visitor the right next step, and flags the question for you — so a confident-sounding question in another language doesn't get a confidently-wrong answer.

What that means for you: Maya won't invent a price or a policy just because the question came in French — the abstention loop works in every language. Honest limit: Maya replies in the visitor's language and switches among the language versions your site already has; she speaks 70+ languages by voice — hearing and answering back out loud in whatever language the visitor uses, rather than a fixed set — and 70+ in text, and she does not machine-translate your whole site into languages you don't have.