Conversation language | Stand Feature Reference

Before you begin

Plan availability: All plans.

Prerequisite: An active conversation; changing the fallback language requires organization-owner access to the Site.

Key boundary: The conversation language guides new AI output and Stand interface copy. It does not translate previously written messages, customer-authored page content, or source documents.

01

Supported languages

Stand-ins support text conversations in the 109 languages listed below. This is the language coverage behind “100+ languages”: it describes AI conversation support, not the number of translated buttons.

The table separates three capabilities: detecting the language from a visitor’s message, answering in that language, and showing translated widget controls and Stand-generated system copy. Yes for detection means the language is covered, but a message must still be clear enough to identify confidently.

Yes for conversation means model-supported text input and replies, not a guarantee of fluency or accuracy in every dialect or subject. Test important conversations with a speaker of the language. UI translation applies to the standard visitor widget, not the rep dashboard or a custom chat UI. On smaller screens, scroll the table sideways to see all columns.

Language	Detect from visitor text	AI conversation	Translated widget UI
Afrikaans	Yes	Yes	No — English fallback
Albanian	Yes	Yes	No — English fallback
Amharic	Yes	Yes	No — English fallback
Arabic	Yes	Yes	No — English fallback
Armenian	Yes	Yes	No — English fallback
Assamese	Yes	Yes	No — English fallback
Azerbaijani	Yes	Yes	No — English fallback
Basque	Yes	Yes	No — English fallback
Belarusian	Yes	Yes	No — English fallback
Bengali	Yes	Yes	No — English fallback
Bosnian	Yes	Yes	No — English fallback
Bulgarian	Yes	Yes	No — English fallback
Catalan	Yes	Yes	No — English fallback
Cebuano	Yes	Yes	No — English fallback
Chinese, Simplified and Traditional	Yes	Yes	No — English fallback
Corsican	Yes	Yes	No — English fallback
Croatian	Yes	Yes	No — English fallback
Czech	Yes	Yes	No — English fallback
Danish	Yes	Yes	No — English fallback
Dhivehi	Yes	Yes	No — English fallback
Dutch	Yes	Yes	Yes
English	Yes	Yes	Yes
Esperanto	Yes	Yes	No — English fallback
Estonian	Yes	Yes	Yes
Filipino, Tagalog	Yes	Yes	No — English fallback
Finnish	Yes	Yes	Yes
French	Yes	Yes	Yes
Frisian	Yes	Yes	No — English fallback
Galician	Yes	Yes	No — English fallback
Georgian	Yes	Yes	No — English fallback
German	Yes	Yes	Yes
Greek	Yes	Yes	No — English fallback
Gujarati	Yes	Yes	No — English fallback
Haitian Creole	Yes	Yes	No — English fallback
Hausa	No	Yes — with a language hint	No — English fallback
Hawaiian	No	Yes — with a language hint	No — English fallback
Hebrew	Yes	Yes	No — English fallback
Hindi	Yes	Yes	No — English fallback
Hmong	No	Yes — with a language hint	No — English fallback
Hungarian	Yes	Yes	No — English fallback
Icelandic	Yes	Yes	No — English fallback
Igbo	No	Yes — with a language hint	No — English fallback
Indonesian	Yes	Yes	No — English fallback
Irish	Yes	Yes	No — English fallback
Italian	Yes	Yes	Yes
Japanese	Yes	Yes	No — English fallback
Javanese	Yes	Yes	No — English fallback
Kannada	Yes	Yes	No — English fallback
Kazakh	Yes	Yes	No — English fallback
Khmer	Yes	Yes	No — English fallback
Korean	Yes	Yes	No — English fallback
Krio	No	Yes — with a language hint	No — English fallback
Kurdish	Yes	Yes	No — English fallback
Kyrgyz	Yes	Yes	No — English fallback
Lao	Yes	Yes	No — English fallback
Latin	Yes	Yes	No — English fallback
Latvian	Yes	Yes	No — English fallback
Lithuanian	Yes	Yes	No — English fallback
Luxembourgish	Yes	Yes	No — English fallback
Macedonian	Yes	Yes	No — English fallback
Malagasy	Yes	Yes	No — English fallback
Malay	Yes	Yes	No — English fallback
Malayalam	Yes	Yes	No — English fallback
Maltese	Yes	Yes	No — English fallback
Maori	No	Yes — with a language hint	No — English fallback
Marathi	Yes	Yes	No — English fallback
Meiteilon, Manipuri	No	Yes — with a language hint	No — English fallback
Mongolian	Yes	Yes	No — English fallback
Myanmar, Burmese	Yes	Yes	No — English fallback
Nepali	Yes	Yes	No — English fallback
Norwegian	Yes	Yes	No — English fallback
Nyanja, Chichewa	No	Yes — with a language hint	No — English fallback
Odia, Oriya	Yes	Yes	No — English fallback
Pashto	Yes	Yes	No — English fallback
Persian	Yes	Yes	No — English fallback
Polish	Yes	Yes	No — English fallback
Portuguese	Yes	Yes	Yes
Punjabi	Yes	Yes	No — English fallback
Romanian	Yes	Yes	No — English fallback
Russian	Yes	Yes	No — English fallback
Samoan	No	Yes — with a language hint	No — English fallback
Scots Gaelic	Yes	Yes	No — English fallback
Serbian	Yes	Yes	No — English fallback
Sesotho	No	Yes — with a language hint	No — English fallback
Shona	No	Yes — with a language hint	No — English fallback
Sindhi	Yes	Yes	No — English fallback
Sinhala, Sinhalese	Yes	Yes	No — English fallback
Slovak	Yes	Yes	No — English fallback
Slovenian	Yes	Yes	No — English fallback
Somali	Yes	Yes	No — English fallback
Spanish	Yes	Yes	Yes
Sundanese	Yes	Yes	No — English fallback
Swahili	Yes	Yes	No — English fallback
Swedish	Yes	Yes	Yes
Tajik	Yes	Yes	No — English fallback
Tamil	Yes	Yes	No — English fallback
Telugu	Yes	Yes	No — English fallback
Thai	Yes	Yes	No — English fallback
Turkish	Yes	Yes	No — English fallback
Ukrainian	Yes	Yes	No — English fallback
Urdu	Yes	Yes	No — English fallback
Uyghur	Yes	Yes	No — English fallback
Uzbek	Yes	Yes	No — English fallback
Vietnamese	Yes	Yes	No — English fallback
Welsh	Yes	Yes	No — English fallback
Xhosa	No	Yes — with a language hint	No — English fallback
Yiddish	Yes	Yes	No — English fallback
Yoruba	Yes	Yes	No — English fallback
Zulu	No	Yes — with a language hint	No — English fallback

