RCS vs SMS vs WhatsApp: Which Channel for Your Shop

RCS stands for Rich Communication Services. It is the carrier-operated successor to SMS, and it arrives in the phone's default messaging app rather than in a separate app the customer has to install. Apple describes it as a carrier-provided service that supports high-resolution photos and videos, links, delivery receipts, read receipts and typing indicators (Apple Support, retrieved 2 October 2026).

The business side of it is a separate product called RCS for Business. A verified sender name carries a checkmark, and messages can hold rich cards — an image, GIF or video with a title, a description and up to four suggested replies or actions, several of them arranged in a scrollable carousel.

The structural difference from SMS is not the media. SMS is a text transport that every handset made in the past three decades understands, with no account, no app and no server in between. RCS is an IP service that needs a modern handset, a supporting carrier and a platform account. One of its consequences is easy to miss and shapes how you can use it: an RCS for Business agent opens the conversation, and users cannot start a conversation with your agent — they can only reply once it has started (Google for Developers, RCS for Business documentation, retrieved 2 October 2026).

No — and this is the number that decides the channel, not the feature list.

Four separate conditions have to hold at the same time before an RCS message lands:

• The operating system. On iPhone, RCS requires iOS 18 or later. End-to-end encrypted RCS arrived later still, as a beta in iOS 26.5, and only with supported carriers.
• The carrier. Apple's wording is unambiguous: RCS messaging is a carrier-provided service, and availability varies by region and carrier. If the carrier has not switched it on, the setting does not even appear on the phone.
• The customer's own choice. On iPhone, RCS Business Messages is a separate toggle under Settings, Apps, Messages, RCS Messaging. A customer who leaves RCS on for friends can still switch business messages off.
• A fallback. When the device does not support RCS, Google's platform returns a 404 error and the sender is expected to fall back to another technology, such as SMS.

Read that fourth point again, because it is the planning consequence. An RCS programme is in practice an RCS-and-SMS programme. You write two versions of every campaign, you carry two cost lines, and your audience is split by a condition you do not control and cannot see in your own customer records. Market-level coverage charts do not tell you your coverage. Only a test send against your own list does.

That is the contrast worth holding on to. On WhatsApp the gate is consent, which you control and can improve. On RCS the gate is infrastructure, which you cannot. If you want to see what the WhatsApp side looks like as a set of flows and campaigns rather than as a protocol, the Keaz templates overview shows the campaigns a store actually runs.

Capabilities only below — no rates. Message prices on all three channels move independently of each other and of this article, so compare them at the source rather than from a blog post.

SMS

• Reaches any mobile number, with no app and no account on the customer's side.
• 160 characters per segment in the standard character set, and fewer once you use special characters. Longer texts are split into several segments.
• No sender branding, no buttons, no media, no read receipts.
• Links arrive as bare URLs from an unidentified sender — which is precisely what a phishing message looks like, and customers have learned to treat it that way.

RCS for Business

• Arrives in the default messaging app under a verified sender name with a checkmark, once the brand has passed verification and launch approval.
• Rich cards with image, GIF or video, a title, a description and up to four suggested replies or actions; several cards can run as a carousel.
• Delivery receipts, read receipts and typing indicators.
• Messages are encrypted between the agent and Google's servers, and between Google's servers and the device. Google's documentation states that partners cannot use their own encryption keys, because Google needs to scan messages for malicious content.
• The agent always opens the conversation. A customer who wants to ask something cannot start one.

WhatsApp Business Platform

• Reaches contacts who gave you a documented opt-in, inside an app most of your DACH customers already open daily.
• Media, buttons and quick replies, plus a genuine two-way conversation that the customer can start.
• A 24-hour customer service window opens with each customer message; outside it, only approved templates go out. Meta's current rates, messaging limits and window rules are collected, dated and sourced on our WhatsApp Business Platform facts page.
• Replies land in a shared inbox where a person can take over mid-conversation.

