Building AI agents for the GCC

In the Gulf, the commercial conversation often starts on WhatsApp — not a web form, not email, and not a phone tree. Property, home services, clinics, distributors and ecommerce teams already take enquiries there. An AI agent that cannot live in that channel is an agent customers will never meet.

That changes the architecture. Identity, consent and lead ownership have to survive a chat thread. Arabic and English need approved phrasing, not a translation layer bolted on at the end. Working hours run on Gulf time; an India-based delivery team can work async, but handoff copy has to say when a person will actually reply — “a colleague will pick this up at 09:00 GST” is clearer than pretending the bot is a night shift.

Data handling is not optional packaging. The UAE Personal Data Protection Law covers collection, purpose, access and cross-border transfer. Saudi Arabia and the other GCC states are not the same regime. A project that stores chat logs, IDs or booking data should document what is collected, where it sits, how long it stays and who can see it — then get counsel for the specific countries and sector. This hub is an engineering map, not legal advice.

The three notes below are the practical starting points we use with UAE and GCC teams: WhatsApp agents with real system actions, CRM plus WhatsApp lead routing, and internal web applications that keep operations off spreadsheets.