Run the same campaign on SMS, RCS and WhatsApp and you get three reports that do not line up. One counts deliveries, another counts reads, and the third is full of replies. Comparing engagement across the three channels means first agreeing what you are measuring. This post covers how the channels differ, which metrics can be compared fairly, and why most teams do better using all three together than choosing a single winner.
How do SMS, RCS and WhatsApp differ?
SMS
SMS is plain text that reaches every mobile phone. There is no app to install and nothing to set up on the customer’s side. That reach is its strength. Its limit is that a text message carries very little, and tells you very little about what happened after it arrived.
RCS
RCS messages arrive in the phone’s own messaging app, the same place a text would. Whether a customer can receive one depends on their phone and their network, so RCS covers part of an audience and not all of it.
WhatsApp reaches customers who use the app, through the official WhatsApp Business API. Messages a business sends first use approved templates, and once the customer replies, the thread becomes a two-way conversation. For many customers it is the channel they check first.
Which engagement metrics can you compare across channels?
- Delivery rateMessages delivered, divided by messages sent. Available on all three, and the base for every other number.
- Read rateUseful only where the channel reports it. SMS confirms delivery and nothing more, so a read rate cannot be compared across all three.
- Reply rateReplies divided by delivered messages. It works on every channel and is the clearest sign that a message was noticed.
- Click rateClicks on a tracked link, measured the same way on each channel.
- Completion rateThe share of recipients who did what the message asked: confirmed, paid, booked or rescheduled.
- Opt-out ratePeople who asked to stop receiving messages. This is engagement too, of the kind you want less of.
If you track only one number, make it completion rate. A reminder that was read and ignored did less for you than one that was answered.
Why do raw numbers mislead?
Three things distort a simple side-by-side comparison:
- Different audiencesThe customers you reach on WhatsApp are not the same group you reach by SMS. A difference in results may come from the people, not the channel.
- Different messagesA plain text and a longer WhatsApp message with a reply option are not the same offer. You may be measuring the content.
- Different measurementOne channel reports reads and another does not. A missing number is not a zero.
How do you run a fair comparison?
- Choose one goal and one main metric for the campaign, ideally a completed action.
- Split a single audience at random across the channels, limited to people who can be reached on each.
- Send the same offer at the same time, in wording as close as each channel allows.
- Measure against delivered messages, not sent ones.
- Count replies, and count what happened to them. A reply nobody answered is a lost customer.
- Repeat the test. One campaign is an anecdote.
- Weigh the result against what each channel costs you to send.
The channel that wins is usually the one the customer was already looking at.
Which channel suits which message?
| SMS | RCS | ||
|---|---|---|---|
| Where it arrives | Every mobile phone | The phone’s own messaging app | The WhatsApp app |
| Who it reaches | Anyone with a mobile number | Customers whose phone and network support it | Customers who use WhatsApp |
| What it suits | Short notices that must reach everyone | Customers who are not on WhatsApp | Messages that invite a reply |
There is no single ranking, and the fit depends on the job. SMS suits short notices that have to reach everyone, whatever phone they carry. WhatsApp suits messages that invite a response, such as a reminder the customer may want to reschedule, or an update that may raise a question. RCS reaches customers who are not on WhatsApp in the messaging app already on their phone. Your own results should decide the mix, which is the reason to run the comparison at all.
Why use all three with fallback?
Choosing one channel means accepting its gaps. The alternative is to write the campaign once and let each message go out on a channel that customer can receive. Auxy’s WhatsApp, SMS and RCS campaigns run on SMS and RCS alongside WhatsApp, with fallback between them: if a message cannot be delivered on one channel, it is sent on the next.
Fallback changes the question you ask. You stop asking which channel performed best, and start asking how many customers received the message and acted on it.
What happens to the replies?
Engagement is only worth measuring if someone answers it. A campaign that gets replies and leaves them unread has created a support problem. In Auxy the same AI agent reads what comes back and finishes the job in the thread, or hands it to a person, and every conversation appears in the unified inbox next to calls, chat and email. For customers who do not respond to a message at all, AI outbound calling can follow up by phone.
One rule applies to every channel: message only people who have agreed to hear from you, and act on opt-outs straight away. No engagement metric makes up for a customer who feels spammed.

