Conversational Commerce: What It Is and What It Isn't

Conversational commerce is commerce conducted inside a two-way messaging thread: the customer asks, the shop answers, and the buying, the support and the follow-up happen in the same place. The channel is usually WhatsApp, Instagram DM, SMS or RCS. What makes it conversational is not the medium but the shape — a thread with a history, rather than a series of one-way sends.

Three properties separate it from everything else in a store's marketing stack:

• It is two-way. A customer can reply to any message and get an answer. If replies go nowhere, what you have is a broadcast channel wearing a chat interface.
• It is triggered by something real. The message follows an event in the shop — an abandoned checkout, a shipped order, a subscription renewal — rather than a slot in a campaign calendar.
• It is persistent and identified. The thread survives between sessions and is tied to a phone number, so context from March is still there in September.

This is also why conversational commerce sits alongside email rather than replacing it. Email remains the right place for long-form and low-urgency content; the thread carries the moments that need a reply. The WhatsApp flows and growth tools a Shopify store can run are the concrete form of that split.

A chat widget on a product page is the thing most often mistaken for conversational commerce. The difference matters because the two build completely different assets.

Four questions separate them:

• Who owns the identity? A widget session is anonymous unless the visitor is logged in. A messaging thread is tied to a phone number you have consent to write to.
• Where does the conversation live? A widget conversation lives on your site and ends with the tab. A thread lives on the customer's phone, in an app they open anyway.
• What survives? A widget usually starts from zero each visit. A thread keeps every earlier message, so the customer never re-explains their order.
• What can you do afterwards? After a widget session, nothing — there is no way back to that person. After a thread, a shipping update, a reorder reminder or a back-in-stock alert is possible, within the platform's rules.

None of this makes widgets useless. A widget that hands the conversation over to WhatsApp is a good acquisition tool, because it turns an anonymous visitor into a contact. It is the handover that makes it conversational commerce, not the widget itself. Our guide to WhatsApp customer support for Shopify stores covers what that handover looks like day to day.

In practice it is a loop with four steps: an event fires, a message goes out, the customer replies in the same thread, and the revenue is attributed back to the message that caused it.

The starting point is the event. Our help center documents five trigger types from four sources: two Shopify events (a contact purchase and an abandoned checkout), one Keaz-internal trigger (Smart activation, which picks the sending moment per contact), one external trigger (a webhook from another system) and one on WhatsApp itself (chat-in, where the customer writes first). The flows overview in the help center sets out what each one does.

The messages that follow are ordinary shop moments, written once. A customer who leaves a checkout gets one nudge about fifteen minutes later with a checkout link that stays valid for 48 hours. A shipped order gets a tracking link, which also opens a thread later flows can use. A subscription renewal gets skip, swap and pause options three days before the charge. The full set sits on the templates page.

The last step is what makes it commerce rather than messaging. Each flow carries its own discount code, created in Keaz and mirrored into the shop system, so an order that redeems it is attributed to the flow that sent it.

Conversational commerce fails quietly when one of four preconditions is missing. In order:

1. Phone numbers. Switching the Shopify checkout phone field from optional to encouraged moves capture from roughly 22% to 65% and above. Without numbers there is no thread to have.
2. Documented consent. Meta requires an opt-in before a business messages a WhatsApp user, the opt-in has to name the business, and it has to comply with applicable law (Meta, WhatsApp Business Platform documentation, 2026, retrieved 2026-09-29). Record when and how it was given.
3. Something worth saying. Event-triggered messages earn replies; calendar-driven sends earn opt-outs. If you cannot name the event behind a message, do not send it.
4. A route to a person. Automation handles the first exchange. Someone has to be able to take the thread over when a customer asks what the flow did not anticipate.

One timing rule is worth knowing before you plan anything. A customer's message opens a customer service window, and once that window closes you can only reach them with an approved template message, charged by category. Meta's current rates, messaging limits and window rules — each figure dated and sourced — are collected on our WhatsApp Business Platform facts page.

Measurement is where most conversational commerce projects go vague, because the channel invites flattering metrics. Open rates on a messaging channel are high almost by construction, and they tell you very little.

Three numbers are worth reporting:

• Reply rate — the share of recipients who answer. It is the only metric that tests whether the thread is actually a conversation.
• Flow finish rate — the share of contacts who reach the end of a sequence. It catches drop-off that a per-message open rate hides.
• Attributed revenue per flow — which requires a unique discount code per flow. Share one code across several flows and attribution collapses, as our note on revenue tracking with discount codes explains.

Set the codes up once, in the flow's starting point: revenue tracking with one discount code per flow walks through it. And resist comparing these numbers against email directly. The denominators differ — an opted-in messaging list is smaller and more engaged than an email list by construction — so a straight comparison flatters the newer channel. The complete guide to WhatsApp marketing for Shopify works through how the two split the lifecycle between them.

Six patterns account for most of the disappointing results:

1. Running it as a second newsletter. Broadcasting to a messaging list on a weekly schedule produces opt-outs faster than email does, because the channel is more personal and leaving takes one tap.
2. Buying a chatbot before collecting phone numbers. The bot is the last piece, not the first. Contact capture sets the ceiling on everything else.
3. Treating consent as a checkbox. An opt-in that does not name the business, or that is bundled into unrelated terms, is not usable consent — and platform rules sit on top of whatever local law requires.
4. One discount code across every flow. It is the single most common reason a store cannot say what the channel earned.
5. No human fallback. A thread where nobody answers the unexpected question is worse than no thread, because the customer has learned that replying is pointless.
6. Framing it as an email replacement. Stores that cut email to fund a messaging channel usually lose more than they gain; the two answer different questions.