Most businesses in Dubai should not build an Arabic WhatsApp bot, and the ones that should already know why. The deciding number sits in your own inbox: open the last 200 inbound WhatsApp threads and count how many opened in Arabic script. Under 5% and a second language is maintenance work you pay for every month with no return attached. Above 15%, or if you deal with government entities, patients, or an Emirati household clientele, it stops being optional. Everything between those two lines is a judgement call, and this piece gives you the questions that settle it.
The cost is not the translation. Translating a set of chat flows into Arabic is a weekend of work for a competent bilingual writer. The cost is that every message template now exists twice, gets reviewed twice by Meta, breaks twice, and needs a human who can read Arabic to sign off before every change. Budget somewhere in the region of AED 2,500 to 6,000 on top of a build to add a second language properly, plus a permanent uplift on the monthly support line.
An Arabic WhatsApp bot in Dubai is an automated agent on a WhatsApp Business API number that detects the customer's language, replies in Arabic, and holds the same booking, qualification and payment flow it runs in English. It is worth building when a meaningful share of inbound arrives in Arabic script, or when the business is government-facing, healthcare, or sells to a local and GCC-resident clientele. It is rarely worth building for B2B software, tech services, or businesses whose customers are overwhelmingly expatriate professionals.
What language your customers in the UAE actually write in
The UAE population sits at roughly 11.5 million in 2026, and Emirati citizens number around 1.3 million of that, roughly one resident in nine. The Indian community alone is close to 4 million. Dubai itself has passed 4 million residents. Arabic is the official language of the country, and English is the working language of almost every commercial transaction inside it.
That gap is the whole subject. Arabic carries the state, the courts, official correspondence and a large part of family and social life. English carries the invoices. A Lebanese founder, a Syrian contractor and an Egyptian marketing manager will all read Arabic comfortably and will still write to a supplier in English, because that is the register business happens in here and because their phone keyboard is already in English.
So the question is not whether your customers speak Arabic. Many of them do. The question is whether they will choose to write to you in it, and whether the ones who do represent enough revenue to justify a permanent second surface on your automation.
Read your own data before you read anyone's opinion, including this one. Language distribution in a Dubai inbox varies wildly by industry, by emirate, by price point and by which ad creative brought the lead in. A luxury clinic in Jumeirah and a B2B logistics firm in JAFZA operate in the same city and get almost no overlap in inbound language.
Where Arabic is not optional
Some categories fail without it, and no amount of automation quality compensates.
Government-facing work. If your process touches official submissions, correspondence with a ministry, or documents that must exist in Arabic to be valid, then the conversation around those documents runs in Arabic. Companies doing PRO services, corporate documentation and licensing work are not adding Arabic as a nicety.
Healthcare, especially with older patients. A patient describing a symptom will do it in the language they think in. Insisting on English at that moment is a clinical problem before it is a service problem. Clinics with a strong Emirati or Levantine patient base need Arabic on the front door, and the older the patient skew, the harder that is.
Emirati household clientele. Home services, private tutoring, event work, majlis catering, luxury retail with a local client list. This segment runs on referral inside families, and the first impression is a WhatsApp message. Replying in English to a message written in Arabic is a small, legible signal about who you are set up to serve.
GCC visitors and buyers. Saudi nationals are one of the largest visitor groups into Dubai and a serious share of the premium property and retail market. Someone messaging from Riyadh about a Palm apartment is far more likely to write in Arabic than a resident of Dubai Marina is.
Anything sold outside Dubai and Abu Dhabi. Language distribution shifts noticeably in Sharjah, Ajman and Al Ain. A business whose customer base sits in the northern emirates should count its own threads before assuming the Dubai pattern applies.
Where Arabic is money you will not get back
The honest list, which is the part the other articles on this topic leave out.
B2B software and technology services. Your buyer is a founder, a CTO or an operations manager, and the entire vocabulary of their job exists in English. An Arabic version of your sales flow will be used by almost nobody and will still need maintaining.
Agencies and professional services selling to expatriate founders. Same reasoning. The people signing your contracts negotiate in English.
Creative production, studio rental, photography. We run this category ourselves and the inbox is overwhelmingly English, with the occasional Arabic message that almost always contains English words inside it.
E-commerce aimed at expatriate consumers. Fitness, beauty subscriptions, pet supplies, imported goods. The customer found you on Instagram in English and will keep going in English.
Trade, logistics and field services. The uncomfortable version of the question lives in this category. If you are going to fund a second language, Arabic may not be the one that serves the most customers. For a cleaning company, a delivery operation or a maintenance firm, Hindi, Urdu or Russian can reach more of the people who actually message you. The decision is which second language, not whether Arabic specifically.
If your business is on this list, the money is better spent on speed. An agent that replies in under a minute in English will beat a bilingual competitor replying in forty minutes in either language. That is the trade we make on our own inbox and we have not regretted it.
Which Arabic, exactly
This is where most vendor pitches go quiet, because the honest answer complicates the sale.
Modern Standard Arabic (الفصحى, al-fusha) is the written, formal register: news broadcasts, government documents, contracts. Gulf Arabic (الخليجي, al-khaleeji) is what people actually speak and text in around here, and Emirati Arabic has its own vocabulary inside that. A customer types شحالك (shhalak, how are you) where MSA would use كيف حالك. They write الحين (al-heen) for now, وايد (wayed) for a lot, and شو for what.
Large language models handle MSA confidently. That makes sense, because MSA is what the internet has the most of. Performance on dialect is thinner and gets thinner the further you move from Egyptian, which is the best-represented dialect online. In practical terms your bot will understand a Gulf-dialect message most of the time and will answer in something that reads like a newsreader replying to a text message. Not wrong, and not close either.
The workable setting is to comprehend dialect and reply in a light, plain register: simple MSA with the formality dialled down, short sentences, no classical flourishes. Trying to make the bot speak convincing Emirati dialect is a project with a bad return, and a bot that speaks dialect badly is worse than one that speaks plain Arabic well.
Then there is Arabizi, Arabic written in Latin script with numerals standing in for sounds that English lacks. The 3 is ع, the 7 is ح, the 2 is a hamza, the 5 is خ. So "shu el se3r" and "3ayez a7jez" arrive in your inbox in Latin characters. Every naive language detector reads that as English, or as noise, and routes it to the wrong flow. Handling it needs an explicit rule, because the detection library will not save you.
Code-switching finishes the picture. Real messages look like "السلام عليكم do you have availability Saturday الساعة ٤؟" inside a single line. Half Arabic, half English, one Arabic-Indic numeral. A router built on "which language is this message" has no correct answer here. The one that works reads the whole thread rather than the last message and stores a language preference on the contact.
The small technical things that break first
Right-to-left rendering. Arabic text runs right to left, and the bidirectional algorithm decides how to place anything inside it that is not Arabic. Time ranges, phone numbers, prices and URLs get reordered visually in ways that look fine in your editor and wrong on the customer's screen. A booking window written as 09:00-11:00 inside an Arabic sentence is a classic offender. Keep numbers and links on their own lines, or push them into buttons, and check every template on a real handset rather than in a web console.
Numerals. Eastern Arabic-Indic digits (٠١٢٣٤٥٦٧٨٩) and Western digits both appear in UAE messages, often in the same thread. If your automation parses a time, a quantity or a phone number, it has to normalise digits before parsing or it will silently fail. This is the single most common bug we see in Arabic-capable flows, and it fails quietly, which is worse.
Dates and the calendar. Hijri dates appear in official contexts and in conversation around religious dates. Relative expressions carry a lot of the traffic: بكرة (bukra, tomorrow), بعد بكرة (day after tomorrow), بعد العيد (after Eid). A date parser tuned on English relative expressions will not catch these, and "after Eid" is not a date at all until you resolve it against a lunar calendar that itself moves.
Line length and layout. Arabic and English versions of the same message do not occupy the same number of lines. A template that fits neatly inside the preview in English can wrap badly in Arabic and push your call to action below the fold.
None of these are hard problems. All of them are invisible until a customer hits one, and the customer does not report it. They just stop replying.
One bilingual agent or two separate ones
One number handling both languages is right for almost everyone. Two numbers means two WhatsApp Business accounts, two template libraries, two verification processes, two sets of ad destinations and two things to monitor, and it only earns its keep when you genuinely run separate Arabic-language advertising into a separate Arabic-speaking team.
For the single bilingual setup, three rules hold it together.
Detect once, on the first substantive message, not on every message. A bot that flips language mid-conversation because someone typed "ok" is a worse experience than a bot that picked wrong and stayed consistent.
Store the language on the contact record, not on the conversation. A returning customer should not be re-detected six weeks later.
Give the customer an explicit switch. One line at the start offering the other language, and an instant, permanent honouring of a request to change. This single feature removes most detection failures, because the customer corrects you for free.
Detection reliably struggles on short replies, emoji-only messages, voice notes, and the Arabizi case above. Design for a wrong guess rather than pretending you will not make one.
The template bill nobody budgets for
Anything your automation sends outside an active 24-hour conversation window has to be a message template pre-approved by Meta. A template is identified by its name plus its language, and each language version carries its own review status. Your Arabic version can sit rejected while the English one is live.
Work out what that means operationally. Twelve templates in English becomes twenty-four objects to manage. Every price change, every new service, every wording correction is now two submissions and two review waits. Editing an approved template sends it back into review, and Meta limits how often you can edit, so a bad Arabic string is not something you quietly fix on a Tuesday afternoon.
The real bottleneck is review before submission. Somebody who reads Arabic has to check the copy, because you cannot proofread what you cannot read. If that person is a freelancer, every template change is now blocked on their availability. If nobody in your business reads Arabic, you are shipping customer-facing copy you have never verified.
Messaging rates themselves do not change with language. In the UAE, utility category messages run at roughly AED 0.03 to 0.06 each and marketing category messages sit several times higher, in the region of AED 0.15 to 0.20. Meta revises its rate card, so confirm the current published UAE rates before budgeting. The second language costs you in maintenance hours, not in per-message charges.
Escalation, and the trap of a bot that outclasses your team
One failure mode turns an Arabic bot into a liability. The agent opens in fluent Arabic, qualifies the customer in Arabic, then hands the thread to a human who cannot read a word of it.
The customer has already been told, by the language of the reply, that this business handles Arabic. Switching them to English at the moment they need a person is the exact point where they were most invested. That handover does more damage than never offering Arabic at all.
Three workable positions:
If you have Arabic-speaking staff, tag the thread by language and route only to them. Never let the round robin hand an Arabic conversation to an operator who cannot read it.
If you have partial coverage, have the agent be honest about it. A message saying a colleague will follow up in Arabic within a stated window, with a scheduled callback attached, holds the customer. A silent switch to English does not. An Arabic-capable voice line covering the same hours can carry the gap when the callback lands outside office hours.
If you have no Arabic coverage at all, do not build the Arabic bot. Automate the English path to the point where nothing takes longer than a minute, and revisit Arabic when you hire someone who can back it up.
The seven questions that settle it
Answer these in order. The first one carries most of the weight.
- In your last 200 inbound WhatsApp threads, how many opened in Arabic script? Under 5%, stop here. Over 15%, keep reading and expect to build it.
- Is there at least one person in your business who reads Arabic and is reachable on the days you trade?
- Does your work involve government entities, official documents, or regulated patient communication?
- Is a meaningful part of your revenue from Emirati households or GCC-resident buyers rather than expatriate residents?
- Do you run any advertising in Arabic? If your creatives, landing pages and forms are English, your inbound will stay English no matter what the bot speaks.
- Would Hindi, Urdu or Russian serve more of your actual customers than Arabic would?
- Can you commit to maintaining two template sets and two escalation paths for at least a year?
Two or more clear yes answers across questions 2, 3 and 4, combined with an Arabic share above the threshold in question 1, means build it. A yes on question 6 means you are asking about the wrong language. Anything else means the budget belongs in response time, follow-up discipline and payment links, which move revenue in every language.
What we actually run, and what it costs
We run this class of automation on our own business. SkyLight's studio in Dubai takes its enquiries on WhatsApp, and the agent answers a 02:40 message on a Saturday the same way it answers 10:00 on a Monday, qualifies the enquiry, writes the booking into the calendar and issues the payment link without a person in the loop. The same contour supports a business doing around AED 67,600 net a month at roughly 5x ROAS.
Our inbox is English-dominant. Arabic messages arrive, and when they do they usually carry English words inside them. We built the fast English path first and treat language as a decision to revisit against our own thread counts, not as a feature to install because it sounds thorough. That is the same advice we give clients, including when it costs us the extra line on the quote.
Open numbers, as always. One automated process built and handed over starts at AED 6,000 with support from AED 1,200 a month. Adding a second language to that flow typically lands in the AED 2,500 to 6,000 band on top, depending on how many templates and branches exist, plus an uplift on monthly support to cover the extra review cycle. Full detail sits on our pricing page, and the agent itself is described on the WhatsApp AI sales agent page.
If you are not sure which side of the line you are on, the cheapest next step is counting your own threads. If they say Arabic matters, the build is a single-process job under one-process AI automation, not a platform migration.
