WhatsApp chatbot in the UAE (2026): Arabic and English in the same conversation

The summary in one table — how it works and what it costs

Meta's cost on our accounts ÷ its message countsample 120 daysmeasured 5 September 2026

Why one agent rather than two bots — and how it detects the language

The commonest mistake in the UAE is building an Arabic bot and an English bot with a menu at the start asking "choose your language". A customer in Dubai does not choose a language; they write English in the morning from the office and Arabic in the evening from home, may write «هل عندكم الطقم الأبيض in size M؟» in one sentence, and may write Arabic in Latin letters. A menu asking for their language loses half the audience on the first reply.

One agent works at the level of the message, not the conversation: it reads each message, decides its language, answers in it, and keeps the context before it. If the customer asks about delivery in English and then about the size in Arabic, the first answer comes in English, the second in Arabic and the order at the end in the language of the last message. The knowledge base is written once in both languages — delivery and return policy, the FAQ — and products are read from the store with the Arabic and English names as you entered them.

And why does this matter more in the UAE than in any other Arab market? Because Emirati and resident Arab customers mostly write in Arabic, while a large share of residents from South Asia, the Philippines and Europe write only in English — and all of them are on the same WhatsApp and the same number of yours. An agent fluent in English that does not understand «شو» and «وايد» loses the first group; one fluent in Arabic with poor English loses the second. A Dubai merchant cannot choose between them, so the bot should not force the choice.

Use cases in Dubai and Abu Dhabi — and what the agent will not do in each

Average order value in the UAE is far above the region's other markets, so an unanswered conversation costs more. These five cases are what we actually see, and each has a line the agent will not cross — which is what makes running it safe rather than merely fast.

The cost — in dollars and dirhams, from our own measurement

A WhatsApp bill is two bills: Meta's fees on messages you start, and the platform subscription. The misread part is the first: Meta bills per message, not per conversation, and replying to a customer who wrote first is free and uncapped. The figures below are not copied from a rate card; they are Meta's actual cost on our accounts divided by its message count, and the dirham is a conversion at the peg rather than a price we bill in — our UAE plan is in dollars.

The line that matters to a Dubai business specifically: the price follows the customer's number, not your address. UAE customers are of many nationalities and many carry numbers from home, so a Dubai store with half its customers on +971 numbers and half on Egyptian, Jordanian or Indian ones pays each message at the rate of that number's country. That is why the full table by number nationality is on the UAE pricing page.

Worked example — a Dubai store, 400 orders a month, all on Emirati numbers. Confirmation + "shipped" + "delivered" per order = 1,200 utility messages × $0.0157 ≈ $18.84 (about 69 dirhams) from Meta. Customer questions in English and Arabic — some two thousand conversations — are started by customers and cost zero. With the subscription: about $59 a month for everything. A bulk marketing message? We do not publish its UAE rate because we have not been billed for one yet.

The steps — from the number to the first bilingual conversation

1. The number

   Create the account with no card and connect a +971 number through the official WhatsApp Cloud API from the dashboard. Is the number on the WhatsApp Business app now? Move it with coexistence mode and keep your chats and contacts.

2. The business account and verification

   A Meta business account, then business verification with the trade licence. Verification opens the higher sending tiers and the official name, and does not stop you starting and testing before it.

3. The agent: language on "auto"

   Create the agent and answer its questions — how the service is ordered, delivery times per emirate, the return policy, when to hand to a person. Language "auto" so it detects each message's language; Arabic dialect "Gulf".

4. The knowledge base in both languages

   Write the delivery and return policy and the FAQ in Arabic and English in the same base, upload a PDF, or give it your website link. Products are not uploaded: they are read from the store at the moment of the question with both names as you entered them.

5. The store and the channels

   Connect Shopify, Salla or WooCommerce with one approval, then add Instagram and Messenger to the same inbox. The same agent on all of them.

6. The three-message test, then go live

   "Do you deliver to Abu Dhabi?" then «وكم يوم يوصل؟» then "ok yalla اطلب لي واحد" — and a voice note. Watch the first two days from the app, and close the "questions it did not know" list with a line per question it learns for next time.

Three mistakes we see in UAE accounts specifically

First: locking the agent to one language "because most of our customers write in English". Most is not all, and the other half discovers from the first reply that it is talking to a machine that does not understand it, gives up and calls. The right setting is always "auto", even when ninety per cent of your customers use one language; the setting costs nothing and the tenth customer costs an order.

Second: a knowledge base in English only, relying on translation at reply time. The agent does translate, but translating the return policy on the fly produces formal MSA in front of a customer who wrote «شو نظام الاسترجاع عندكم؟». Write the items that matter — delivery, returns, payment — in both languages in the same base, in Arabic a Gulf customer reads, and the agent answers with the text you wrote rather than a translation of it.

Third: a marketing campaign in one language to the whole list. An Arabic message to a customer who only ever wrote in English gets reported more, and reports lower the number's quality rating and its sending limit. The inbox keeps each customer's last-message language; get two templates approved — Arabic and English — and send each to its segment. It is also the cheaper way, since a marketing message is the dearest category and there is no need for it to be reported.

Frequently asked questions