Which WhatsApp AI Actually Does the Work? 13 Tools Compared for MENA

Every platform on this list will tell you it has an AI agent. That word now covers two very different products, and the gap between them is the whole decision.

The question that separates them is whether the agent can change something in a system you own, and who builds that. Checked on 19 September 2026, the tools that publish documentation for an agent calling your own API include respond.io, SleekFlow, Infobip, Yellow.ai and Meta itself. Interakt and Zoko package commerce actions for Shopify stores instead of exposing a general one. Gupshup and Unifonic describe enterprise agents that act across connected systems. Twilio and 360dialog sell the infrastructure and expect you to bring the agent, and Twilio's AI Assistants developer preview is retiring in July 2026 in favour of Agent Connect. Wati's own AI operates mainly inside Wati. In every one of those cases somebody still has to build the action against your store, your CRM and your courier account, test it, and repair it when an API changes. That is the real product difference: not whether actions are possible, but whether they are your job. plumcut is the option where they are not.

How this comparison was prepared

This is a documentation based buying guide, not a hands on benchmark and not a ranking by score. Every capability claim below comes from the named vendor's own published product or documentation pages, checked on 19 September 2026, and links to the page that states it. Where a vendor publishes a capability only on a marketing page rather than in developer documentation, we say so, because that difference tells you how much detail you will find when you start building.

Prices are deliberately absent. They move, and we cover the pricing shapes separately in the best WhatsApp automation tools, honestly compared. This guide is about one axis only: what the agent is documented to do beyond replying. The observations about Arabic language websites come from our earlier comparison, checked on 11 September 2026.

plumcut sells a managed WhatsApp service and is one of the options below, so read our own entry with that in mind. We name the buyers each competitor suits better, and we mean it.

The table

Meta Business Agent: the new floor, not the ceiling

Meta announced in June 2026 that it was expanding Business Agent to businesses of all sizes globally, that more than a million businesses were already using one on WhatsApp and Messenger, and that it was free to activate, with paid subscription options signalled for later. The developer documentation describes knowledge sources plus custom connectors to external APIs so the agent can take actions on the business's behalf.

Take it seriously, because it resets what "answers customers" is worth. Then read the eligibility rules: the number must be on the Cloud API, the business must be in an authorised country and an eligible vertical, with finance, government, health, alcohol, gambling, over the counter drugs and matrimony excluded, and one number cannot run two competing messaging products at the same time. That last rule is the one to plan around, because it makes this an either or decision for your main number.

Choose it when answering is the whole job and you have someone who can build and maintain connectors when it is not.

The platforms where the agent can call your API

respond.io is the most explicit of the group. Its AI Agent Actions include a Make HTTP Requests action that lets the agent call external APIs mid conversation, ask the contact for any missing field first, then interpret the response and reply from it. The documentation states a limit of ten HTTP request actions per agent. Agents can also update contact fields and lifecycle stages, manage tags and trigger workflows. Ten actions is enough for a focused commerce agent and a real constraint on a sprawling one.

SleekFlow takes a similar position through AgentFlow. Its help centre documents custom API integrations that let an agent retrieve external data, trigger actions or update records during a conversation, with integrations and endpoints enabled per agent under Configuration then Actions, alongside connectors for Shopify, HubSpot and Salesforce.

Both are good buys if you have an operations person who enjoys this. Both leave the building, testing and repair with you.

Wati deserves a precise reading. Its AI Support Agent, formerly KnowBot, answers from your content, and its Bring Your Own AI feature lets you attach your own agent as an operator with a token for Wati's public APIs, which cover sending messages, updating contacts, reassigning and resolving chats. Wati also publishes an MCP server for contacts, conversations, templates and campaigns. Those are actions inside Wati. Acting inside your store or your ERP is a separate build, usually through a workflow tool.

The commerce packagers

Interakt publishes packaged WhatsApp AI agents for order management: tracking, cancellations, modifications and returns, synced with Shopify or WooCommerce, described on its product pages rather than in public developer documentation. Zoko is Shopify first and documents in conversation commerce actions plus Zoko Flows for order modification and returns, again mostly on product and blog pages.

For a single Shopify store with standard flows, this packaging is the fastest route to actions that work, and you should take it. The trade is scope: you get the actions the vendor decided to build, and when your process sits outside them, you are back to a person retyping.

The enterprise stacks

