Back to Blog

RCS Is Ready. Your Marketing Team Is Not.

· Jenny @ RCS X

RCS is production-ready. Your marketing team is still running SMS in a rich media body.

Here's the data: RCS campaigns consistently deliver 3x the engagement of SMS, 27% higher engagement lift, and 30% revenue boost on identical offers (Vibes, April 2026). Coppel saw 3x better results. Bandwidth reports 26% of brands now on RCS, with 2x more preparing.

The technology works. The results aren't keeping up.

The reason isn't the channel. It's the operational mindset still treating RCS like broadcast media.

The Mode Mismatch: One-Way vs. Two-Way

SMS is a memo. One message, one direction, fire and forget.

RCS is a session. Multi-message, bidirectional, stateful across every turn. The protocol maintains conversation context — what was said, what was clicked, what the customer chose — across an entire dialogue that can span days and seven or more back-and-forth exchanges.

This isn't a cosmetic upgrade. It's a fundamental architectural difference.

SMS: Customer abandons cart → you send "Complete your purchase" → message lands → maybe they click, maybe they don't, you never know.

RCS: Customer abandons cart → you send a Rich Card showing the product, price, and estimated delivery → they tap "Size out of stock near me" → your system checks inventory, finds a store 3 miles away with their size → sends a suggested action "Pick up today?" → they reply "yes" → appointment booked, session complete.

That's not a message. That's an orchestration.

Five capabilities SMS literally cannot replicate:

  1. Session continuity — the conversation persists across messages, days, and turns
  2. Stateful suggested actions — CTAs that remember prior choices within the session
  3. Mid-conversation rich media — product carousels, videos, and cards that appear contextually, not as attachments
  4. Read receipt + dwell time — you know not just IF they read, but WHEN and for HOW LONG
  5. Two-way personalization — the customer's reply changes the next message's content in real time

Why Teams Default to Broadcast Mode

Marketing teams are structurally organized around campaigns. Blast the list, measure open rates, move on. The entire discipline — content calendars, sends per week, subject line optimization — is built for one-way distribution.

RCS requires a different operating model. You don't "send campaigns." You design conversation flows. You instrument session depth. You optimize for messages-per-conversation, not opens-per-send.

The measurement model compounds the problem. Most teams still optimize for open rate — an SMS-era metric. The metric that actually predicts RCS revenue impact is session depth: how many messages does a typical RCS conversation contain?

Teams running RCS well target 5+ message sessions as their core success metric. Why? Because industry data shows RCS sessions with 5+ messages have 3.4x higher conversion rates than sessions with 1-2 messages. The session depth isn't a vanity signal — it's a purchase intent proxy.

The teams winning on RCS aren't sending better messages. They're designing better conversations.

The Technical Shift: From Message Sender to Session Orchestrator

This is where the gap between RCS-ready and RCS-ready-marketing-team becomes stark.

Stateful session management is the foundation. Every RCS session maintains a server-side record: session ID, full message history, customer choices, suggested action responses, timestamp, and fallback triggers. You track this in a session store — Redis, DynamoDB, or your RCS platform's built-in session management — and it persists across every subsequent message in that conversation thread.

Event-driven architecture replaces campaign scheduling. In an RCS session, each suggested action click fires a webhook to your backend. Your system processes the intent, queries the appropriate data source (inventory, CRM, appointment calendar), and serves the next message in the session tree. This is an event-handler loop, not a cron job.

Fallback logic is non-negotiable in two-way conversations. What happens when a customer replies "I need help" instead of tapping your suggested action? Your system needs NLU classification of customer intent — route to the support branch. What happens when they reply with something your system doesn't understand? You need an escalation path. SMS has no equivalent; RCS demands it.

MCP (Model Context Protocol) integration is the layer that transforms RCS from scripted conversation to AI-powered dialogue. Modern RCS agents connect LLMs to live sessions via MCP tools: the model receives the customer's message, calls the appropriate tool (CRM lookup, inventory check, appointment booking, order status), generates a contextual reply, and sends it back over RCS — all within the same session. This is what "AI agent + RCS" actually means in production: a stateful event loop where an LLM handles intent classification and response generation, and MCP tools provide the real-world data that makes responses accurate.

The orchestration layer is the mindset shift. You're not a marketer sending messages. You're an engineer designing a state machine that happens to converse with customers over RCS.

The Framework: Four Steps to Close the Readiness Gap

Step 1: Redesign for sessions, not messages

Before writing a single line of content, map the conversation tree. Every customer reply — yes, no, question, objection, branch — should have a relevant next message. Design for 3+ message sessions as the success condition. Open rate is table stakes. Session continuation is the goal.

Step 2: Instrument session depth

Track: messages per session, suggested action clicks per session, session duration, and continuation rate. Target: 40%+ of sessions reaching 5+ messages. Connect this data to your CRM — the session belongs to a customer record, and that record should update when an RCS conversation starts and ends.

Step 3: Connect to your AI agent stack

Treat RCS as an AI agent interface — like a website chat widget, but running on the customer's default messaging app with full carrier verification and rich media support. Build your MCP toolchain for the top 5 customer intents (order status, product availability, appointment booking, returns, account updates). Test the session flow end-to-end before going live.

Step 4: Test session quality, not campaign volume

A 500-session campaign where 40% reach 5+ messages outperforms a 5,000-send campaign where 90% are single-message drops. Run an incrementality test: hold out a segment, measure session depth delta in conversion rate. That's your RCS ROI.

The Bottom Line

RCS technology is ready. AWS, Twilio, Infobip, Bandwidth — the entire ecosystem is built and carrier-certified. The infrastructure for enterprise-grade RCS at scale exists today.

The bottleneck is the marketing team still running one-way broadcast logic on a two-way channel.

The teams that make the operational shift — from message sender to session orchestrator, from campaign manager to conversation designer — will capture the 3x engagement and 30% revenue lift that RCS is built to deliver.

The ones who don't?

They'll keep running RCS campaigns that look like fancy SMS — and wondering why the numbers feel underwhelming.

Sources: