
Replying to Arabic DMs without sounding like a bot
In much of MENA the DM is the checkout. Why replying in fusha to a dialect message costs you the sale, and how to hold response times without falling back on templates.
In much of the region the DM is not customer support. It is the checkout. A customer asks the price, gets an answer, and pays — without ever seeing a product page. Which means the reply is not an aftercare cost, it is the conversion step.
Should you reply to Arabic DMs in dialect or fusha?
Match the sender. When a customer writes in dialect and the reply comes back in formal fusha, it reads as a form letter — and across much of MENA the DM is where the sale actually closes, so that costs revenue rather than only warmth. Speed matters too, but a template is not speed.
Why the register of the reply matters
Someone writes to you in Saudi dialect. You reply in Modern Standard Arabic. Nothing was wrong with your reply, and something just changed: the exchange stopped feeling like a conversation and started feeling like a form. Distance, in a moment where distance costs money.
The rule is simple and almost never followed: reply in the language of the last inbound message. If they wrote Egyptian, answer Egyptian. If they wrote English, answer English. If they wrote fusha, answer fusha — they chose it.
What breaks response times
- Templates. They hold the speed and lose the register. A templated reply in the wrong dialect is worse than a slow one in the right dialect.
- One inbox per platform. Instagram in one tab, Facebook in another, X in a third. Nobody sustains that, so one platform quietly goes unanswered.
- No target. "We reply quickly" is not a target. A number is.
What actually works
- One inbox for every platform. The tab-switching is the reason replies get slow, not staff effort.
- Drafts, not templates. A draft that already matches the sender's dialect, edited before sending, keeps both speed and register.
- A response-time target you can see. Measure it or it drifts.
- Assignment. Two people replying in one inbox with no ownership means duplicate replies and missed ones.
- Saved replies for facts only. Shipping times and return policy are facts and can be saved. Tone cannot.
The one thing not to automate
Do not auto-send. Draft automatically, send deliberately. An AI-drafted reply that goes out unread will eventually invent a price, a delivery date or a discount — and in a market where the DM is the checkout, that is a commitment you did not make.
The four replies you write every day
Most of an Arabic inbox is four questions. Writing them properly once, in your market's dialect, removes most of the pressure that pushes teams back onto templates. These are Saudi; swap the markers for your own market.
«بكم؟» — the price question, and the most common message in any Arabic inbox.
- Fusha: «يبلغ سعر المنتج ٣٠٠ ريال». Correct, and reads like a catalogue.
- Dialect: «٣٠٠ ريال — وفيه توصيل مجاني فوق ٥٠٠». Answer first, then the useful extra.
«متوفر؟» — availability.
- Dialect: «إي متوفر، وعندنا منه لونين». Never just «نعم»; a one-word reply reads as a bot.
«وصل وين؟» — where the order is.
- Dialect: «طلبك خرج أمس، ويوصلك بكرة إن شاء الله». Give the state and the date, not a tracking link alone.
A complaint.
- Dialect: «آسفين والله، هذا غلط منا — نعالجه اليوم». Apologise plainly, own it, give a time. This is the one case where dialect helps most and fusha hurts most, because fusha under complaint reads as a form letter.
Write these four for your market, keep them where the team can see them, and let people vary the wording. That is the difference between a starting point and a template.
One more thing they don't cover: the messages that arrive at two in the morning. Rather than answering badly to look fast, set an away message that states real hours in your market's dialect and then keep to them. A stated window that you meet builds more trust than an unstated one you miss.
Where to start
- Bring every platform into one inbox.
- Set a response-time target and watch it weekly.
- Reply in the sender's dialect, always.
- Save facts as replies; never save tone.
Intilq brings comments, DMs and mentions into one inbox with dialect-aware drafted replies you approve before they send. See features and pricing.