Arabic-first, not Arabic-also: building AI for the Gulf

There's a quiet tell in most global software. Arabic is technically there — you can switch the interface, the layout flips right to left, a translation appears. And it's almost right, which is somehow worse than being plainly wrong. The phrasing is stiff. The tone sits at the wrong register. The dialect belongs to nobody in particular. It reads exactly like what it is: a product designed in English and translated afterwards.

Call that Arabic-also. It treats Arabic as an item near the bottom of a localisation checklist, ticked once and forgotten. Arabic-first is a different decision made at the very start, and it shapes everything downstream. In the Gulf, that distinction isn't academic. Customers feel it on the first call, and you can read it in the results.

Two products that look identical on a feature list

On paper, "supports Arabic" looks the same whether you did the real work or not. In a live conversation, the gap shows up inside a sentence.

Modern Standard Arabic is the written, formal register — correct for a newspaper, faintly strange coming from a voice assistant taking a call in Dubai or Jeddah. Nobody chats to their bank in MSA. They speak Khaleeji, and within it Emirati, Najdi, Hijazi and more, each with its own vocabulary, rhythm and warmth. A system that answers every caller in flat textbook Arabic announces itself as foreign in the first three seconds, and the caller quietly switches to English out of politeness. The connection is already lost.

Speaking Arabic and speaking to an Arab customer are not the same skill. One is translation. The other is belonging.

What building Arabic-first actually takes

Arabic-first isn't a bigger dictionary. It's a set of design choices a bolt-on can't reach:

• Dialect, not just language. Understanding and replying the way a caller actually speaks, not the way a textbook prescribes.
• Register and courtesy. Matching the formality the moment calls for, from a warm greeting to the respect a government or banking call expects.
• Code-switching. Following real Gulf speech as it slides between Arabic and English mid-sentence and back, without losing the thread.
• Tone as meaning. In Arabic especially, how something is said carries as much as the words. Flat delivery reads as cold even when every word is correct.
• Regional instinct. Grounding all of it in data, testing and judgement that come from being in the Gulf, not a translation memory in another timezone.

None of that survives being added at the end. It has to sit in the foundation, which is why global platforms struggle with it and teams building in the region treat it as the starting point.

The commercial case, not just the cultural one

It would be easy to file this under respect and courtesy — real reasons, but soft ones. The harder argument is that Arabic-first makes money and Arabic-also loses it.

A customer who reaches a system fluent in their dialect stays on the line. They don't switch to their weaker second language, they don't hang up frustrated, and they don't leave with the quiet sense that this company doesn't quite get them. In a market where a Gulf customer can pick a competitor who does sound local, that impression is worth real revenue. Higher completion rates, fewer abandoned calls, more resolved on first contact, better retention — none of that is sentimental. It's the direct payoff of sounding like you belong.

This is why xAIa builds Arabic-first rather than Arabic-also. The proof is in the volume: xAIa's Voice AI handles around 100,000 calls a month for Watt Utilities, answered in under a second and almost all picked up — at a scale where a stiff, translated accent would cost customers on every shift.

You can hear it in one sentence

The test is simple. Put a global platform's Arabic beside one built in the Gulf and give both the same call. One makes the customer work. The other makes them comfortable. That difference — the customer relaxing, staying in Arabic, forgetting for a moment they're talking to a machine — is the whole product.

For a Gulf enterprise, that's the reason to choose a partner who treats Arabic as the first language of the product, holds your data in the region, and builds for your customers rather than porting to them.

---

Hear the difference for yourself. Book a demo.