Conversational Commerce
Chat with customers on WhatsApp and Telegram: browse the catalog, add to a cart, get a payment link and be handed to a person.
A single bot runtime handles WhatsApp and Telegram conversations. It keeps a session for each customer, runs a flow you design to search the catalog, add items to a cart and send a payment link, and can flag a conversation for a person. WhatsApp order updates go out through the provider you already use. Language-model intent detection and the Conversation OS plugin family are not available yet, as the sections below say.
What Conversational Commerce does
6 capabilities, each described as it works today.
WhatsApp and Telegram bot runtime
One orchestrator handles inbound messages from WhatsApp providers and Telegram, and replies on the same channel.
Inbound messages from WATI, Gupshup, AiSensy and MSG91 on WhatsApp, and from Telegram, are normalised into the same shape and handled by one orchestrator. Each customer has a session stored in the database that remembers where they are in the flow, and messages are de-duplicated so a repeated webhook does not trigger a second reply. Telegram supports inline keyboards and verifies a secret token on the webhook.
- WhatsApp through WATI, Gupshup, AiSensy or MSG91, and Telegram
- One runtime and one session store for both channels
- Repeated webhooks are de-duplicated
- Telegram inline keyboards and webhook secret verification
Flows for catalog, cart and payment link
Design a flow that searches the catalog, adds items to a cart and sends a payment link.
Conversations run as a graph of nodes. Nodes can search the catalog, add items to a cart and create a payment link through the first payment provider configured for your business. A node can also flag the conversation for a person to take over. Flows are matched on what the customer sends, not understood in free language. There is no promo-code entry, delivery-slot selection or invoice sending in the chat today.
- Node-graph flows
- Catalog search and add to cart
- Payment link from the first configured provider
- A handover flag for a person to take over
- No promo codes, delivery slots or invoices in chat yet
WhatsApp order updates
Send order confirmed, shipped, delivered, cancelled and refunded messages through your WhatsApp provider.
When an order changes state, a template message goes out to the customer through the WhatsApp provider connected to your business. The states covered are confirmed, shipped, delivered, cancelled and refunded.
- Confirmed, shipped, delivered, cancelled and refunded messages
- Sent through the provider you connect
Which business a chat belongs to
Incoming chats are matched to a business through its provider settings.
For WhatsApp, the sender number, project or instance on the provider's webhook is matched against the settings saved for each business. Telegram does not include the bot token in its updates, so it is matched to the single active Telegram integration. A deployment where several businesses share one Telegram setup is not fully separated yet, so run one Telegram bot per deployment for now.
- WhatsApp matched by the provider's sender number, project or instance
- Telegram matched to the active Telegram integration
- Several businesses on one shared Telegram setup are not fully separated yet
Language-model intent detection
RoadmapAn agent that classifies what a customer wants and pulls out items and quantities exists, but is not connected to the live bot yet.
A conversational-commerce agent has been built that reads a message and returns an intent (browse, add to cart, checkout, payment, complaint, return, negotiate, greeting or other), any items and quantities, suggested actions, and whether a person should take over. It is not yet part of the live WhatsApp and Telegram flow, so today's bots follow the flows you design rather than interpreting free text.
- Built: intent, items and quantities, suggested actions and escalation flag
- Not yet connected to the live bot flow
- Today's bots follow designed flows
Conversation OS plugin family
RoadmapFour plugins for WhatsApp AI agents, marketing automation, a sales CRM and an AI call receptionist are catalogued, and are not available to run yet.
The marketplace catalogue defines four Conversation OS plugins: WhatsApp AI Agents, Conversation Marketing Automation, Conversation Sales CRM and AI Call Receptionist. Each has a description, channels and default limits, and the admin shows the catalogue and can grant the entitlement. The behaviours the catalogue describes, such as an AI voice receptionist or spam call detection, have not been confirmed as running, so treat this as a roadmap item and ask us before you plan around it.
- WhatsApp AI Agents, Marketing Automation, Sales CRM, AI Call Receptionist
- Catalogued with channels and default limits; the admin can grant the entitlement
- Runtime behaviour is not confirmed, so treat as roadmap
QuantumOS Dispatch
Insights for commerce operators
Operator stories, platform deep dives and notes on what ships.
We'll send the QuantumOS Dispatch by email. Unsubscribe any time. See our privacy notice.