RCS vs SMS vs WhatsApp: which message should you actually send?
Three channels, one phone. Here is the decision rule we use per message type — and why the answer is almost never 'pick one'.
Most brands treat messaging as a single line item and then argue about which channel to standardise on. That argument has no winner, because RCS, SMS and WhatsApp are good at genuinely different things. The useful question is not which channel, it is which message.
What each channel is actually good at
- RCS: branded, verified sender with logo, images, carousels and tappable buttons, delivered in the phone's default Messages app with nothing to install. Best for rich broadcast — offers, order updates with tracking, appointment reminders.
- WhatsApp: the only one of the three where a real two-way conversation is natural. Best for support, order queries, re-engagement and anything that needs a human or a bot to reply.
- SMS: no rich media, no branding, but it reaches every single handset including feature phones. Best as the guaranteed fallback and for OTP and time-critical alerts.
The rule we use
Pick the channel by what the message needs to do. If it needs a reply, send WhatsApp. If it needs to be seen and tapped, send RCS. If it absolutely must arrive on every device, send SMS. Then wire the three together instead of choosing between them.
A waterfall does that automatically: attempt RCS first, fall back to WhatsApp where the customer has opted in, fall back to SMS for everyone else. Every contact gets the richest message their handset and consent allow, and you stop paying rich-channel rates for people who cannot receive rich messages.
The mistakes that cost the most
- Sending the same creative on all three. An RCS carousel rewritten as a 160-character SMS reads like spam. Write per channel or do not use the channel.
- Ignoring consent per channel. Opt-in for SMS is not opt-in for WhatsApp. Store them separately or you will get blocked.
- Measuring only delivery. Delivery is the floor. Tap-through and reply rate are what tell you the channel earned its cost.
- Skipping sender verification. On RCS the verified brand badge is a large part of why the channel outperforms SMS at all.
How to start in 30 days
- Week 1: verify your RCS brand sender and confirm your WhatsApp template library is approved.
- Week 2: take one high-volume SMS use case and split it — half stays on SMS, half moves to RCS.
- Week 3: read tap-through, not opens. Cost per tap is the number that decides the rollout.
- Week 4: turn on the waterfall for that use case and leave the rest on SMS until it earns the move.
Done this way the migration pays for itself before you have moved your whole message volume, and you never lose reach while testing.
The services behind this post.
Frequently asked questions.
RCS support has been rolling out on iOS, but Android is where the volume is — more than nine in ten Indian smartphones. Plan RCS as an Android-first channel with SMS covering everything else.
No. RCS is a broadcast channel in the default messaging app; WhatsApp is a conversation channel. Brands that do well run both, with SMS underneath as the universal fallback.
Talk to the team that does this every day.
Tell us what you're trying to grow. You'll get a plan, not a pitch.
Contact Us