Half your customers type "مرحبا" and the other half type "hi" — and a one-language bot loses one of those halves at the first message. If you run a clinic in Deira, a salon in Sharjah, or a real-estate desk in Business Bay, learning how to set up an Arabic WhatsApp chatbot (UAE) that switches cleanly between Arabic and English is the difference between a booked appointment and a silent chat that never gets a reply.
This guide walks through the real setup — not the theory. What you need, how language detection actually works, where Arabic breaks things, and how to stay on the right side of TDRA rules while you do it.
What "bilingual" really means on WhatsApp
A bilingual chatbot is not two separate bots bolted together. It is one flow that:
- Detects the customer's language from their first message (or asks once).
- Replies in that language for the rest of the conversation, including buttons and lists.
- Handles Arabic script correctly — right-to-left (RTL) text, Arabic-Indic numerals if you use them, and mixed messages like "أريد booking بكرة".
- Falls back to a human in the same language when the bot hits its limit.
The trap most people fall into is translating the English flow word-for-word. Emirati and Levantine Arabic customers rarely write formal Modern Standard Arabic in a chat — they write the way they speak. Your bot's copy should feel like a WhatsApp message from a helpful receptionist, not a government circular.
Before you build: get on the WhatsApp Business API
The free WhatsApp Business app can do canned "away" replies, but it cannot run a proper decision-tree bot, detect language, or send approved template messages at scale. For that you need the WhatsApp Business API (Cloud API). If you are still on the green app and unsure whether it is time to move, our guide on when your Dubai business should upgrade from the app to the API breaks down the trigger points, and the complete 2026 UAE API guide covers pricing, verification, and the Meta setup end to end.
You will need a Meta Business account, a verified business number (a new one or your existing line — you can migrate and keep the same number), and a platform to run the flows. Most UAE SMBs go through a provider rather than coding against Meta directly, because the provider handles template approval, the inbox, and the bot builder in one place.
Step 1: Set your language detection rule
You have three practical options. Pick one and keep it simple.
| Approach | How it works | Best for |
|---|---|---|
| Ask once | First message replies with "English / العربية" buttons; customer taps one | Most SMBs — clear, zero guesswork |
| Auto-detect script | Bot reads the first message; Arabic characters → Arabic, Latin → English | High-volume inbound where a tap adds friction |
| Default + switch | Reply in English but offer "للعربية اضغط هنا" on every menu | Businesses whose audience is majority English |
The ask-once method is the most reliable in the UAE because so many customers type Taglish-style mixes ("hello اريد موعد"). A single button tap removes all ambiguity, and you store their choice on the contact record so returning customers skip the question. Auto-detection is elegant but stumbles on one-word openers like "hi" followed by an Arabic sentence.
Step 2: Build each flow in native copy, not translation
Write the Arabic path from scratch. Keep sentences short. Use the customer's dialect register — friendly, direct, a little warm. A booking greeting might read:
- English: "Hi! Want to book an appointment? Tap a service below."
- Arabic: "أهلين! تحب تحجز موعد؟ اختر الخدمة من تحت."
Both should offer the same buttons and reach the same booking, reminder, and payment steps. If you are wiring the booking half of this, the mechanics are identical in either language — our walkthrough on setting up an AI booking bot on WhatsApp in 10 minutes shows the slot-picking and calendar logic you will mirror on both language branches.
Watch these Arabic gotchas
- RTL rendering: WhatsApp handles RTL automatically, but if you embed an English word or a phone number mid-sentence, test it on a real phone — punctuation and brackets can jump to the wrong side.
- Numbers: Decide early between Western digits (2:30) and Arabic-Indic (٢:٣٠). Western digits are safer for times, prices in AED, and dates that customers copy into their calendar.
- Emoji and buttons: Button labels have a character limit; Arabic words run longer, so test that "تأكيد الحجز" (confirm booking) does not truncate.
- Names and gender: Arabic verbs change with gender. "أهلاً وسهلاً" is safe and neutral — avoid guessing gendered greetings from a name.
Step 3: Get your templates approved in both languages
Any message you send outside the 24-hour customer-service window — appointment reminders, confirmations, promotions — must be a pre-approved template. In the UAE you submit these to Meta, and you should submit the Arabic and English versions as separate templates in the same category. Meta reviews Arabic copy on its own, so a rejected English template does not block the Arabic one.
Reminders are where bilingual bots earn their keep. A confirmation the day before in the customer's own language measurably cuts no-shows — the playbook in how to reduce no-shows at your UAE salon or clinic with WhatsApp reminders has the timing and message structure, and you simply duplicate the approved template into Arabic. If you need help getting the wording past review the first time, how to write a WhatsApp template that Meta approves covers the common rejection reasons — most of which apply to Arabic copy too.
Step 4: Stay TDRA- and opt-in compliant
The UAE takes unsolicited messaging seriously. Two rules to bake in from day one:
- Opt-in first. Only send marketing templates to customers who agreed to hear from you. A bilingual bot makes this easy: capture consent in the same conversation, in the same language, and log it against the contact.
- Honour opt-out. Give an Arabic and English way to stop ("للإلغاء اكتب إيقاف" / "reply STOP").
The full picture — including how to avoid a number ban — is in sending WhatsApp marketing messages in the UAE without getting banned (TDRA + opt-in rules). Getting consent right also keeps you clean under UAE PDPL when you store customer chat data.
Step 5: Route to a human — in the right language
No bot answers everything. Set a clear handover trigger (a keyword, a "talk to a person" button, or three failed attempts) and route the chat to a team member who reads that language. A shared inbox where staff see the whole thread and the detected language means an Arabic customer never gets bumped to someone replying in English. That team-visibility is exactly what a multi-agent WhatsApp inbox is for.
A realistic timeline
For a typical UAE clinic or salon, a working bilingual bot takes about a day of focused work: half a day to draft and refine both language flows, an hour or two to submit templates (approval lands within a day, usually much faster), and the rest to test on real phones with real Arabic and English messages. Do not skip the phone testing — RTL bugs only show up on the actual app.
Remarketly runs this whole bilingual setup — language detection, native Arabic and English flows, TDRA-safe templates, and a shared inbox with per-contact language memory — in one place, so you are not stitching a translator, a bot builder, and a CRM together yourself.
Start with one flow: a bilingual booking greeting with a clean language tap. Get that live, watch the replies come in on both sides, and expand from there.