Recover abandoned carts over WhatsApp, the way MENA shoppers actually buy

Why your email recovery flow underperforms here

The standard abandoned-cart playbook was written for a market where the shopper has a saved card and checks email. In Egypt and the Gulf the shopper added items, hesitated at a checkout that asks for card details, and left to pay cash on delivery somewhere they trust more. Your three-email drip lands in an inbox they open once a week. The cart is gone.

Two things are actually true about this shopper: they live in WhatsApp, and the thing that stopped them was usually the payment step, not the product. Recovery has to meet both.

What the agent does

Connect your store and WhatsApp Cloud to the Wassel MCP endpoint and give the agent the recovery instruction:

When a checkout is abandoned, wait 45 minutes, then send the customer a WhatsApp message in Arabic with their cart items and a one-tap link back to checkout. If no order in 24 hours, send one follow-up offering cash on delivery explicitly. Stop the moment they place any order.

What the agent handles:

• The store signals the abandoned checkout with the cart contents and the customer's phone.
• The agent waits a real interval. Not instant — instant reads as automated and pushy. Around 45 minutes is late enough to be a nudge, early enough that intent is warm.
• WhatsApp Cloud sends the message in Arabic, with the items named and a link straight back to the filled cart.
• The follow-up, only if there's still no order, names cash on delivery as an option. For a shopper who bailed at the card field, "you can pay when it arrives" is the actual unlock, not a discount.
• The agent watches for any order from that customer and stops the sequence the moment one lands, so nobody who already bought gets chased.

The MENA specifics that decide whether this works

1. COD has to be said out loud. A generic "you left something behind" ignores why they left. The shopper who abandoned at the card form isn't undecided about the product — they're unsure they can pay the way they want. Naming COD recovers carts a discount never would, and it costs you nothing in margin.
2. Arabic, and human. A message that reads like an English template machine-translated converts worse than no message. Keep it short, in Arabic, the way a person texts.
3. Timing is a real lever. Too soon feels like surveillance. A day later the intent is cold. One nudge, one follow-up, then stop. A third and fourth message trains people to mute your number, which costs you the transactional order updates they would have read.
4. Respect the 24-hour window. WhatsApp requires a pre-approved template to open a conversation with someone who hasn't messaged you recently. The recovery message is that template. It's a one-time approval, usually cleared within a day.

Why it matters

Recovered carts here are not marginal. COD-heavy stores routinely abandon a large share of started checkouts at the payment step. Even a 10 to 20% recovery on those, at no discount, is direct revenue that was already in the cart. The cost is one WhatsApp template message per abandoned checkout. The math is not close.

Point your agent at the endpoint

Open the Wassel dashboard, copy the MCP endpoint into your Claude, ChatGPT, or Cursor config, and connect your store and WhatsApp Cloud. Submit the two recovery templates for approval, run the flow on test checkouts, then turn it on.

If you want the follow-up to carry a small incentive instead of only naming COD, that's a one-line change to the instruction. Most stores find COD alone does the work.