Arabic AI customer service: dialects, tone and what to check before you choose

What does an Arabic AI customer service tool need to understand?

Customers rarely write to a shop in Modern Standard Arabic, the formal Arabic of news and contracts. They write the way they speak. A customer in Riyadh, one in Cairo and one in Beirut can ask the same question with almost no words in common.

So "supports Arabic" is not enough. A useful tool has to read dialect, read Arabic written in Latin letters, cope with Arabic and English in one message, and still answer from your real prices and policies. If it only understands formal Arabic well, it will misread a large share of real messages or answer them in a way that feels foreign.

How do Gulf, Egyptian, Levantine and Maghrebi Arabic differ in customer messages?

The differences show up in the everyday words customers use most: asking a price, saying what they want, asking when and where. The table shows common forms. Usage varies by country, city and person, so treat it as a guide, not a rulebook.

Maghrebi Arabic, spoken in Morocco, Algeria and Tunisia, is the hardest for most systems. It mixes in many French words, such as livraison for delivery, and it is often typed in Latin letters. If you sell in North Africa, put it at the top of your test list.

Can an Arabic chatbot read Arabizi and mixed Arabic-English messages?

Arabizi is Arabic typed with Latin letters and numbers. Numbers stand in for sounds English letters lack: 3 for ع, 7 for ح, 2 for ء, 5 for خ, and in the Gulf 9 is often used for ص or ق. Younger customers and people typing on a phone without an Arabic keyboard still use it.

Code-switching is just as common: one sentence in Arabic, a product name or a whole phrase in English. A good system treats this as normal and answers in the language the customer leads with, instead of getting confused or switching to English for no reason.

• "3ndkom tawseel lel riyadh?" means عندكم توصيل للرياض؟ (Do you deliver to Riyadh?)
• "kam el se3r?" means كم السعر؟ (How much is it?)
• "abi el size L, is it available?" mixes Gulf Arabic and English in one line.

Should an AI reply in Modern Standard Arabic or in dialect?

Both can be right. Modern Standard Arabic reads as polite and neutral, and every Arabic reader understands it. It suits banks, clinics, government-facing services and brands that serve many countries. But in a casual chat it can sound stiff, like a letter from an office.

A light dialect reply sounds local and warm. A Riyadh perfume shop answering "إي نعم، نوصل للرياض خلال يومين" sounds like a person behind the counter. The risk is choosing the wrong dialect: a Gulf customer answered in strong Egyptian slang, or the reverse, notices at once.

A practical rule: pick one dialect that matches your main market and keep it light, or use clear Modern Standard Arabic if your customers come from many countries. Whatever you choose, keep figures, dates and order numbers exact and written plainly, and let the tone stay the same from the first message to the last.

What about right-to-left text and Arabic numbers?

Arabic runs right to left, but prices, phone numbers, order codes and English product names run left to right inside it. Badly handled, a reply like "the 50 ml bottle is 150 SAR" can come out with the numbers in the wrong place or the punctuation on the wrong side.

Check this on a real phone, not only on a desktop preview, and decide whether you want Western digits (150) or Arabic-Indic digits (١٥٠). Many Gulf customers read both. Consistency matters more than the choice.

• Send a reply that mixes Arabic, a price and an English product name, and read it on a phone.
• Check that order numbers and phone numbers are not reversed or split.
• If your team uses the dashboard, check that it works properly in Arabic, not only the customer-facing replies.

How do you test an Arabic AI vendor before you choose?

A demo written by the vendor proves little. Use your own messages. Read your last fifty conversations, list the dialects and habits in them, and turn the most common ones into a test set. Then run it before you sign.

• Send the same question in each dialect you actually receive, and read the answers aloud.
• Send two or three questions in Arabizi and one that mixes Arabic and English.
• Ask for a price and stock level that exist in your catalogue, and one that does not. The tool should say it does not know rather than invent.
• Switch language halfway through a chat and see whether it follows you.
• Send a voice note in dialect and check that the answer shows it understood.
• Ask for a refund or complain angrily, and check that a person on your team is brought in.
• Read every reply on a phone to check right-to-left layout and numbers.

How does Yusr handle Arabic dialects?

Yusr, our AI employee for customer chats, detects the language of each message, replies in it and switches when the customer does. For Arabic replies you can choose the dialect, such as Gulf, Levantine or Egyptian, or set one fixed language instead of matching. Prices and stock come from your own catalogue, not the AI's memory, and you can try the saved agent in a test chat before it answers anyone. The dashboard itself works in Arabic, English and Turkish.

Voice replies, on Basic and above, come in Modern Standard Arabic plus Saudi, Emirati, Qatari, Egyptian, Jordanian, Palestinian, Syrian, Lebanese and Iraqi, with English and Turkish. That list has no Maghrebi dialect, and we make no specific promise about Arabizi. If those matter to you, run the tests above in the test chat with your own messages first.