Answer
Yes. Ordr treats Arabic and English as equal conversation languages rather than translating an English bot. The language is set by the customer's first message, and it stays consistent across every channel a business sells on.
A customer who writes in Arabic is answered in Arabic. No menu, no setting, no per-customer configuration. Teams that sell in Egypt and the wider MENA region should not need a separate “Arabic bot” product—language is part of the same agent that already knows the catalogue.
WhatsApp, Instagram, Messenger, Telegram, and web chat share one conversation contract, so Arabic behaves identically wherever the customer starts. Switching channels does not invent a second language policy or a second catalogue translation layer.
Catalogue items and menu dishes carry an Arabic name beside the English one, so an Arabic conversation stays in Arabic when quoting what is for sale. Prices still follow the tenant’s currency settings rather than forcing a foreign storefront format mid-chat.
Language choice does not weaken commerce steps. Confirming an item, collecting delivery details, or capturing a clinic booking still uses the same structured flow—only the wording the customer sees follows Arabic or English. Operators reviewing the inbox see the thread in the language it actually happened in.
Ordr does not publish dialect quality scores, human-parity translation benchmarks, or guarantees that every colloquial phrase will be perfect. The product claim is operational: Arabic is a first-class conversation language across channels, with optional Arabic catalogue names and human takeover when needed.
Many “global” chatbots ship English-first and bolt Arabic on as a translation toggle. That produces mid-sentence language flips, English product names inside Arabic replies, and support scripts that feel imported. Ordr’s answer pages and operator UI exist because the buying question in this market is usually “will it actually run the conversation in Arabic on WhatsApp?”—not “does it have an Arabic marketing site.”
Yes. Ordr handles Arabic and English as first-class conversation languages. A customer can choose Arabic from a language prompt, and a customer who simply writes in Arabic is answered in Arabic without choosing anything.
No. A first message written in Arabic sets the conversation to Arabic on its own. The language prompt exists for customers whose first message does not make the language clear.
Products and menu items carry an optional Arabic name alongside the English one, so an Arabic conversation can quote Arabic product names rather than switching language mid-sentence.
All of them. WhatsApp, Instagram, Facebook Messenger, Telegram, and the web chat widget share one conversation contract, so language handling does not change per channel.
Yes. Any conversation can be handed to a human operator, who sees the full history in the language it happened in.
No. The same Arabic/English behaviour applies on Instagram DMs, Facebook Messenger, Telegram, and the embeddable web chat—because those channels share one conversation contract.
No. Ordr answers in Arabic when the customer writes in Arabic. It does not publish dialect benchmarks or promise a specific regional register beyond what the live model produces for that tenant.