Infobip documents AgentOS agents that use external systems as tools, and Answers chatbots that call external APIs and receive webhooks back for confirmations. Gupshup describes agents with integrated tools that connect to enterprise systems in real time, with examples such as returns and payment reversal handled without a human agent stepping in. Yellow.ai documents an automation module for designing workflows that call APIs, update databases and complete backend tasks, plus a library of prebuilt enterprise integrations, and states right to left Arabic support in its v3 chat widget.

All three are credible if you have a procurement process, an integration budget and an internal owner. All three are heavy for a brand doing a few thousand conversations a month.

Unifonic is the regional entry worth knowing. It is headquartered in Saudi Arabia, states that it integrates with CRM, identity verification, ecommerce platforms and internal tools so agents can retrieve information and take action, and publishes a regional AI position including work with HUMAIN and Groq. If your constraint is Saudi data residency or an enterprise procurement standard, start there rather than with us.

The infrastructure

Twilio describes tools as endpoints the assistant can call to carry out tasks, in the style of LLM function calling, and its own documentation states that AI Assistants in developer preview is retiring in July 2026 with migration to Agent Connect, now generally available across voice, SMS, chat, WhatsApp and RCS. That is a normal platform transition, and a reminder that building on a preview product carries a migration you will pay for later.

360dialog sells access rather than an application. It documents enabling Meta Business Agent from its Hub with no integration work, connecting custom agents over the Model Context Protocol, and multi webhook so an automation tool, a team inbox and a CRM can share one number at once. Pair it with Zapier, Make or n8n and you have actions, built and owned by you.

The MENA filter most of these lists skip

Three regional tests separate a tool that demos well from one that works here, and none of them appear on a vendor comparison grid.

Can the action hold the right address field? Saudi Arabia uses a national short address from Saudi Post, four letters and four digits, for last mile delivery. Dubai uses Makani, a ten digit code from Dubai Municipality that identifies a building entrance. Lebanon has no unified national addressing at all. An order creation action built around a street line and a postal code produces failed deliveries in all three, and the fix belongs at capture, in the conversation, not in a support ticket afterwards.

Does it read the message your customer actually sends? Arabizi, dialect and code switching inside one sentence are normal in the Gulf and the Levant, not edge cases. Our guide to Arabic customer service sets out how to test it with your own inbox.

Is the channel worth the build? DataReportal's Digital 2026 Saudi Arabia report puts WhatsApp use at 92.2 percent of internet users, ahead of every other platform it lists. In this region WhatsApp is not a support channel bolted to the side. It is where the order happens, which is exactly why the actions behind it matter.

plumcut, and why we would still pick it

Here is the part where we are not neutral, and we would rather say so plainly than bury it.

Everything above is a capability you can buy. What almost none of it includes is somebody doing the work. The actions have to be specified against your store, your courier account, your CRM and your policies, tested against the messages your customers actually send, and repaired when a platform changes an endpoint. Across the tools here, the words "who builds it" almost always resolve to you.

plumcut is built the other way round. plum answers on your own WhatsApp number, sells rather than only replying, and we connect it to what the business already runs on, including Shopify, WooCommerce, Stripe, PayPal, Google Calendar, Calendly, HubSpot, Salesforce, Gmail and Slack, so an order agreed in a chat becomes an order in the store, a payment collected, a booking on the calendar and a record in your CRM. We build it, we run it, and we keep it working, which is set out in how it works and priced per scope on pricing. It reads Arabic, Arabizi and English in the same inbox, which is the normal state of a Gulf or Levant inbox rather than an edge case, and every conversation feeds back an understanding of your customers that stays yours.

For a brand in Saudi Arabia, the UAE or Lebanon doing real volume on WhatsApp, where the request only ends when something changes in a system, and where nobody in the team is going to own an integration backlog, plumcut is the option we would choose. That is editorial judgment from the vendor, offered as such.

When not to pick us. If you have an in house owner who likes this work, buy respond.io or SleekFlow and keep the money. If you are a single Shopify store with standard flows, Interakt or Zoko will be live sooner. If you have engineers and a reason to control the behaviour, take 360dialog or Twilio and build it. If your blocker is Saudi data residency or enterprise procurement, look at Unifonic or Infobip first. We are the right answer for the brand that needs the whole thing to work and has nobody to make it work.

What to ask on every demo, including ours

1. Show the agent creating or changing a record in my system, not reading one.
2. How many actions can one agent hold, and what happens at the limit?
3. What happens when the write fails, and who finds out?
4. Who writes the action, and who fixes it when my API changes?
5. Show me the log of everything it changed yesterday.
6. Send it three real customer messages from my inbox, in Arabizi, with the typos left in.

The sixth question is the one that ends most demos in this region. Bring your own messages, not theirs.