Email Prompts That Work in Arabic and English
Write AI instructions that handle both languages without breaking tone or context
Prompts that work in English produce stiff, literal Arabic replies. You waste time rewriting AI drafts because they miss formality cues or mix registers between languages.
That is the gap this drop closes. It is a operations skill built for Gemini, and it takes about ten minutes to set up the first time. After that it runs in under a minute.
Who should use it
UAE professionals who switch between Arabic and English email daily
How it works
The skill file does five things, in this order.
1. Flag language and formality separately. Tell Gemini the reply language and the relationship level as two distinct variables, not one instruction.
2. Give Arabic tone anchors, not translations. Show Gemini example phrases in Arabic that match the formality you want, instead of asking it to translate English tone.
3. Map greeting and closing conventions by context. List which Arabic greetings and sign-offs to use for government, vendor, internal team, and client emails.
4. Handle mixed-language threads explicitly. Instruct Gemini what to do when the incoming email contains both Arabic and English, and which language takes priority in the reply.
5. Test with real bilingual samples. Run the prompt on five past emails that switched languages or mixed formal and casual Arabic to catch register errors.
What comes back
Email drafts that respect Arabic formality norms and code-switch naturally when your inbox does
The mistake to avoid
Gemini sometimes defaults to Modern Standard Arabic even when the incoming message uses Gulf dialect markers. Add a line specifying register match: reply in the same variety of Arabic the sender used. This prevents awkward formality mismatches in casual internal threads.
Running it
Save the prompt as a Gem so it is reusable, or paste it into Gemini with your files attached. If the task touches Sheets, Docs or Gmail, run it from the Workspace side panel so it can read the file you already have open.
Where this fits
On its own, one skill saves an hour a week. The compounding happens when three or four of them run in sequence on the same input, the same transcript that produces a scope of work also produces the follow-up email and the project brief. That is the point at which it stops being a prompt and starts being an internal tool. If you want that wired into the systems your team already uses, that is the work 67 Digital does.
In the file
You draft email replies in Arabic and English for a UAE professional.
Language rules:
If the incoming email is in Arabic, reply in Arabic.
If the incoming email is in English, reply in English.
If the email contains both languages, prioritize {primary_language} unless the question is asked in the other language.
Arabic formality:
For government entities: use تحية طيبة، الاحترام والتقدير، and full formal register.
For external clients: use السلام عليكم، تحياتي، and respectful tone.
For vendors: use مرحباً، شكراً لتواصلك، and professional but direct tone.
For internal team: match the sender's register, allow some informality if they use it.
English formality:
Government and senior clients: Dear, Respectfully, full sentences.
External clients: Hi, Best regards, polite but efficient.
Vendors: Hello, Thanks, direct and clear.
Internal team: match sender's tone.
Content:
Address the main question or request in the first two sentences.
If information is missing, ask for it specifically.
If action is needed, state the next step and timeline.
Keep replies under 120 words unless detail is required.
Context:
Sender: {sender_name}
Relationship: {relationship_type}
Incoming email summary: {email_summary}
Any missing information I need: {missing_info}
Draft the reply now.