The strategic shift is from “message that links out to a website or app” to “conversation that contains the transaction.” Rich cards and carousels handle discovery, suggested actions handle decisions, and the thread becomes the storefront, with the brand verified throughout.
As Universal Profile 4.0 features like streaming video in rich cards roll out, product experiences in-thread get richer still, pushing conversational commerce closer to the feel of a live, guided shopping session.
Before designing the thread, it is worth being clear about where RCS stops. In the US, RBM has no native in-thread payment step, so the purchase itself happens on a checkout page opened by a suggested action. That is a smaller gap than it sounds, because the friction that costs sales is in discovery and decision rather than in the final tap, but it does mean "buy inside the conversation" describes the experience rather than the payment mechanics. Design for a single handoff to a mobile checkout that already knows the cart, not for a form the customer fills in again.
Three pieces of plumbing decide whether this works. A product feed the messaging layer can read, so cards carry current price and stock rather than yesterday's. Session state keyed to the phone number, so a tap on "Add" three messages ago still means something when the person replies twenty minutes later. And an identity link between that number and the customer record, or the thread cannot show order history and the conversation stays anonymous. Teams usually have the first, rarely have the second, and underestimate the third.
Stock and price are the failure mode that damages trust fastest. A carousel is fetched and rendered when the person opens it, which can be hours after the send, so a card advertising an item that sold out in between is a promise you cannot keep. Either read stock at render time or scope the send to inventory you are confident holds for the life of the message.
Scope the first build narrowly. The journeys that pay for themselves early are reorder of a known item, restock notification into a one-tap add, and abandoned cart recovery, because in each case the product is already chosen and the conversation only has to remove steps. Open-ended browsing in a thread is the hardest version of this and the least likely to beat your own website. Start where the intent already exists, and let the catalogue conversations come later.
- RCS can host the full journey, discover, decide, buy, track, support, in one branded thread.
- Carousels + suggested actions reduce funnel friction versus link-out flows.
- UP 4.0’s streaming video in rich cards (rolling out) will enrich in-thread product experiences.
- US RBM has no native in-thread payment; the purchase happens on a linked mobile checkout.
- You need a live product feed, session state keyed to the number, and a number-to-customer identity link.
- Start with reorder, restock and abandoned cart, where intent already exists, not open-ended browsing.