Short answer
Choose an Arabic AI customer service platform by testing eight things: dialect understanding, real task completion, confirmation before actions, handover to people, data residency, certifications, audit trail, and setup. Test each with your own customer messages in a live demo, not a scripted one.
1. Does it understand the Arabic your customers write?
Customers in the Gulf write in dialect, mix Arabic and English in one message, and sometimes write Arabic in Latin letters. A platform that only handles formal Modern Standard Arabic will miss much of this.
Test: send real messages from your inbox in Gulf, Levantine or Egyptian Arabic, including one mixed with English. Check that it understands and replies in the customer's language.
2. Does it complete the task, or only answer questions?
Answering "What are your opening hours?" is the easy part. The value is in finishing requests: booking, moving or cancelling an appointment, logging a maintenance request, updating a record.
Test: ask it to book a slot, then move it, then cancel it. Check your calendar or system after each step.
3. Does it confirm before it acts?
An AI that changes a booking or a record on a misunderstanding creates work for your team and a bad experience for the customer.
Test: check that it shows the exact details and waits for the customer's yes before anything changes, and that you can require a person's approval for regulated actions.
4. What happens when it cannot help?
Every AI reaches requests it should not handle. What matters is whether your team receives the request with the customer's details and history, or whether the customer has to start again.
Test: ask something outside its rules and look at what the person on your team receives.
5. Where does the data live?
Ask separately about storage and backups, AI processing, and operations access. "Hosted locally" can cover one of these and not the others.
Test: ask for the cloud region by name for each, and whether in-country or on-premise deployment is available if you need it.
6. Which certifications are real and current?
Ask for the ISO/IEC 27001 certificate number and scope, and for the SOC 2 Type II report period and auditor. Ask whether customer data is ever used to train models.
7. Can you see and export everything it did?
For regulated teams, every conversation and action should be logged with what was done and why, and exportable for an auditor.
8. How long to go live, and on which channels?
Ask how long setup takes with your own knowledge and systems, and whether WhatsApp runs on the official WhatsApp Business Platform. Check that WhatsApp, web chat and email work from one setup, so you do not build a separate flow for each.
Demo scorecard
- Understood a mixed Arabic and English message and replied in Arabic
- Booked, moved and cancelled, and the calendar matched
- Confirmed details before every change
- Handed over with the customer's details and history
- Named the region for storage, AI processing and access
- Shared certificate number, scope and report period
- Showed an exportable log of the conversation and actions
- Gave a realistic setup time for your own systems
Where Eshal stands
For reference, Eshal works in Gulf, Levantine and Egyptian Arabic and 56+ languages, completes tasks such as booking, moving and cancelling, confirms before it acts, and hands over with the details collected. Customer data is stored in Microsoft Azure UAE North, with KSA residency and on-premise options. It is ISO/IEC 27001:2022 certified, has a SOC 2 Type II report, is a Meta WhatsApp Tech Provider, and typically goes live in one day.