Answer
Yes. One agent, one catalogue, one set of orders and customers, across five customer channels. Ordering and booking follow a single shared contract, so a customer gets the same behaviour wherever they start.
WhatsApp, Instagram DMs, Facebook Messenger, Telegram, and an embeddable web chat widget are all answered by the same configured agent. You do not train a WhatsApp personality and then rebuild it for Instagram; connecting a channel is credentials and routing, not a second product.
Order confirmation, booking confirmation, edits, and cancellation use the same steps and the same stable choice ids on every channel. That is how a customer who starts an order on web chat and finishes a question on WhatsApp still meets one business logic—not five half-finished scripts.
Orders, bookings, customers, and conversation history land in one workspace regardless of which channel produced them. Reporting is not “WhatsApp revenue vs Instagram revenue” glued together in a spreadsheet; it is one tenant’s commerce and conversation data.
Meta, Telegram, and web chat expose different interactive message types. Ordr’s cross-channel contract allows renderers to differ while keeping option ids and step order stable. Claiming pixel-identical buttons on every network would be false; claiming one ordering behaviour is the accurate product statement.
Language is not a per-channel setting. The agent that answers WhatsApp in Arabic is the same agent that answers Instagram in English when that is what the guest wrote. Catalogue Arabic names, handoff, and order structure stay available wherever the thread starts.
Most tenants go live on WhatsApp first, then add Instagram or Messenger when comment-to-DM and DM volume justify it, then Telegram or web chat for audiences that live there. Because configuration is shared, each new channel is mainly an OAuth or bot-connect step plus a smoke test of the same order path—not a new chatbot project.
Yes. WhatsApp, Instagram, Facebook Messenger, Telegram, and the web chat widget are answered by the same agent, reading the same catalogue and writing to the same order and customer records.
No. The business setup, catalogue, and conversation behaviour are configured once. Connecting a channel is a credential step, not a second configuration of the agent.
Customer records are shared, so a customer the business already knows is recognised. Message history is per conversation, so a customer moving from Instagram to WhatsApp starts a new thread against the same customer profile.
The ordering, booking, confirmation, and cancellation steps follow one shared contract with stable choice ids across channels. How the buttons are drawn differs per platform, because each messaging platform offers different message types.
Connecting the account. WhatsApp uses the Meta Cloud API; Instagram and Messenger connect through Meta; Telegram uses a bot session; web chat is a script snippet with a public key and an allowed origin.
No. Each messaging platform offers different message types, so renderers can differ. The ordering and booking *steps* and stable choice ids stay shared; how a button is drawn is allowed to vary.