RCS Messaging Fallback Analytics: Measuring Engagement When Rich Messages Switch to SMS
You launch a beautiful RCS campaign: product carousel, branded sender, tap-to-buy buttons. The report arrives showing 96% delivered. You celebrate, and then the sales numbers look nothing like that.
The gap usually has a simple explanation. A portion of your audience never saw the rich message at all. Their phones or networks did not support RCS, so the message quietly switched to plain SMS. If your analytics blend both outcomes into one “delivered” figure, you are measuring the wrong thing.
This guide shows how to measure RCS performance properly when fallback is part of the picture.
What is RCS fallback?
Rich Communication Services (RCS) is the upgrade to traditional SMS, supporting verified sender branding, images, carousels, suggested replies and action buttons. But RCS only works when the recipient’s device, messaging app and network all support it, and when the user has it enabled.
When RCS is not available, a well-configured campaign can fall back to SMS. The recipient still receives your message, but as plain text, usually with a link instead of buttons and no rich media. Fallback protects your reach, but it changes what “engagement” means for that recipient.
In India, remember that the SMS leg of any fallback must follow the same DLT rules as any other commercial SMS: registered sender ID and approved content templates. A fallback message that is not compliant can fail even when the RCS plan looked perfect. For a refresher, see our guide to DLT registration in India.
Why blended reporting misleads you
Three things go wrong when RCS and SMS results are combined:
- Delivery looks identical, experience does not. A delivered carousel and a delivered text line are not the same product, yet both count as one delivery.
- Read data is uneven. RCS can report read status when the user’s read receipts are enabled. Standard SMS has no read receipt. Comparing “read rate” across channels is comparing unlike things.
- Cost per message hides cost per outcome. RCS and SMS are priced differently, so the cheapest route is not necessarily the cheapest conversion.
The fix is to separate your reporting into two layers: a channel layer (what happened to the message) and an outcome layer (what the customer did).
The metrics that matter
Channel-layer metrics
RCS-capable reach. Of all contacts targeted, what share could receive RCS? This tells you the real size of your rich audience and how it changes by city, device and operator.
Fallback rate. Messages that switched to SMS divided by total messages sent. A high fallback rate does not mean failure. It means your audience mix is not yet RCS-heavy, and your SMS content must carry the campaign.
Delivery rate by channel. Report RCS delivery and SMS delivery separately, and also the combined end-to-end delivery. Investigate any large gap.
Time to deliver. If a fallback adds delay, time-sensitive offers can arrive late. Check the median delivery time for each route.
Outcome-layer metrics
Click-through rate (CTR) by channel. On RCS, count taps on suggested actions and buttons. On SMS, count clicks on the tracked short link.
Response rate. Replies and suggested-reply taps on RCS, keyword replies on SMS.
Conversion rate. Purchases, sign-ups, bookings or calls attributed to each channel.
Cost per delivered message, cost per click and cost per conversion. These three numbers decide which channel deserves more budget.
Opt-out rate. Track unsubscribes and block requests separately for RCS and SMS, since tolerance for each channel differs.
How to track fallback correctly
Use one campaign ID across both channels
Every send should carry a common campaign and message ID, so that the RCS attempt and the SMS fallback are linked to the same contact. Without that, you cannot tell whether a click came from a user who saw the rich card or one who received the text.
Tag every link and button separately
Give RCS buttons and SMS links different tracking parameters (for example, a source tag such as rcs or sms-fallback). Your web analytics will then show which channel produced the visit, the order and the revenue.
Capture the final channel in your delivery report
Ask your messaging provider for reports that show, per message, the first attempted channel, the final channel and the status. This single field is the foundation of everything else.
Keep a clean control group
If possible, hold back a small SMS-only group with the same offer. This shows what RCS adds beyond the message content itself, so you can calculate the real uplift rather than assuming it.
A worked example
Suppose a retailer sends 100,000 messages with an RCS-first plan. The numbers below are illustrative, not benchmarks.
| Metric | RCS | SMS fallback |
|---|---|---|
| Messages | 62,000 | 38,000 |
| Delivered | 60,500 | 36,600 |
| Link or button clicks | 4,235 | 1,098 |
| Click-through (of delivered) | 7.0% | 3.0% |
| Orders | 254 | 55 |
The blended report would simply say “97.1% delivered and 5.3% CTR.” The split report tells a better story: RCS drove more than twice the click-through rate, but the fallback group still contributed roughly 18% of orders. That makes a clear case for two actions: improve the SMS copy and link, and grow the RCS-capable share where possible.
Common mistakes to avoid
- Treating fallback as an error. It is a safety net. The goal is to measure it, not eliminate it.
- Comparing read rates between RCS and SMS. Use clicks and conversions as the shared yardstick.
- Ignoring SMS copy. Many teams design the RCS card carefully and write the fallback text as an afterthought.
- Judging results too early. Capability and reach change over time, so review monthly trends rather than one send.
- Skipping compliance on the SMS leg. Template and sender mismatches cause silent failures.
How to improve results once you can see them
- Rewrite the fallback SMS so it works as a complete message with a single clear link.
- Segment campaigns by RCS-capable and non-capable audiences, and tailor creative to each.
- Send time-sensitive offers first to the group with the fastest delivery route.
- Reallocate budget towards the channel with the lowest cost per conversion, not the lowest cost per message.
- Review fallback rate every quarter. As RCS support widens among your audience, your rich-message share should grow.
Key takeaways
- Fallback protects reach, but blended delivery numbers hide what really happened.
- Report channel metrics and outcome metrics separately.
- Use shared campaign IDs and distinct link tags so every click can be traced.
- Compare channels on clicks, conversions and cost per conversion, not read rates.
- Treat the fallback SMS as a first-class message.
Get clear numbers from every message you send
MDS Digital Media helps brands plan and run RCS messaging alongside bulk SMS with reporting that shows exactly where each message landed and what it produced.
Request a demo and see how multi-channel analytics can sharpen your next campaign.
