Conversational Commerce
"Conversational Commerce is buying and selling inside a messaging thread, where an agent answers product questions, checks stock and takes orders."
What is a Conversational Commerce?
Conversational Commerce is buying and selling inside a messaging thread, where an agent answers product questions, checks stock and takes orders. Related product: Chat Agents.
Reviewed by Atul Diwedi, Co-Founder · Last reviewed
Deep Dive
Conversational commerce is the store running inside a chat thread. The customer asks about a product on WhatsApp, Instagram DMs, web chat or Telegram, and the agent answers from the catalog, checks stock, shares a checkout link, confirms the order and sends updates to the same thread. It sits between the catalog and the order system, and the thread becomes the customer's record of the purchase.
How it works. The agent is connected to the catalog and order system (Shopify is the common case) so product details, prices, variants and stock are read live rather than from a training snapshot. On a product question it returns the matching items, with images where the channel supports them. For a purchase it collects variant, quantity and delivery details, creates the order or a checkout link, and confirms. After the order it answers where-is-my-order questions from the fulfillment status and handles a return request against the policy. On WhatsApp, notifications sent more than 24 hours after the customer's last message use Meta-approved templates, because that is the customer service window Meta applies to business-initiated messages. Payment stays with the store's checkout; the agent does not store card data.
Why it matters for e-commerce teams. Product questions are where carts are lost: a shopper who cannot find out whether a size is in stock or whether delivery reaches their pin code closes the tab. Answering in the channel they are already in keeps the sale moving. Messaging also carries the post-purchase load: order status, returns, and the repeat purchase, which is the part of the relationship with the margin in it.
Example. A Shopify store selling running shoes gets a WhatsApp message asking whether it has a particular model in size 9.5 wide. The agent checks the catalog, finds the wide fit in 9.5 in two colors, and sends both with prices. The shopper picks one and asks about delivery to Jaipur. The agent confirms the delivery estimate from the shipping rules, sends a checkout link, and when payment completes, posts the order confirmation in the thread. Four days later a tracking question is answered from the fulfillment status. On day 60 a template message, sent with the customer's opt-in, offers the matching insole.
Conversational commerce vs WhatsApp automation. WhatsApp automation is the plumbing: inbound routing, auto-replies, templates and broadcasts on one channel. Conversational commerce is the use case built on top of it, and on other channels too: catalog, stock, orders, returns and reorders inside the conversation. A store can run WhatsApp automation without selling in chat, and can run conversational commerce on web chat without WhatsApp.
Common pitfalls. Letting the agent quote stock from a stale export; sending promotional messages without opt-in or outside Meta's template rules, which lowers the number's quality rating; handling returns without the policy document loaded; and leaving the human handoff path undefined for payment disputes.
Botcadence chat agents connect to Shopify for catalog, stock and order status and run on WhatsApp, Instagram, web chat and Telegram, with reply credits metered per generated message; see the e-commerce industry page.
Related Technology
See Conversational Commerce in a Botcadence agent
Start on the Free plan and configure an agent that uses Conversational Commerce on your own website chat or WhatsApp number. No card needed.
Get Started FreeWebsite chat live in about 5 minutes
Common Questions
Conversational Commerce FAQs
The agent sends a checkout or payment link from the store's own checkout and confirms when payment completes. Card details are not collected in the conversation, which keeps the store's existing payment compliance intact.
Live, when the catalog integration is connected. Stock, prices and variants are read at the moment of the question; a static product document is only a fallback for descriptions and policies.
Order and shipping updates sent more than 24 hours after the customer's last message must use a Meta-approved template and the customer's opt-in. Replies inside the 24-hour window can be free-form.
The agent checks the order date against the return policy document, explains eligibility, collects the reason and item, and either creates the return in the store or hands off to a person when the case is outside policy.