Respond around the clock on the channel customers already open
Most Egyptian and MENA buyers already message businesses on WhatsApp. Ordr sits on that same number through Meta’s Cloud API: it answers product and menu questions, explains modifiers and availability, and keeps a conversation history your team can audit. When the AI should not decide—refunds, custom quotes, VIP complaints—an operator takes over without forcing the customer onto email or a ticket form. Overnight and lunch-rush traffic no longer means missed chats; it means structured replies that land in the same inbox as daytime handoffs.
- AI replies grounded in your live catalogue
- Full conversation history per customer
- One-tap human handoff for exceptions
Take structured orders inside the chat
Order-taking is not a FAQ bot with a “visit our website” dead end. Ordr walks the customer through item selection, variants, quantities, delivery versus pickup, and the profile fields your kitchen or warehouse needs. Confirmed details write a structured order in the tenant workspace—the same order list your dashboard, payments, and fulfilment views already use. Cash on delivery stays first-class for markets where card checkout is optional; when Paymob card payment is enabled, the chat can move into a payment step without inventing a second cart system.
- Product guidance from the live menu or catalogue
- Modifiers, notes, and fulfilment context
- COD and Paymob-aware checkout paths
Run follow-up campaigns without breaking Meta rules
Broadcasts and retention sequences only help if they stay inside WhatsApp’s template and window rules. Ordr keeps approved template workflows, campaign history, and customer segments in the same workspace as inbound chats, so marketing does not fight support for the same phone number. Abandoned-cart recovery, post-purchase thank-yous, and win-back nudges reuse the customer record created during the original order conversation—rather than dumping numbers into a disconnected ESP that cannot see whether the guest already ordered again.
- Approved template workflows outside the 24h window
- Campaign history tied to customer profiles
- Segmentation from real order and chat activity
Built for Egyptian operations and Arabic conversations
Ordr treats Arabic and English as equal conversation languages. A guest who writes in Arabic gets Arabic replies; product and menu items can carry Arabic names so the thread does not flip mid-sentence. Local payment habits—COD, Paymob cards, wallet and bank transfer with receipt upload—are product paths, not afterthoughts. The operator dashboard works for teams that run service in Arabic, and Meta OAuth connects the Business number your brand already uses rather than asking you to start over on a parallel stack.
- Arabic and English in the same WhatsApp thread
- COD, Paymob, and transfer-with-receipt flows
- Official WhatsApp Business number via Meta
One agent across WhatsApp and every other channel
WhatsApp is usually the highest-volume channel, but Instagram DMs, Facebook Messenger, Telegram, and web chat still arrive with the same customers. Ordr runs one AI agent, one catalogue, and one customer profile across those channels so you do not re-train five bots. Ordering and booking steps follow a shared contract; only the button rendering differs by platform. When a guest starts on Instagram and finishes on WhatsApp, the business still sees one customer—not two orphaned threads.
- Shared catalogue and order records
- Cross-channel customer profiles
- Same handoff model on every channel
What you need to go live
Connect a WhatsApp Business account through Meta, import or sync your catalogue, and set the AI behaviour once for the tenant. Use the live demo to see order-shaped conversations before you bind a production number. From there, add Paymob or COD, enable bookings if you take appointments, and turn on campaigns only after templates are approved. Nothing here replaces Meta App Review or Advanced Access where Meta requires them—Ordr uses official Graph APIs and surfaces failures when a Meta-safe check blocks a send.
- Meta Cloud API connection
- Catalogue-aware AI configured once
- Payments, bookings, and campaigns as optional layers