Guides · 8 min read

Answering in Arabic and English without changing who you are

A bilingual inbox is not one inbox translated. Customers switch language mid-sentence, write Arabic in Latin letters, and expect the same brand on both sides. The teams that do this well made a handful of decisions early and then stopped thinking about it.

Mirror the customer, always

The rule is simple enough to put on a wall: answer in the language the customer wrote in. Not the language of your website, not the language of your team's internal chat, and not the one you personally write faster.

Someone who opens in Arabic and gets an English reply learns that the Arabic was tolerated rather than welcomed. It is a small signal and it lands every time.

Two edge cases worth deciding in advance:

• They switch mid-conversation. Follow them. People switch because the new topic sits more comfortably in the other language — technical details in French, frustration in dialect. Following is the polite move.
• They write Arabic in Latin letters (“wenou l commande mte3i?”). Answering in Arabic script is usually right and reads as warmer, but if they keep writing in Latin transliteration after your Arabic reply, they are telling you something about their keyboard. Switch to whichever they can read fastest, not whichever is more correct.

Dialect or Modern Standard?

This is the question that stalls teams for weeks. A workable answer: Modern Standard for anything written once and read by everyone, dialect for anything typed to one person.

Policies, help centre articles, automatic replies, the widget's own labels — Modern Standard. They are read across the region and they need to be unambiguous. Live replies in chat — the local dialect your customers actually speak, because that is what sounds like a person rather than a bank letter.

If your customers are spread across several countries and no single dialect fits, a light Standard Arabic — short sentences, everyday vocabulary, no formal clichés — is safer than picking one dialect and sounding foreign to everyone else.

Keep one voice, not two brands

The usual failure is subtle: the English replies are relaxed and direct, and the Arabic ones drift into heavy formality, because formal is what most people were taught to write. Now you have two different companies depending on which language you open in.

Fix it by writing the pair together. When you create a saved reply, write both versions in the same sitting, and read them one after the other asking a single question: would these two messages come from the same person? If the Arabic is three lines longer and opens with a blessing while the English opens with a first name, they would not.

Translate meaning, not sentences. “Sorry for the wait” has no good literal Arabic equivalent in chat; what the Arabic version wants is something closer to “I know that took a while, here is where we are” — the same intent, in a shape that language actually uses.

What right-to-left breaks, and how to check

Most chat tools were built left-to-right and had Arabic added later. The bugs are predictable, and they all look like carelessness to the customer:

• Mixed-direction sentences scramble. An Arabic message containing an order number or a Latin product name can render with the number in the wrong place. Fixed by declaring direction properly on the message, not by rearranging the text by hand.
• Punctuation lands on the wrong side. A question mark at the left of an Arabic sentence is the classic tell of a tool that was never tested in RTL.
• The layout doesn't mirror. The avatar stays left, the timestamp stays right, the chat bubbles point the wrong way. In a properly mirrored interface the whole conversation flips, not just the text inside it.
• Numbers and dates. Decide whether you use Arabic-Indic digits (٤٨٢) or Latin ones (482), then be consistent everywhere — order numbers, prices, tracking codes.

A five-minute test for any tool you are evaluating: send yourself a message in Arabic containing an order number, a price, a link and a question mark. If all four survive in the right places, in the customer's view and in the agent's, the tool was tested. If not, you will be working around it forever.

Routing: who gets the Arabic conversations

Language is the one routing rule almost every bilingual team needs and almost none set up. Tag each agent with the languages they actually answer in — not the ones on their CV — and send conversations accordingly. The alternative is the internal handoff, where a customer waits while their chat is passed to somebody who can read it.

Where you can't cover a language at all hours, say so rather than leaving people in a queue: “Our Arabic team is here 9–18. Leave your question and we answer first thing tomorrow” is a far better experience than a silent chat that eventually gets an English reply.

Bilingual help centres and the AI answer

If an assistant answers from your help centre, it can only answer in a language your help centre exists in. A customer writing Arabic to a knowledge base that only holds English articles gets the worst of both: either a confident answer translated out of English with the details rubbed off, or an escalation for a question you have already documented.

Rank your articles by how often they are asked, translate the top ten, and check that the assistant cites the Arabic article rather than the English one when the customer wrote in Arabic. Ten well-translated articles cover more real conversations than sixty machine-translated ones, and they do not put wrong policy in your voice.

Don't forget the agent's own screen

Bilingual support is not only about what the customer sees. If half your team reads Arabic more comfortably than English, the inbox itself should be available in Arabic — including the layout, mirrored properly — so nobody is doing their job in their second language all day. A person who reads their tools comfortably answers faster and makes fewer mistakes, in any language.