Languages
Orchestrate works for people who don't work in English, at every layer: the console, voice calls, knowledge bases and the PII guardrails.
The console
The console is available in English, Arabic and French. Arabic is laid out right to left from the first frame, with Gulf conventions and Latin digits.
Which language a browser shows, in order:
- the person's own choice, from the menu in the top bar or Settings > Language and region
- the install default a platform admin sets under Settings, which the sign-in page follows too
- the browser's languages
- English
The time zone is set per browser under Settings > Language and region, and is the device's own until you set it. Dates, times and numbers on every page follow the language and time zone.
The workflow graph canvas stays left to right in every language, on purpose.
The console's frame (sidebar, top bar and breadcrumbs), sign-in, Overview, Settings and the language and PII controls are translated. Other pages still show English text until they are translated. A missing translation always falls back to English, never to a blank.
Agents
An agent answers in the language its model can. Pick a multilingual chat model for agents that serve people in other languages. For example, Granite 3.3 2B covers 12 languages, Arabic and French among them. See Models and serving.
Voice and phone calls
- Caller's language in an agent's voice settings tells the speech-to-text model which language to expect, or Detect automatically lets it detect the language of each utterance.
- Voice per language gives the agent a voice for each language, so its reply switches voice when the caller switches language. A Piper voice speaks the language its name starts with, for example
ar_JO-kareem-mediumfor Arabic orfr_FR-siwis-mediumfor French. - The model is told to reply in the caller's language.
- A call can override the language: the Playground's Language picker, a phone number's language, or
languagewhen you start a session through the API. - A Whisper model whose name ends in
.entranscribes English only. Use a multilingual one, such as Whispersmall, for other languages and for detection. - Kokoro's built-in voices cover several languages, and a cloned voice records its language. See Voices and speech models.
- Auto-translate lets an agent built in one language serve callers in another: a translation model translates each turn in and the answer back out. See Auto-translate.
See Voice agents.
Knowledge bases
- The model library marks every embedding model as English or multilingual. For documents in other languages, pick a multilingual one, such as
bge-m3,paraphrase-multilingualorgranite-embedding:278m. - Documents are split at the script's own sentence marks, such as
؟and।, and never between a letter and its diacritics. - A document that isn't in Latin script gets a note that recommends a multilingual embedding model.
You can change a knowledge base's embedding model later, and Orchestrate re-indexes it in the background. See Knowledge bases.
PII guardrails
The PII rules include regional packs for the Gulf, India, the UK, the EU and the US. Digits in Arabic-Indic, Persian and Indic scripts are read as ordinary digits, so a number in an Arabic or Hindi transcript is still seen. The context words that mark a business reference, such as "order" and "invoice", have French and Arabic equivalents. See PII guardrails.
Models on a new install
Your operator can have the install add and deploy models at start-up with modelCatalog.seed and modelCatalog.deploy, for example a multilingual chat model, a multilingual embedding model, Whisper small and Arabic and French voices. See Configuration.