02

Languages supported by the widget interface

Stand has complete built-in widget copy in ten languages: English, Finnish, Swedish, German, French, Spanish, Portuguese, Italian, Dutch, and Estonian. Regional tags use the corresponding base-language interface—for example, Brazilian Portuguese uses Portuguese copy.

The translated surface includes composer labels; send, minimize, retry, new-message, end-conversation, and start-new-chat controls; connection and typing states; quota and unavailable messages; handoff and follow-up cards; and conversation-ended actions.

Visitor’s language	Stand-in reply	Widget controls and Stand-generated system copy
Spanish	Spanish	Spanish
Polish	Polish	English fallback, because Polish UI copy is not yet built in
Japanese	Japanese	English fallback, because Japanese UI copy is not yet built in

03

How Stand chooses the active language

Before the visitor writes, Stand uses browser, page, and Site hints to choose a sensible starting language. After visitor-authored text establishes a language, the visitor’s own messages become authoritative.

Priority	Signal
1	The latest visitor message whose language can be identified confidently. A later clear switch replaces the earlier active language.
2	The visitor’s ordered browser language preferences, then the browser’s primary language.
3	The current page’s `lang` value.
4	The Site’s owner-configured fallback language.
Final fallback	English when none of the preceding signals provides a usable language tag.
Context only	Greeting, private page context, Stand-in instructions, and knowledge-source language can inform the answer but do not override clear visitor-authored language.

