Octwin by Cequens · Playbook
Sell inside the conversation.
Catalog, cart, order and payment in the same thread the customer started — on WhatsApp and on your website. No "visit our site to complete your order".
The leak
Every handoff is a place to lose the sale.
A customer who is already talking to you, already told you what they want, and is already holding their phone — and the next step is a link to a login screen.
ThenThe link opens a browserDifferent app, different session, no memory of the conversation.
ThenThey re-enter what they told youSize, quantity, address — all of it, again.
ThenYou lose the threadIf they drop out, the conversation has no idea and cannot follow up.
The shape
Four steps, one thread, no exit.
Each step is a record, not a session variable — so a customer can walk away mid-cart, come back tomorrow, and pick up where they stopped.
What it looks like
The whole purchase, in one thread.
What WhatsApp gives you
Native commerce surfaces, not screenshots of products.
WhatsApp has real product messages and a real cart. The platform uses them where they exist and renders the equivalent where they do not.
| Surface | Web widget | |
|---|---|---|
| Native product catalog | Yes | Rendered by the widget |
| Native cart | Yes | Rendered by the widget |
| Products in one message | 30, across 10 sections | 30 |
| Images per item | 10 | 10 |
| Takes payment | Yes | Yes |
The cart is data
An abandoned cart is a record, not a lost session.
Carts move through a lifecycle your team can see and query — open, submitted, abandoned. Not "we think people drop out at checkout", but which carts, holding what, and for how long.
Your catalog
Your products, your fields — not our schema.
A product is a record in your own declared data model. You describe the fields your business actually has, and the commerce surfaces read them.
Payments
Card checkout works today. Native in-chat pay depends on where you are.
LiveCard checkoutStripe is the shipped gateway. The customer pays and returns to the thread.
RegionalWhatsApp native payMeta's in-chat payment is only available in some markets and needs separate onboarding.
FallbackAlways a way to payWhere native pay is unavailable, the message carries a checkout link instead — the flow does not change.
Ask before you promise in-chat payment. Meta's native checkout is region-gated and requires WhatsApp Payments onboarding plus a payment configuration. Everywhere else the conversation degrades to a hosted checkout page — which is still one tap, but it is a page, and the customer will notice.
Reaching back out
One boundary worth stating up front.
Everything above happens in a conversation the customer started. Messaging them first — a cart reminder, a back-in-stock note — is a different thing.
Outbound on WhatsApp. Replying inside WhatsApp's 24-hour service window is fully supported. Business-initiated messages outside it require an approved WhatsApp template, and that path is still landing — so scheduled cart-recovery campaigns on WhatsApp are not something to commit to yet. The web widget has no such window.
Next
Buy something from a bot.
The demo is a real catalog, a real cart and a real checkout. Ten minutes on a phone tells you more than the rest of these slides.
SeeThe full purchaseBrowse, add, change your mind, and pay — on WhatsApp.
ReadThe commerce guideThe same ground, a level deeper, including how orders are modelled.
PlanYour catalogBring your product fields; we will map them in the session.
OCTWIN BY CEQUENS · Conversational commerce