Arabic and English customers in one inbox
A team serving Arabic and English customers works well with one shared inbox, a clear rule that every customer is answered in the language they wrote in, and published answers written properly in both languages rather than translated on the fly. Put the people who write good Arabic and good English on the rota so each shift covers both, and let colleagues help each other through internal notes. This guide covers the rota, the writing, the widget and the mistakes that make a bilingual business look careless.
The one rule
Answer in the language the customer used. If they switch, switch with them. If they write in Arabic with English words mixed in, which is common in the UAE, answer in Arabic and keep the product names and numbers as they wrote them.
This sounds obvious, but it fails in two ways: the person on shift only writes one language well, or the ready-made answers exist in only one language. Both have simple fixes.
Cover both languages on every shift
| Shift | Arabic | English | Fallback |
|---|---|---|---|
| Morning | Sara | Sara | Ali (Arabic) |
| Afternoon | Ali | Meera | Sara (both) |
| Weekend | Omar | Omar | Owner |
If one shift has only one language, decide in advance what happens: the person on shift sends a short holding reply in the customer's language ("Thank you, a colleague will reply in Arabic within the hour") and assigns the conversation with a note.
Write your answers twice, not once and translated
Your published answers to common questions (hours, prices, booking, delivery, returns) should exist in Arabic and English, each written to read naturally.
- Write the Arabic as Arabic. Machine translation of a friendly English answer often produces stiff or odd Arabic. Have a fluent writer write it, or at least rewrite it.
- Choose a register and keep it. For customers across the Gulf, clear modern Arabic travels well. A business serving one community may prefer its local dialect; either is fine if it is consistent.
- Keep numbers, prices and times identical in both versions. The same price list should feed both.
- Keep product and brand names as customers know them, often in Latin letters.
In StayReplied, knowledge documents and price records are drafted, reviewed and published, with every version kept, as the docs describe. Write the Arabic and English answers side by side and publish them together, so neither falls behind; ready-made replies that don't sound canned has wording tips for both.
The widget in both languages
StayReplied's website chat widget is available now and shows Arabic right to left correctly. In its settings you write a welcome message in English and a separate one in Arabic, choose the default language, and list starter questions (ten welcome messages to copy). On the home page the promise is stated plainly: the app, the web chat and your replies work in Arabic and English, right to left included. That covers the people answering too: your team can use the app in either language.
Check one thing on your own site: open it in Arabic on a phone and confirm the chat opens on the side and in the direction you expect, with the Arabic welcome message.
Helping across languages without double replies
When the owner of a conversation is stuck on a phrase or a reply in their weaker language, a colleague helps in an internal note: "Suggested Arabic: …". The owner sends it. The customer gets one reply in one voice, and the note shows who helped. Internal notes look different from customer messages, so there is no risk of sending the suggestion by accident.
Mistakes that make a bilingual business look careless
- Answering an Arabic message in English because the person on shift was more comfortable. The customer reads it as "you're not for us".
- Two prices, because the Arabic answer was written last year and the English one updated.
- Half-translated replies, an Arabic greeting followed by an English paragraph.
- Dialect clashes, a Gulf customer answered in a strong dialect from elsewhere, or the reverse. Pick a neutral register for written answers.
- Wrong-direction text, numbers and Latin product names jumping around in right-to-left text. Read your Arabic replies on a phone before publishing them as standard answers, and include a few Arabic chats in your weekly quality review.
What about AI in two languages?
No plan includes AI today, but if you add your own Anthropic key, StayReplied's AI replies can answer in the customer's language from your published knowledge, with your tone, length and language instructions. The answer mode (off, draft for a person, or answer) is set per channel. For a bilingual team, drafts are a useful start: the AI drafts, and a fluent person checks the Arabic before it goes out.
When this is not for you
If your customers write in a third language, such as Hindi, Urdu or Tagalog, StayReplied's app and widget languages today are Arabic and English; your team can still type replies in any language, but the interface will not be in it. And if most of your Arabic-speaking customers reach you on WhatsApp, web chat is the channel you connect today and WhatsApp is coming soon (integrations); who StayReplied is for sets out the teams it fits today. Prices for each plan are on the pricing page.
Questions and answers
Should we answer in Arabic if the customer writes in Arabic?
Yes. Answer in the language the customer used, and switch if they switch. Keep product names and numbers as they wrote them.
Can one inbox handle Arabic and English chats?
Yes. In StayReplied the app, the web chat and your replies work in Arabic and English, right to left included.
Is machine translation good enough for our standard answers?
Usually not for Arabic. Have a fluent writer write or rewrite each answer so it reads naturally, and keep prices identical in both versions.
Can the chat widget greet visitors in Arabic?
Yes. The StayReplied widget has a separate welcome message for English and for Arabic, and a default language setting.
Serve both languages from one inbox.
start your free trial, 14 days, no card needed.