Conversational Commerce: How to Sell Through Chat, End to End

This guide is for e-commerce, retail and D2C leaders who want chat to produce orders, not just answer questions. It walks through each stage of selling in a conversation, the systems you need behind it, the decision points between automation and people, and the KPIs that prove whether it pays. For WhatsApp template examples such as order confirmation and cash-on-delivery checks, see our WhatsApp for ecommerce guide.

What is conversational commerce?

Conversational commerce is selling through a two-way messaging channel: the customer discovers, asks, chooses, pays and tracks the order in a chat rather than only on a website or app. The chat can be run by agents, automation or both.

It is not a replacement for your store. It is a second checkout path for customers who prefer to ask before buying, which is common for high-consideration items, custom orders, repeat purchases and markets where messaging apps are part of daily life.

What are the stages of a conversational sale?

Every conversational sale passes through six stages. Design each one deliberately.

Human assistance is not the last step in time; it can happen at any stage. It is listed last because it is the safety net under the whole flow.

How does each stage work in practice?

Discovery

Customers start chats from links and QR codes on your website, product pages, packaging, ads and social posts. Use a prefilled message per source (for example, "Hi, I'm interested in the Oud gift set") so agents and reports know where the chat came from. On WhatsApp, the customer messaging first opens a customer-service window in which you can reply freely.

Product presentation

Send products as structured content rather than screenshots. On WhatsApp, Meta's documentation describes single-product messages and multi-product messages that show up to 30 products from your catalogue, organised into sections. Keep the catalogue in sync with your store so price and stock are never wrong in chat.

Cart

Customers can build a basket from product messages, or an agent can assemble it from the conversation. Confirm size, colour, quantity, delivery address and delivery slot in a single summary message before payment to avoid errors.

Payment

Native in-chat payments on WhatsApp exist only in specific markets, according to Meta and provider documentation, so most businesses send a payment link generated by their own gateway. Good practice:

• Generate one link per order, tied to the order ID, with an expiry.
• Show the amount, currency and merchant name in the message.
• Confirm payment back in the chat as soon as the gateway webhook arrives.
• Never ask for card numbers or one-time passwords in the chat.

On Telegram, bots support digital goods payments with Telegram Stars, and physical goods through third-party payment providers, according to Telegram's bot documentation.

Order updates

After purchase, send confirmed, shipped, out-for-delivery and delivered updates as utility templates where opted in. Keep promotional wording out of them, or Meta may treat them as marketing. Our delivery status guide explains how to track whether updates arrive.

Human assistance

Route questions an automated flow cannot answer to an agent with the full conversation and order context. Set clear service hours, an away message and a target first response time.

What architecture do you need?

At minimum, five components connected by APIs and webhooks:

1. Messaging channels: WhatsApp Business API, Instagram DM, Telegram bot, email.
2. Shared inbox: one place for agents to see and answer all channels, with templates and attachments. See shared inbox for WhatsApp, Instagram and email.
3. Commerce backend: catalogue, stock, pricing and order management.
4. Payment gateway: creates payment links and sends paid or failed events.
5. CRM or customer data store: identity, consent, order history and segments. Our CRM webhooks guide covers the event design.

Data flows to agree before building:

• Inbound message to inbox, with customer lookup by phone or handle.
• Order created to payment link generated to link sent in chat.
• Payment confirmed to order status updated to utility template sent.
• Delivery events to utility templates, with failures routed back to an agent.

Which KPIs prove conversational commerce works?

Measure commerce outcomes and service quality together; one without the other misleads.

For service metrics, use the formulas in our support KPIs guide.

How do you launch? A step-by-step checklist

1. Choose one product category with frequent pre-purchase questions.
2. Add click-to-chat links with prefilled messages to those product pages and ads.
3. Connect the catalogue and check prices and stock daily.
4. Create saved replies for the ten most common questions.
5. Set up payment link generation tied to order IDs.
6. Get utility templates approved for order confirmation and shipping.
7. Collect marketing opt-in separately for follow-up offers.
8. Tag chat orders for attribution and launch for four weeks.
9. Review KPIs, then expand categories or add automation.

Worked example: a Kuwait perfume house

"Bayt Al Oud" (synthetic) sells premium fragrances online and in a mall boutique. Customers often ask about scent notes before buying gifts.

• Instagram posts and product pages carry a "Ask a perfume adviser" link that opens WhatsApp with a prefilled message naming the product.
• Advisers reply from the shared inbox with a multi-product message of three matching scents and a short video.
• The customer picks one; the adviser confirms gift wrapping and delivery slot, then sends a payment link from the store's gateway.
• Paid status triggers a utility template confirming the order in Arabic, followed by shipping and delivery updates.
• After four weeks, the team compares conversion and average order value from chat against the website and adjusts adviser hours to match peak chat times.

What are the limits and common mistakes?

• Chat without systems. If agents copy prices from a spreadsheet, errors and delays follow.
• Payment in the chat thread. Never collect card details or OTPs in messages; use the gateway.
• Over-automation too early. Bots that loop frustrate high-intent buyers. Always offer a person.
• Promotional order updates. Mixing offers into utility templates risks recategorisation and complaints.
• Ignoring messaging costs. WhatsApp template fees and agent time must be in your cost per order; see our pricing guide.
• No attribution. Without order tagging, chat revenue stays invisible and under-resourced.

How OmniChannels.ai helps

OmniChannels.ai, powered by BroadNet Technologies, gives sales and service teams an Omni Inbox for WhatsApp, Instagram, Messenger, Telegram and Email, with assignment, tagging, media and templates. WhatsApp onboarding runs through Meta Embedded Signup, and catalogs, interactive messages and WhatsApp Flows are supported alongside templates with approval tracking. Chatbots and AI agents answer in Arabic and English and hand over to agents. Campaigns run on every channel with scheduling and delivery reports, and commerce systems connect through the public REST API and webhooks. See marketing solutions or book a demo.