H Habla Agente docs
/

Your product

Languages

Habla has two different “language” ideas. Mixing them up is the most common source of confusion — keep them separate.

  1. Agent reply language — the language visitors receive in answers.
  2. Operator / marketing UI language — the language of the Habla dashboard and marketing chrome for you.

1. Agent reply language

Each agent has a default reply language set in agent Settings. That default is used for visitor answers unless a conversation picks up a supported language from the visitor’s Accept-Language header when the widget initializes.

Optionally, admins can enable Automatic visitor language detection per agent (default off). When on, HABLA detects each visitor message and answers in that language for the turn — without rewriting the conversation’s stored language. The first production-tuned automatic set is en and es. Admins may further restrict allowed reply languages; the default language is always the fallback when detection is uncertain or outside the allow-list. Explicit requests such as “Answer me in Spanish” are recognized when the requested language is allowed.

Changing the Habla admin or marketing UI locale does not automatically change the agent reply language. Website / page locale and widget chrome locale are separate from reply language.

Supported reply-language allow-list

Agent replies are limited to this supported allow-list (not an open-ended list):

  • en — English
  • nl — Dutch
  • es — Spanish
  • fr — French
  • de — German
  • pt — Portuguese
  • ja — Japanese
  • ar — Arabic
  • zh — Chinese

Choose the agent default from Settings using this allow-list.

Accept-Language behavior

  • On widget init, Habla may set this conversation’s reply language from the visitor’s Accept-Language header only when the requested language is in the allow-list above.
  • Otherwise Habla uses the agent’s configured default reply language.
  • That choice applies to the conversation. It does not rewrite the agent’s saved default language setting.

Agent settings and persona details: Agents.

2. Operator / marketing UI locales

The Habla dashboard and marketing chrome can be shown in many UI locales when multilingual mode is enabled for the deployment. That only changes buttons, navigation, and forms for you as an operator — it does not retrain the agent or change reply language by itself.

How UI locales, RTL, and translation management work: Languages & i18n (platform).

Knowledge in other languages

Index content in the languages your visitors ask about. How retrieval handles multilingual content is covered in RAG pipeline. You do not need a separate agent per language unless you want different personas or knowledge sets.

Related