If you are weighing a messaging channel against the email programme you already run, the same exercise on email is set out in our comparison of WhatsApp and email marketing. The short version there applies here too: a new channel earns its place by adding reachable, consenting contacts, not by looking more modern.

The three channels gatekeep in completely different places, and this is where a comparison usually goes wrong.

On WhatsApp, Meta requires an opt-in before the first business message and requires the business to be named when it is collected. The platform rule and the legal rule point the same way, which is why the record is worth keeping properly. In Keaz that record lives on the contact as an opt-in level rather than in a separate subscriber list, and a flow can require a minimum level before anyone enters it — the mechanics are in how opt-in levels work. How to collect that consent in the first place is a longer subject, covered in our guide to collecting WhatsApp opt-ins the GDPR-compliant way.

On RCS, the gate sits before you, not before the individual message. Google requires brand verification and launch approval before an agent may send at all. What the customer gets afterwards is a switch and a junk-report button. That is a real protection for them, but it is not a consent record you hold, can audit, or can carry to another system.

On SMS there is no platform gatekeeper at all. Nobody approves your sender, nobody reviews your content, and the only rules are the legal ones in the market you are sending to. That sounds like freedom and is mostly exposure: the channel with the weakest platform enforcement is the channel where a mistake is entirely yours.

Which reframes WhatsApp's opt-in requirement. It reads as friction when you are setting the channel up. It behaves as an asset the moment anyone asks you to prove why a given person received a given message — because the answer is a dated record attached to the contact, not an inference.

This section sets out principles rather than legal advice. Consent requirements for electronic marketing differ by market and change; have your own counsel review how they apply to your store before you send.

Answer four questions with your own data before you answer the channel question at all.

1. What share of your customer records holds a usable mobile number at all? Every channel here fails at the same place if the number is missing, and that gap is usually larger than store owners expect.
2. On which channel can you attribute revenue to a specific send, rather than reporting a delivery rate and hoping?
3. On which channel can a customer answer and reach a person? A campaign that generates questions it cannot receive creates work somewhere else in the business.
4. Which consent record do you own, and could you produce it on request?

For a Shopify store in DACH with a list in the low thousands, those four questions tend to resolve the same way. Start where consent, measurement and two-way conversation are solved together rather than separately, which today means WhatsApp. Keep SMS as the transactional fallback it is good at — the delivery note that has to arrive on any handset. And treat RCS as a channel to re-evaluate on a date, not to adopt on an argument: revisit it when a test send against your own list shows real coverage, not when a vendor shows you a market-level adoption chart.

One more thing worth saying plainly, because it cuts against how channel comparisons are normally written. Adding a channel rarely adds revenue on its own. It adds a surface that has to be fed with content, measured, and answered when someone replies. Two channels run properly beat three run partly, every time. What that looks like in sends, segments and campaign reporting is described in the newsletter overview in our help center.

• Treating a market-level RCS adoption figure as your own coverage. Your coverage is the share of your list on a supporting carrier, a supporting OS, with the business toggle left on. Nobody can tell you that number except a test send.
• Designing the campaign for RCS and the SMS fallback as an afterthought. A meaningful share of the audience will only ever see the fallback, so the fallback is the campaign for them.
• Assuming the RCS verified-sender checkmark and the WhatsApp Official Business Account blue badge are the same thing. Different programmes, different issuers, different requirements — earning one gets you nothing towards the other.
• Running all three channels at once without a single consent record. The question is never which channel a message went out on; it is why that person was on the list.
• Reusing one creative across all three. A rich card, a 160-character SMS and a WhatsApp template are three different formats with three different review regimes; copy pasted between them performs badly in at least two.
• Choosing on per-message rate alone. The number that matters is revenue per delivered message, and a cheaper message that nobody acts on is the more expensive option.
• Comparing open rates across channels. They are measured differently on each and are not the same metric wearing three names.