The Bilingual Lead Reply
Draft replies to Arabic and English enquiries that match tone and context in each language
Direct translation fails because formality levels, greeting conventions and persuasion patterns differ between Arabic and English. A casual English tone becomes inappropriately informal in Arabic, and formal Arabic sounds stiff in English.
That is the gap this drop closes. It is a sales & leads skill built for Claude, and it takes about ten minutes to set up the first time. After that it runs in under a minute.
Who should use it
Sales teams in the UAE handling enquiries in Arabic and English
How it works
The skill file does five things, in this order.
1. Set your reply standards for each language. Tell Claude the level of formality, typical greetings and how directly you state price or next steps in Arabic versus English.
2. Paste the enquiry without translating. Give Claude the original message in whichever language it arrived so it can detect tone and regional phrasing.
3. Ask for cultural context notes first. Before drafting, have Claude flag formality signals, honorifics or expectations the enquiry contains.
4. Request the reply in the enquiry language. Claude drafts in Arabic or English to match the customer, preserving appropriate formality and structure for that language.
5. Check for translation artifacts. Review for English sentence patterns forced into Arabic or Arabic politeness formulas that sound odd in English.
What comes back
A reply that feels native in Arabic or English, respecting the cultural expectations each language carries in the Gulf market
The mistake to avoid
If you serve both Khaleeji and Levantine customers, specify which Arabic dialect conventions you follow for greetings and closings. Claude can maintain Gulf formality standards even when the enquiry uses Levantine phrasing, but you need to tell it your house style.
Running it
Save this as SKILL.md inside a folder named after the skill, then drop the folder into your Claude Code skills directory or upload it to a Claude Project. Claude reads the frontmatter to decide when the skill applies, so keep the description line intact. For a one-off run, paste the prompt block directly.
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 are helping me reply to a sales enquiry. I need the reply to feel natural and appropriate in the language the customer used.
My reply standards:
- Arabic: {formality level, e.g. formal Gulf business style / moderately formal / friendly but respectful}
- Arabic greetings: {your preference, e.g. السلام عليكم for all / vary by time of day / match customer's opening}
- English: {tone, e.g. professional and warm / concise and direct}
- Pricing mention: {approach, e.g. always state in first reply / only if asked / invite call to discuss}
- Next step: {your default, e.g. propose meeting / ask qualifying question / send brochure link}
Here is the enquiry I received:
"""
{paste the customer's message exactly as it arrived}
"""
First, give me three brief observations:
1. Language and formality level the customer used
2. Any honorifics, titles or politeness markers present
3. Urgency or timeline signals if any
Then draft a reply in the same language as the enquiry, matching the appropriate formality and cultural expectations for that language in a UAE business context. Keep it under {word count or sentence count} and include {any specific elements: our availability, the product name, a question to qualify budget, etc.}.