Building Arabic-first customer support AI
Arabic is the fifth most spoken language in the world, yet most AI support tools treat it as an afterthought. Here is how we are approaching it differently.
The gap in the market
When we started building Orqelo, we looked at what the dominant customer support AI tools were doing with Arabic. The answer was: RTL text rendering that breaks in ticket threads, transliterated responses that feel machine-generated, and zero understanding of Gulf, Levantine, or Egyptian dialect differences.
For the MENA market — a region with over 400 million Arabic speakers and fast-growing e-commerce adoption — this is not a niche problem. It is the core product problem.
What "Arabic-first" actually means
It does not mean translating an English-first product. It means:
RTL everywhere. The chat widget, the inbox, the analytics dashboard — all flip correctly when the tenant's locale is Arabic. This sounds obvious. Getting it right in a Vue/Tailwind app with mixed LTR/RTL content (Arabic messages next to English timestamps, for example) requires deliberate design, not an afterthought.
Dialect awareness. A customer typing in Egyptian Arabic uses different words and contractions than a customer in Lebanon or Saudi Arabia. Our AI routing layer uses dialect signals — alongside intent signals — to choose the right response style. We do not conflate Modern Standard Arabic with spoken dialects.
Transliteration handling. A large share of MENA users type Arabic words using Latin characters ("Arabizi"). The AI pipeline normalises Arabizi inputs before routing so the response is never confused by the script.
Right defaults. New tenants based in MENA markets get Arabic as the primary language by default, with English as a secondary. Not the other way around.
Where we are today
The core message routing handles Arabic correctly. The widget renders RTL. Sentiment analysis works on Arabic input. The biggest remaining gap is dialect-specific tone calibration — making the AI sound Levantine when talking to Lebanese users, not formally MSA. That is next.
Why this matters for the product
Orqelo's initial ICP is bootstrapped and early-stage SaaS teams in MENA and Europe who need to talk to customers across WhatsApp, website chat, and Instagram DMs from a single inbox. The Arabic-first orientation is not just a localisation feature — it is the core reason a MENA-based team would choose Orqelo over Intercom or Zendesk.
If you are building something that serves Arabic-speaking customers and want to talk about what we are doing, reach out.