Email + WA03 Aug 2026 · 7 min read · how-to

Bilingual Email and WhatsApp Campaigns

Run English and Arabic lifecycle campaigns properly: when to split lists, RTL email, WhatsApp tone, translators vs copywriters, and UAE cultural timing.

Bilingual in the UAE is not a Google Translate plugin. It is two (or more) customer realities sharing one city: English-dominant expats, Arabic-preferring residents and nationals, and a huge middle that code-switches daily. Brands that “support Arabic” with a broken footer lose trust faster than brands that do English excellently and Arabic selectively—but honestly.

This how-to covers when to go dual-language, how to build EN/AR email and WhatsApp without double the chaos, and cultural timing that is not performative.

Decide the bilingual level

Level	What you do	Who it fits
0	English only, excellent	Niche expat brands with proof audience is EN
1	Arabic key paths only	Website CTAs, WhatsApp greeter, ads
2	Full dual lifecycle	National audience, gov-adjacent, family brands, many retailers
3	Arabic-first	Brands whose buyers primarily prefer AR

Do not jump to level 2 with machine translation and no reviewer. Level 1 done well beats level 2 done poorly.

Data: language as a field, not a guess

Capture preference via:

Form toggle
WhatsApp first-language mirror
Last campaign click language
Explicit preference centre

Avoid ethnicity guessing from names—error-prone and awkward. Mirror the language the customer writes in until they switch.

Email production workflow

Write the master in the stronger brand language (often EN for international DTC; sometimes AR for local-first brands)
Transcreate, do not translate—offers, idioms, humour change
Native review for CTA length (Arabic can run longer)
Separate templates for RTL
QA on mobile with images off
Segment sends; do not staple AR below EN in one blob for long newsletters

RTL checklist

Mirrored layout
Correct Arabic fonts that load in clients
Numbers and English brand names rendering cleanly
Buttons still full-width
Unsubscribe and legal lines also in Arabic for AR sends

WhatsApp bilingual patterns

Short dual greeter is fine:

Welcome / أهلاً بك Reply EN or ع for العربية

Then commit to one language per conversation. Quick replies duplicated. Voice notes: agents should be competent or hand off—bad Arabic voice notes damage premium brands.

Sample Arabic templates and chat lines

أهلاً بك في [العلامة]. كيف نقدر نساعدك اليوم؟ (Welcome to [Brand]. How can we help you today?)
تفضّل العربية أو English؟ (Would you prefer Arabic or English?)
موعدنا المؤكد: يوم الثلاثاء 4 مساءً في جميرا. لل إلغاء قبل 24 ساعة. (Confirmed appointment: Tuesday 4pm in Jumeirah. Cancel at least 24 hours ahead.)
سلة التسوق بانتظارك — أكمل الطلب خلال 12 ساعة واحصل على توصيل مجاني داخل دبي. (Your cart is waiting — complete within 12 hours for free delivery inside Dubai.)
شكراً لتواصلك. إليك عرض السعر: من 450 درهماً شامل الضريبة. (Thanks for reaching out. Your quote: from AED 450 incl. VAT.)
Subject (email): عرض إفطار رمضان — احجز قبل اكتمال المقاعد (Ramadan iftar offer — book before seats fill)

Templates: submit EN and AR versions separately on the API; map user language to template language.

Cultural timing and tone

Ramadan: respect energy levels; post-Iftar windows; less aggressive scarcity theatre; food brands especially careful
Eid: warm, not spammy “BUY BUY” at prayer-sensitive moments
National Day / Commemoration: sincere, short; do not force every furniture brand into hollow patriotism
Summer: many residents travel—logistics honesty > fake urgency

Tone: Gulf Arabic vs MSA vs dialect choices depend on brand. Luxury often leans polished MSA-ish; youth brands may use lighter dialect with a careful editor. Hire humans who know the difference.

Offer and proof differences

Sometimes the offer stays the same but proof changes:

AR creative emphasises family, local reviews, Arabic-speaking staff
EN creative emphasises delivery speed for expats, English support hours

Prices in AED remain consistent. Dual pricing games destroy trust.

Org model for small teams

One lifecycle owner
EN copywriter + AR copywriter (freelancer retainer beats random staff cousin)
Shared brief with audience, offer, proof, CTA, legal notes
Single approval calendar so AR does not ship two days late and miss the promo

Budget: serious AR transcreation might be AED 200–800+ per email depending on length and seniority—still cheaper than a failed campaign to the wrong language.

Illustrative scenario: family entertainment brand

They sent English-only emails with high open among expats but weak show-up from Arabic-preferring parents who discovered them on Snapchat AR ads. Fix: AR WhatsApp booking flow + AR reminder templates + monthly AR email for school-holiday camps. English remains for the expat segment. Same rides, two communication designs.

QA script before every dual send

Segments mutually exclusive?
Links locale-correct?
AED and dates unambiguous?
WhatsApp templates approved in both languages?
Tone respectful for the calendar week?
Native speaker read the final, not the draft only?

What not to do

Auto-translate entire Klaviyo flows overnight
Mix AR and EN randomly mid-sentence in long form
Use screenshot images of Arabic text (bad for accessibility and rendering)
Assume all Emiratis want Arabic and all Indians want English—preference > passport

Tie-ins

Consent language versions: PDPL. Seasonal planning: Ramadan calendars. Design: Mobile-first email.

Bilingual excellence is a competitive moat in the UAE because most SMEs either ignore Arabic or fake it. Choose a level you can staff, then execute with the same rigour you give English creative.

Glossary and terminology control

Build a living glossary: product names, procedure names, fabric types, legal phrases. Inconsistent Arabic for the same SKU confuses customers and SEO/content teams alike. Share the glossary with ads, packaging, and support.

When mixed-language is intentional and good

Young audiences sometimes expect EN with Arabic interjections in social—but lifecycle email still prefers clean single-language messages for scannability. WhatsApp can be more flexible mid-chat if the customer mixes; agents should not force purity.

Hiring and freelancers

Ask for:

Portfolio of UAE or GCC work, not only MSA textbook samples
Willingness to work from briefs and glossaries
Revision rounds included
Understanding of WhatsApp length limits and template variables

Rate quality with native staff or customers—not only with the EN copywriter’s approval.

Measuring bilingual performance fairly

Do not crown English “better” because the EN list is older and more engaged. Compare:

Click and conversion within language cohorts of similar recency
Booking completion rates
Block/report rates on WhatsApp by language template
Support tickets caused by unclear translation

Sometimes AR underperforms because the offer is wrong, not because Arabic “doesn’t work online.” Fix strategy before abandoning the language.

Part of the Dubai Marketing Playbook by Shabang — practical marketing for UAE businesses.