AI for Retail & E-commerce —
Capture Every Order, Recover Every Cart

Your store gets 70-110 WhatsApp messages between Asr and midnight, and 30-40% never get a same-day answer — every unanswered "كم سعره؟" is an order your competitor captures in four minutes. Carts die overnight: customers add to cart on Salla at 11pm, hesitate over shipping cost, and are gone by morning, because following up manually with every cart is a full-time job nobody has. Ramadan and White Friday triple your volume exactly when your replies are slowest — the seasonal peaks where the year's revenue is made are also where response times collapse. A flow-builder menu answering "اهلا! اختر من القائمة" to a Najdi customer asking if the oud is original, or failing "3ndk mqas M?" in Arabizi, loses the sale and the trust in one message. Unconfirmed cash-on-delivery orders ship, bounce, and come back as return-to-origin cost — every unconfirmed COD order is a coin flip you pay for either way. "وين طلبي؟" buries the questions that actually need a human: sizing, exchanges, wholesale inquiries. Instagram DMs become screenshots, then WhatsApp threads, then a notes app — order capture is manual copy-paste across three apps, addresses get lost, and there is no record of what was promised. And you cannot see the leak: no response-time number, no cart-recovery rate, no revenue-per-conversation, so you feel the loss in slow months but cannot show it, or fix it, with data.

A Salla fashion store pilot in Riyadh: a WhatsApp AI agent handling Najdi and Arabizi, a Salla webhook driving abandoned-cart templates, catalog and payment links in-thread, and human handoff rules after 9pm — measured by median first-response time against baseline, same-day answer rate, cart-recovery rate and recovered SAR value, and orders captured end-to-end without a human touch. An electronics retailer pilot with heavy COD exposure in Jeddah/Cairo: a confirm-edit-cancel flow before dispatch, an order-status agent wired to store and courier APIs, and staff escalation for exceptions — measured by COD confirmation rate, return-to-origin rate against a 90-day baseline, share of WISMO conversations resolved without staff, and staff hours returned per week. A multi-branch retail group pilot in the UAE: one WhatsApp entry point with branch routing, a bilingual agent tested against dialect evals, and a monthly ops review — measured by containment rate, CSAT on closed conversations, response-time SLA attainment per branch, and conversation-to-order conversion. We never publish invented numbers; every pilot is instrumented from day one, and the report becomes the case study only after client sign-off.

Salla and Zid are our default retail integrations, connected through their official APIs and webhooks: abandoned-cart events trigger recovery messages, the agent reads live product and stock data, and captured orders land back in your store dashboard. Shopify and WooCommerce are equally supported. If you sell only through Instagram with no storefront, the agent captures orders in a structured flow and sends payment links, so nothing lives in screenshots anymore. Setup for a standard Salla or Zid store takes about two weeks.

Retail groups with 10-100+ branches face a different problem: fragmented WhatsApp numbers, no consistency between branches, and no analytics — a Head of Digital needs one number to behave the same way everywhere, and a COO wants numbers, not another pilot (MIT research found 95% of enterprise AI pilots produce no P&L return). We build unified WhatsApp routing with a bilingual agent tested against dialect evals, a monitoring dashboard per branch, and a monthly ops review under retainer, scoped as an AI Implementation engagement.

Saudi Arabia: marketing messages require consent under PDPL, so our opt-in flows are a selling point, not a footnote, and we offer KSA-regional hosting for conversation data; Salla and Zid dominate SMB storefronts here, and pricing on Saudi pages is in USD. UAE: UAE PDPL applies similarly, English-first search matters for retail groups, and Meta Business verification requires a registered trade license; pricing is anchored in USD across the GCC. Egypt: Law 151/2020 governs data, pricing is in USD, and Egypt is our dialect-Arabic proving ground where pilot templates run first with Cairo merchants. Across every market, the WhatsApp Business API requires Meta Business verification and template approval, and per-message pricing is passed through transparently — we automate conversations, orders, and back office; we do not provide payment processing, consumer credit, or tax advice, and payment links use your store's existing gateway.