> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vorel.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Languages

> Arabic and English in the same conversation, dialect handling, and how language is chosen per turn.

Vorel is bilingual by default. The agent answers in the language the customer used, including when
they switch part way through.

## What is supported

* **English**
* **Arabic**, including Gulf and Levantine dialect input

Your workspace has a default language, which decides the opening greeting and anything the platform
sends proactively. Everything after the first turn follows the customer.

## Switching mid-conversation

A customer who opens in English and switches to Arabic gets Arabic from that turn on. A single
message mixing both is answered in whichever language dominates.

The switch is resolved per turn rather than pinned once at the start, because pinning it means one
Arabic sentence in an English conversation drags the rest of the call into Arabic.

## Dialect

Arabic input is handled across dialects rather than only Modern Standard Arabic, which matters for
voice: callers do not speak MSA. Replies are in a register appropriate to your persona and vertical,
which for most businesses means clear, neutral Arabic rather than heavy dialect.

## Writing for voice

Arabic and English replies on the voice channel are written to be spoken. Numbers, dates, prices and
addresses are phrased the way a person says them rather than the way they are written. Latin strings
inside Arabic sentences (an email address, a brand name) are handled so they are not read out
character by character.

## Configuring language behaviour

<CardGroup cols={2}>
  <Card title="Default language" icon="flag">
    Which language the agent opens in and uses for proactive messages.
  </Card>

  <Card title="Persona per language" icon="user-pen">
    Agent name, tone and signature phrases are set separately for English and Arabic.
  </Card>

  <Card title="Knowledge in both" icon="book">
    Knowledge entries can be written in either language. Retrieval works across both, so an Arabic
    question can find an English answer, which the agent then answers in Arabic.
  </Card>

  <Card title="Templates and canned copy" icon="message">
    Confirmations, CSAT questions and canned fallbacks are configured in both languages.
  </Card>
</CardGroup>

## Where the default language matters most

Anything the platform sends first, rather than in reply, uses your default language:

* WhatsApp templates, which are approved per language, so the right approved template is picked
* Appointment reminders and re-engagement messages
* CSAT survey questions
* Escalation alerts to your team

## Adding a language

Support beyond Arabic and English is a configuration and content exercise rather than a code change,
covering persona, canned copy, templates and voice formatting. Talk to your operator if you need
one.
