The inbox is becoming a storefront

For most of the last decade the messaging channel was a notification pipe. Something happened in the store or the app, and a message went out to say so.

Increasingly the conversation is where the thing happens. A customer asks whether an item is back in stock, gets a card with the answer, and buys it without ever opening the site.

That shift is often described as conversational commerce: using messaging and conversational interfaces to help customers discover products, ask questions, make decisions, and move toward a purchase. The important distinction is that messaging is no longer only a channel for notifying customers after something happens. It can become part of the shopping journey itself.

The experience does not necessarily mean that every purchase happens entirely inside the messaging app. Depending on the platform and implementation, a conversation may handle discovery and decision-making before handing the customer to a web checkout or another secure payment experience. The opportunity is reducing unnecessary friction, not pretending the website has disappeared.

What actually moves into the thread

Not the whole catalogue. The parts that work in a conversation are the ones that were already conversational: a question with a short answer, a choice between two or three options, a confirmation, a status.

• Discovery: A handful of relevant products, not a grid of ninety.
• Assistance: The one question standing between interest and a decision.
• Checkout: A short, obvious path, with the payment step where the customer expects it.
• After the sale: Delivery, returns and support, in the same thread as the purchase.

This is the core principle of conversational commerce: move the parts of the buying journey that benefit from conversation into the conversation. Do not try to reproduce an entire ecommerce site inside a message.

RCS for Business provides some of the building blocks for this approach. Rich cards can combine media, titles, descriptions, and suggested replies or actions, while carousels can present multiple options for users to explore. Google specifically describes carousels as useful when users need to explore a variety of choices or related content.

That makes an RCS conversation well suited to a question such as "Which of these three products is right for me?" It is much less suited to displaying an entire catalogue with hundreds of products and every possible filter.

Why the thread is different from a page

A web page is somewhere a customer chose to go. A message is something that arrived. That difference sets the tone for everything: the thread has less room, less patience, and a much lower tolerance for being sold to.

It also has one thing a storefront does not — continuity. The order, the delivery update, the return and the next purchase all sit in one place, which is why a conversation started well is worth more than a session.

A page can afford to be browsed. A thread has to be worth the interruption every single time.

That continuity can be particularly useful when the customer's question changes during the journey. A shopper might begin by asking about availability, then ask about size, then request delivery information, and finally decide to buy. A conversation can connect those questions instead of treating each interaction as a separate website visit.

Google's RCS for Business documentation describes conversational agents as supporting back-and-forth dialogue, personalized interactions, product recommendations and actions within the conversation. That is a meaningful change from the traditional model of sending a notification and waiting for the customer to leave the message to continue.

From product discovery to decision

Traditional ecommerce often assumes that customers know how to navigate the store.

Search. Filter. Open a product. Read the description. Compare. Go back. Open another product. Add to cart.

Conversational commerce changes the starting point. Instead of asking the customer to navigate the catalogue, the business can help them narrow the choice through a question or recommendation.

A customer might ask:

I need a waterproof jacket for a weekend trip. What do you recommend?

The useful response is not a catalogue of 500 jackets. It is a small set of relevant options, followed by the next useful question or action.

That is where rich cards and carousels become useful. They can present a limited number of products with images, descriptions, and actions, allowing the customer to explore without turning the conversation into a full website replica.

The message should reduce decisions, not create more

The temptation with richer messaging is to add everything.

More products. More buttons. More offers. More links.

But interactive messaging works best when the available actions correspond to what the customer needs at that moment.

Google's RCS guidance explicitly recommends limiting suggested replies and actions to those that are useful for the current context rather than overwhelming the user with options.

That principle matters for commerce because every additional choice creates another decision. A message offering "View product," "Check availability," and "Ask a question" may be useful. A message containing ten competing calls to action is much harder to interpret.

The best conversational commerce experiences therefore behave less like a catalogue and more like a helpful salesperson: narrow the choices, answer the question, and make the next step obvious.

Checkout does not have to disappear

The phrase "buy in the inbox" can be misleading.

In some commerce implementations, customers can complete significant parts of the purchase journey inside the messaging experience. In others, the conversation hands the customer to a website, payment page, or another secure checkout environment.

What matters is not whether every transaction technically occurs inside the message. What matters is how many unnecessary steps exist between the customer's intent and the action they want to take.

RCS suggested actions can open URLs and connect users to other device actions, while conversational flows can maintain context before and after those transitions. Google documents URL actions specifically as a mechanism for moving users to a destination while keeping the messaging interaction part of the broader experience.

So the better goal is not "never leave the inbox." It is "leave the inbox only when leaving it adds something necessary."

After the sale, the conversation continues

Commerce does not end at checkout.

A customer still wants to know:

• Has my order shipped?
• When will it arrive?
• Can I change the delivery?
• How do I return it?
• Where is my receipt?
• Can I reorder it?

These post-purchase interactions may be even better suited to messaging than the original purchase. They are usually short, specific, and tied to an existing customer action.

That creates a continuous journey: product discovery, question, decision, purchase, delivery, support and potentially the next purchase can all be connected through messaging.

The result is not necessarily a replacement for the ecommerce website. The website remains valuable for broader discovery, content, account management and complex shopping journeys. Messaging becomes another interface for the moments where a direct conversation is faster or more useful.

Where teams get it wrong

The common failure is treating the channel as a smaller website: the full catalogue, the seasonal banner, the newsletter. It fills the thread with things nobody asked for and burns the attention needed for the message that mattered.

The teams doing this well are conservative about what they put in the conversation and generous about what they let the customer do once they are in it.

Another mistake is confusing rich formatting with conversational commerce. Adding a product image and a "Buy now" button does not automatically create a conversational experience. The real value comes when the customer can ask something, receive a relevant answer, and continue toward a decision without unnecessary friction.

That is why conversational commerce is broader than RCS alone. The category includes messaging apps, chat, AI-assisted conversations, and other conversational interfaces. RCS is one implementation that gives businesses structured messaging features such as rich cards, carousels, suggested replies and suggested actions.

The inbox should not become another website

The opportunity is not to move every part of ecommerce into the inbox.

It is to identify the parts of ecommerce that become easier when there is a conversation.

A product question. A recommendation. A stock check. A delivery update. A return request.

Those are small moments, but they are often the moments where customers hesitate.

The strongest inbox commerce experiences use messaging to remove that hesitation. They answer the question that blocks the purchase, surface a small number of relevant choices, and make the next action obvious.

That is a more sustainable model than turning every message into a storefront. The inbox has limited attention, limited space, and a customer who can leave with one tap.

The future of commerce in messaging is not about putting the entire store in the inbox. It is about putting the right part of the store there at the right moment.

That distinction is what separates conversational commerce from another marketing channel. The goal is not more messages or more buttons. It is a shorter path between a customer's question, their decision, and the action that follows.