04

Switching languages during a conversation

Stand checks visitor messages before preparing an AI reply. When it detects a different language confidently, it saves the new language, instructs the Stand-in to use it, and updates supported widget copy. No language menu or separate request to switch is needed.

Stand changes language conservatively. A single word—such as a greeting, a name, or a keyboard mash—never changes the language, and a two-word message changes it only when the language is unmistakable. Other short or ambiguous text may also leave the current language unchanged. If several messages arrive together, the last confidently identified language guides the response. The following example uses invented delivery policies to show the language change, not product facts.

Speaker	Message	What Stand does
Visitor	“Toimitatteko tilauksia Ruotsiin?”	Establishes Finnish. The Stand-in answers in Finnish and the widget uses Finnish controls.
Stand-in	“Kyllä. Toimitamme tilauksia myös Ruotsiin.”	The reply follows the visitor’s Finnish without translating the earlier transcript.
Visitor	“How long does delivery usually take?”	The visitor switches naturally to English. Stand records English before generating the next reply.
Stand-in	“Delivery usually takes three to five business days.”	The Stand-in mirrors English and the widget changes its built-in controls to English.
Visitor	“¿Y puedo cambiar la dirección después de pagar?”	The visitor switches again, this time to Spanish.
Stand-in	“Sí, si el pedido todavía no se ha enviado.”	The Stand-in and the supported widget interface both switch to Spanish.

05

Set the Site fallback language

Owners configure the fallback from Dashboard → Sites, expand the relevant Site, then open Chat language and choose Fallback language. Saving changes the starting fallback for future conversations on that Site; it does not force every visitor to remain in that language.

The setting is useful for a site whose intended audience is known but whose pages or browsers do not provide a reliable language hint. Leaving it unset allows the normal browser and page signals to lead.

06

When a visitor prefers another language

When the conversation language has no widget translation, only the fixed interface and system copy fall back to English. The AI is still instructed to use the established conversation language.

If Stand cannot confidently identify a message’s language, it keeps the previous language or the starting fallback. A fuller sentence can give the detector more evidence. Human reps write in the languages they support; Stand does not translate their messages.

07

Persistence and restoration

A confident visitor-language switch updates durable session state rather than changing only one reply.
The current language is saved with the local session pointer and also restored from the server when a conversation is reopened.
A restored conversation uses its established language instead of reverting to the browser’s current default.
A new conversation starts a new language decision and can use different visitor, page, or Site fallback signals.

08

Availability and permissions

Automatic conversation-language handling and localized widget controls are available on every plan.
Visitors do not choose a language from a Stand settings menu; their writing and browser or page signals drive the conversation.
Only an organization owner can change the Site fallback language.
AI replies require an eligible AI Stand-in; a human rep remains responsible for the language of messages they write.

09

Translation boundaries

Stand does not rewrite or translate earlier visitor or rep messages when the language changes.
Customer-authored stand-card content, page text, product names, and linked destination pages are not automatically translated by this setting.
Knowledge-source documents remain stored in their source language; the conversation language guides the AI response rather than creating translated source copies.
Human rep messages are not machine-translated before delivery.
AI language quality varies by language, dialect, subject, and message clarity. Check important wording with someone who knows the language.

10

Related features

Visitor messaging and chat controls — The Stand widget gives website visitors a real-time text conversation with a matched rep or AI Stand-in. Visitors can send formatted messages, minimize or resize the window, end a conversation, and start another without leaving the website.
Site management — A Site is Stand’s installation and routing boundary for one named website context. It owns the stable embed snippet, normalized domain, enablement, Site instructions, fallback language, behavior rules, coverage diagnostics, and usage scope.
Stand-in instructions and prompt builders — Stand-in instructions define the individual Stand-in’s role, facts, tone, boundaries, and conversation behavior. They are applied after shared Team and Site instructions, while guided builders can draft instruction text from structured answers.