What is conversational commerce?
Conversational commerce is buying inside a conversation. The customer asks, compares, orders, and changes the order without leaving the thread. On the phone, that thread is the call.
In this guide
Conversational commerce is buying, and the work around buying, inside a conversation. A customer asks whether the larger size is in stock. The agent checks, suggests the thing that goes with it, takes the order and the payment, and sends the confirmation, all before anyone opens a browser. The short definition is discover, evaluate, buy, and manage, in one thread.
Chris Messina named the term in 2015. He was describing shopping inside a message, and by voice, so a person could decide while they were doing something else. The name stuck. What was missing for a long time was an agent that could finish the purchase, especially on a phone call, where a lot of real orders already happen.
A conversation that can take the order
A helpful chat is not commerce. Commerce is the moment money, or a committed order, changes hands inside the same conversation that answered the question. These are the four jobs.
| Job | What the customer is doing | What has to be true |
|---|---|---|
| Discover | “What do you have for a birthday, about $80?” | Answers come from your catalog, not a guess |
| Evaluate | “Will it arrive by Friday, and can she eat it?” | Delivery dates, ingredients and policies are looked up |
| Buy | “Yes, send that.” | The order is placed and the payment is taken before they hang up |
| Manage | “The box arrived crushed.” | The order can be changed, replaced, or refunded from the same thread |
Stop before “buy” and you have a shopping assistant. The customer still has to find the cart, re-enter the address and hope the promo code works. Most of them don’t. The sale lived in the conversation, and the checkout lived somewhere else.
A link is not a checkout
| What the customer gets | Where the sale happens | |
|---|---|---|
| FAQ bot | A link to a help article | Nowhere. The question was deflected |
| Shopping assistant | A few products to compare | On the website, if they keep going |
| “I’ll text you a link” | A URL to finish later | Often never. The moment passed |
| Conversational commerce | The answer, the recommendation, and the completed order | Inside the conversation |
“Where’s my order?” answered with a tracking link is service. Seeing the delay, offering Friday instead, and updating the order is commerce too. Managing the purchase is part of the sale, because a broken delivery that gets fixed is a customer who orders again.
The phone was already a store
The 2015 version of this idea lived in messaging apps. For a lot of brands the store was the phone line long before that. Gift orders, reorders, “talk me through the options,” the customers who would rather say it than tap it. Those calls are conversational commerce. They were just waiting on a person to pick up.
A website chatbot never reaches them. Text and chat do, when the customer starts there, and email does when they want the details in writing. The thread has to be the same one. Someone who calls Tuesday, gets the comparison by email, and asks about Saturday delivery in chat on Wednesday is in the middle of one purchase. An agent with one profile treats it that way. The retail guide goes further on phone orders and peak season.
What the agent has to be plugged into
The agent can only sell what it can see and change. A sentence in a prompt, “place the order,” is not an order. The guide to how a conversation triggers an action is the mechanism. For commerce, these are the connections that matter.
- The catalog, with products, prices, promo codes, and the claims you’re willing to make. The agent never invents a price or a promise.
- Inventory and delivery dates, so “by Friday” is a lookup.
- The order system, with permission to place an order and to change one.
- The customer record, past orders and earlier conversations included, so the recommendation fits this person.
- Payments. The card is collected in the conversation, masked in the transcript and recording, and passed to your payment system.
- A person, for the order your rules won’t let the agent finish, with the conversation already on their screen.
One recommendation tied to what they just said beats a list of best-sellers. “He can’t have sugar, so skip the dessert” is a reason. A carousel is not. And the agent takes no for an answer. An add-on pushed after a no is how a completed order becomes a complaint.
How Simple does it
Simple is one agent on calls, texts, web chat, and email, with one profile of the customer. Answer picks up, including the call that would have waited on hold. Close is the commerce. It builds the order from your catalog, applies the promo code, makes the one add-on that fits, and takes the payment while the customer is still there. The card is masked everywhere the conversation is stored, and it goes to your payment system. The order is written back before the next call rings.
Prices and promotions come from the catalog. If it isn’t in there, the agent doesn’t quote it. A photo of a crushed box can come in by text. The agent can read it and start the replacement from the same thread, inside the rules you set.
Book is the part after the conversation, and the part before the next one. A cart that stalled, a reorder that’s due, and a confirmation the day before it ships. That follow-up stops when the order is placed. Develop scores the conversation against your checklist, including whether the add-on was offered and whether the total was confirmed before the card was charged.
Omaha Steaks runs this on its sales line. With Simple it handles 78% of sales calls, and its upsell rate is 30%, against 22% for seasonal agents. The Omaha Steaks story has the rest.
How to tell it’s commerce
- A test order, placed on a call, exists once in the order system, at the catalog price, with the promo code that actually applies.
- Ask for a product you don’t sell, or a discount you don’t offer. The agent says so.
- Decline the add-on. The order still completes, and the add-on is not in it.
- A bad card is declined while the customer is still on the line, and the agent doesn’t say the order went through.
- The same customer continues by text an hour later and doesn’t have to repeat the order.
- The transcript shows a masked card, not the number.
If the conversation ends in a link, you have a chatbot with better manners. Conversational commerce ends in the order.