RCS Delivery: How It Works, What Breaks It, and How to Monitor Performance
This post was originally published on December 4, 2025. It was updated on May 5, 2026, to expand coverage of RCS fallback design, add guidance on delivery performance monitoring tools, and reflect current platform capabilities.
RCS is a real upgrade from SMS. Branded sender profiles, rich media, interactive buttons, read receipts. But the upgrade comes with complexity that some marketers aren’t prepared for.
SMS delivery is simple. You send a message, it arrives. RCS delivery is conditional. Every message passes through a chain of requirements, and if any single link breaks, the message silently falls back to SMS. Your recipient still gets a message, but it is stripped of everything that made it valuable. And unless you are actively monitoring for it, you may never know it happened.
This guide covers how RCS delivery works, what causes it to fail, how to design messages that hold up when it does, and how to track delivery performance so you’re not flying blind.
How RCS Delivery Works
When a business sends an RCS message, the messaging platform does not simply push it to a phone number. It runs a series of checks first. The recipient needs all of the following to be true for the message to arrive as RCS:
- A compatible device (Android with Google Messages, or iOS 18+ in supported markets)
- A messaging app that supports RCS delivery
- RCS enabled at the device level
- A carrier that supports the RCS standard
- An active data connection (Wi-Fi or mobile data)
If all five conditions are met, the message lands as a rich, branded, interactive experience. If any one of them is not, the message falls back to SMS or MMS automatically.
This fallback happens at the platform level. According to Google’s RCS for Business documentation, when a device does not support RCS delivery, the platform returns a 404 error. The sending agent is then expected to deliver the message through another channel, typically SMS.
The Capability Check
Before sending, platforms can run a capability check against a phone number. This returns a list of the specific RCS features that device supports, things like standalone rich cards, carousels, URL actions, and PDF support. If the device cannot receive RCS at all, the check returns a 404 NOT_FOUND error.
Google’s documentation identifies three specific scenarios that trigger that error:
- The device does not support RCS or has it disabled
- The user is on a network where RCS traffic is not enabled
- An unlaunched agent is trying to reach a non-tester
For marketers, the takeaway is that sending an RCS message does not guarantee an RCS experience. Your message will be delivered, but whether it arrives as a rich, branded interaction or a plain text SMS depends on conditions you need to be checking before every send.
Message Expiration and Fallback Timing
Another fallback trigger beyond device capability is time. Google’s RCS for Business API supports a time-to-live (TTL) setting on every message. If the message cannot be delivered before the TTL expires, the platform sends a revocation notification. That notification is your cue to trigger SMS fallback.
This matters for time-sensitive content like one-time passwords, appointment reminders, or limited-time offers. If the recipient’s phone is off or out of data range when the message is sent, it will not be delivered as RCS. The TTL ensures you are not waiting indefinitely for delivery confirmation before falling back.
What Happens When Customers Disable RCS Delivery
When a user turns off RCS on their device, or when any of the delivery conditions above are not met, the experience changes in several ways at once. As MessageFlow documents, rich content does not downgrade gracefully during fallback.
Messages Default to SMS or MMS
The most obvious change: messages route through SMS or MMS instead of the RCS delivery channel. They still arrive, but without any of the enhanced features.
Rich Features Disappear
Everything that makes RCS feel like a modern messaging experience is gone. Carousels, branded sender information, suggested replies, interactive buttons, high-resolution media, typing indicators, read receipts. The recipient sees a plain text message from a phone number or short code instead of a branded business profile.
Engagement Data Degrades
This is the change some marketers miss. RCS provides detailed engagement metadata: delivery confirmations, read receipts, and interaction tracking. SMS provides almost none of that. When a segment of your audience silently falls back to SMS, your reporting gets noisy. Open rates look lower than they are. Interaction rates drop. And you cannot tell whether the problem is your content or your delivery channel without digging into the data.
Personalization Logic May Break
If your RCS message relies on interactive elements to carry meaning, like buttons that route users to different flows or carousels that present options, the SMS fallback version may not communicate the same thing. A message designed around tapping a button becomes confusing when the button is not there.
Visual and Structural Changes
Formatted cards and rich layouts become plain text. Calls to action that were presented as tappable buttons either become plain URLs or disappear entirely. The structure of your message changes, and with it, the clarity.
Designing for Reliable Fallback
The best RCS strategies treat fallback as a design constraint, not an afterthought. Every message should work in both environments from the start.
Treat Rich Features as Enhancements, Not Requirements
Carousels, buttons, and rich cards should add clarity and convenience. They should not be the only way your message makes sense. If you strip every rich element from your RCS message and the remaining text still communicates the core point and provides a clear next step, your fallback design is solid.
Always Include a Standard URL
Buttons disappear in SMS fallback. A plain URL does not. Every RCS message that includes an interactive button should also include the destination URL in the body text. This ensures the call to action survives regardless of delivery channel.
Map Features to Fallback Behavior
Understanding exactly what happens to each RCS feature during fallback helps you plan for it. Here is how the most common features translate:
| RCS Feature | Fallback Behavior | Design Best Practice |
| Action Buttons | Removed. Message reverts to plain text. | Include the URL in the body text as backup. |
| Carousels | Converted to a single image or a plain text list. | Put the most critical information in the first card or the main text block. |
| Branded Sender | Reverts to a standard phone number or short code. | Identify your brand in the first few words of the message copy. |
| Read Receipts | No longer available. | Use link-click tracking to measure engagement on fallback traffic. |
Build Modular Message Components
B2B communication follows predictable sequences: onboarding, product updates, renewal reminders, event follow-ups. Building reusable message components that work across both RCS and SMS reduces production time and keeps brand consistency intact across delivery channels.
Segment by Device Readiness
If your platform supports it, segment your audience by RCS eligibility. Prioritize rich experiences for confirmed RCS-capable devices. Default to SMS-first paths for mixed or unknown audiences. This improves experience quality and testing accuracy, because you can measure RCS and SMS performance separately instead of blending them together in aggregate reporting.
Monitoring RCS Delivery Performance
Sending RCS messages without monitoring delivery performance is like running paid media without conversion tracking. You know money is going out, but you do not know what is working.
What You Should Be Measuring
At a minimum, track these metrics for every RCS campaign:
- Delivery rate by channel. What percentage of your messages landed as RCS vs. fell back to SMS? This is the single most important metric for understanding your actual reach.
- Read rate. RCS provides read receipts. SMS does not. Your read rate applies only to messages that were delivered as RCS, so track it separately from overall campaign metrics.
- Interaction rate. Button taps, carousel scrolls, suggested reply selections. These tell you whether your rich content is doing its job.
- Fallback rate. The percentage of messages that could not be delivered as RCS and were routed to SMS instead. Track this over time. A sudden spike could indicate a carrier issue, a change in your audience’s device mix, or a technical problem on your end.
- Engagement delta. Compare engagement between recipients who received the RCS version and those who received the SMS fallback. This tells you the actual value your rich content is adding, and it helps you justify continued investment in RCS creative.
Native Platform Reporting
Google’s RCS for Business platform provides built-in analytics through the Business Communications Developer Console. It tracks three core metrics: messages sent, messages delivered, and messages read. These metrics are grouped by send date and updated daily, with an eight-day backfill window for delivery and read events.
The console also provides agent-level analytics including reputation scoring, spam trend tracking, and unsubscribe reason breakdowns. If your agent’s reputation drops, Google may throttle your sending volume, so monitoring this dashboard is not optional.
For teams that need more depth, Google’s documentation outlines how to build custom analytics by capturing RCS delivery receipts, read receipts, typing indicators, user response times, and interaction types directly from the API.
CPaaS Platforms With RCS Support
Not all businesses send RCS messages directly through Google’s API. Some use a CPaaS (Communications Platform as a Service) provider that handles carrier connections, capability checks, fallback routing, and analytics. Here is what the major platforms offer.
- Twilio made RCS generally available in August 2025 across 20+ countries and 55+ carriers. Their Messaging Insights dashboards provide cross-channel analytics for SMS, MMS, WhatsApp, and RCS in a single view. Twilio handles capability checks and automatic SMS fallback at the platform level, with no code changes required for existing messaging customers. They also recently launched a Consent Management API that enforces opt-in preferences across RCS, SMS, and MMS channels simultaneously.
- Sinch routes RCS through its Conversation API, which provides a unified analytics dashboard across SMS, WhatsApp, RCS, and other channels. The dashboard tracks message volumes, delivery and failure rates, and cost breakdowns by channel and country. It supports a sent-delivered-read funnel view, refreshes every 24 hours, and is included at no additional cost. Sinch also supports automatic SMS fallback when RCS delivery is not available.
- Infobip has supported RCS since 2018 and has delivered over 10 billion RCS messages. Their RCS reporting is available through multiple interfaces: Broadcast, Answers, Conversations, Moments, and API. Reports include delivery status, message-seen confirmations, and end-user interaction tracking. Delivery reports can be pulled via API or pushed to a webhook in real time.
The Gap Between RCS Platforms and Marketing Operations
Here is where some teams run into trouble. CPaaS platforms give you delivery data. They tell you whether a message was sent, delivered, and read, but not what happened next.
Did the recipient click through to your landing page? Did they convert? How does RCS engagement compare to email engagement for the same audience segment? How does fallback traffic perform compared to RCS-delivered traffic across the full funnel?
That analysis requires connecting your messaging delivery data to your broader marketing and sales operations stack. It means integrating RCS delivery reports with your CRM, your marketing automation platform, and your analytics layer so you can see the complete picture, not just the messaging slice.
This is the kind of work Sureshot does. We sit between your messaging platforms and your marketing operations systems, ensuring that delivery data, engagement signals, and campaign performance metrics flow into the tools where your team actually makes decisions. Whether you are connecting RCS delivery data to MAP and/or CRM, building cross-channel attribution models, or setting up fallback rate alerting so your ops team catches problems before they affect campaign results, Sureshot’s connective tissue makes RCS technically functional and operationally useful.
Monitoring RCS Delivery Red Flags
Even with the right tools in place, you need to know what signals to watch for.
- Sudden fallback rate spikes. If your fallback rate jumps without a corresponding change in your audience, something is wrong. It could be a carrier-level issue, a platform configuration change, or a problem with your RCS agent registration.
- Engagement drop-offs by segment. If a specific audience segment’s engagement drops, check whether their delivery channel shifted. A drop in read rates might mean more of that segment is receiving SMS instead of RCS, not that your content stopped resonating.
- Delivery-to-read ratio changes. A healthy RCS campaign shows a consistent ratio between delivered messages and read messages. If that ratio shifts, investigate. It could indicate deliverability issues, audience fatigue, or a change in how recipients are interacting with their messaging app.
The Bottom Line
RCS is a more powerful channel than SMS. But that power comes with more complexity. Messages pass through a conditional delivery chain. Fallback happens silently. Engagement data varies by channel. And most marketing teams are not set up to monitor any of it.
The marketers who get value from RCS understand the delivery mechanics, design defensively for fallback, and actively monitor performance across channels. They treat RCS as a creative upgrade and an operational system. A thoughtful approach to RCS delivery helps ensure that every message arrives with clarity, regardless of what happens between send and receive.
Maintaining delivery across mixed environments requires a consistent fallback strategy. If you’re building your plan, we’re happy to share the framework we use.