What is supported
- English
- Arabic, including Gulf and Levantine dialect input
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
Default language
Which language the agent opens in and uses for proactive messages.
Persona per language
Agent name, tone and signature phrases are set separately for English and Arabic.
Knowledge in both
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.
Templates and canned copy
Confirmations, CSAT questions and canned fallbacks are configured in both languages.
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
