App Development

RCS business messaging vs SMS and WhatsApp in 2026

8 min readBy Sandeep Mahajan

A blue phone and an orange phone side by side on a light wooden desk

RCS (Rich Communication Services) is the carrier messaging standard that replaces plain SMS with branded, verified messages that can carry images, buttons and carousels, and it now works on Android and on iPhones running iOS 18 or later with a supporting carrier. For most businesses it is not a replacement for SMS or WhatsApp but a layer on top: send RCS where the phone and carrier support it, fall back to SMS where they do not, and use WhatsApp where your customers already live on it. Sender approval is per country and takes weeks, so plan for it.

Key takeaways

  • RCS on iPhone needs iOS 18 and a carrier that supports RCS on iPhone, according to Apple; RCS is a carrier-provided service.
  • Business RCS uses a branded sender profile instead of a phone number, with rich cards, carousels, up to 11 suggested replies, and delivery and read receipts (Twilio).
  • Carriers must approve an RCS sender before it can message anyone outside test devices; Twilio says to allow four to six weeks or longer for multiple regions, and its sender registration list does not include Canada or India.
  • With Twilio, an RCS sender in a Messaging Service falls back to SMS or MMS automatically when a device cannot receive RCS.
  • WhatsApp has charged per delivered message since 1 July 2025, and from 1 October 2026 service messages beyond 1,000 free per month per number are charged (Meta).

What is RCS, and how did it get here?

RCS is a GSMA standard for carrier messaging: the same default messaging app and phone number as SMS, but with features people expect from chat apps, such as typing indicators, high-resolution photos and read receipts. Google spent years trying to build its own messaging app; in April 2018 it paused work on Allo and put its effort into "Chat", an RCS-based upgrade to Android Messages built with carriers. That bet is what this post covered when it was first written.

Two later changes made RCS relevant for business. Apple added RCS to iPhone with iOS 18. And in March 2025 the GSMA published RCS Universal Profile 3.0, which adds end-to-end encryption based on the Messaging Layer Security (MLS) protocol. Apple began rolling out end-to-end encrypted RCS in beta on iOS 26.5 in May 2026, for supported carriers and with Android users on the latest Google Messages. Apple says the encryption applies only when every participant's carrier supports it.

Google now calls the business side "RCS for Business"; its developer pages describe branded, rich-media conversations and a "Verified" icon for approved senders.

How do RCS, SMS and WhatsApp compare?

SMS RCS for Business WhatsApp Business Platform
Where it arrives Default messaging app on any phone Default messaging app, on supported Android and iOS 18+ devices with supporting carriers WhatsApp app, if the customer has it
Sender shown Phone number or short code Brand name, logo and colours, with a verified badge Business profile on a registered number
Content Plain text; 160 GSM-7 characters per segment (70 with emoji or other Unicode) Text, media, rich cards, carousels, suggested replies and actions Text and media; business-initiated messages use approved templates
Setup Number plus country rules (for US long codes, A2P 10DLC registration) Sender registration with Google and carrier approval per country Registered WhatsApp sender
Billing basis Per segment (Twilio) Set by provider and country; check your provider's price list Per delivered message, by template category (Meta)

SMS still has one advantage nobody else matches: it reaches every phone. RCS has a better experience in the default app but only where device and carrier support it. WhatsApp has rich features and its own audience, but only for customers who use WhatsApp and have opted in.

When does RCS make sense for a business?

RCS earns its setup effort when the message benefits from looking official and from buttons:

  • Order and delivery updates with a product image and a "track" action.
  • Appointment reminders with "confirm" and "reschedule" suggested replies, so the reply comes back structured instead of free text.
  • Verification codes from a branded, verified sender, which is harder to imitate than a number. Twilio's Verify API can send codes over RCS.
  • Simple choices, such as picking a delivery slot from a carousel.

It makes less sense for low-volume, plain-text alerts in a country where the sender is not yet approved, or where most of your customers are on WhatsApp anyway.

What does it take to send RCS?

A registered and approved sender. Twilio's onboarding guide lists the steps: create an RCS sender and test it on test devices; register it for compliance with Google and, for US recipients, with US carriers; wait for carrier approval; then add it to your Messaging Service for production. Registration asks for your opt-in and opt-out policies, a description of the use case and a video showing it. Twilio says to "allow four to six weeks or longer" for multiple regions and that approval times vary by carrier.

As of October 2026, Twilio's sender registration list covers the United States, Mexico, the United Kingdom and a number of European countries. Canada and India are not on it, so if those are your main markets, check your provider's coverage before you design around RCS.

How does fallback to SMS work?

With Twilio, through a Messaging Service. When an RCS sender is in the service's sender pool, Programmable Messaging checks whether the recipient's device supports RCS and, if a message cannot be delivered over RCS, sends it as SMS or MMS from another sender in the pool. You can name the fallback sender with the FallbackFrom parameter, which works only when sending through a Messaging Service. If you add the rcs: prefix to the recipient number, automatic fallback is off and your own code must retry on another channel.

Two practical consequences:

  1. Write each message twice. The RCS version can have a card and buttons; the SMS version must make sense as plain text, with a link instead of buttons. Keep it short, because SMS is billed per segment.
  2. Keep your SMS registration current. Fallback in the US still sends from an SMS sender, which needs its A2P 10DLC registration for long-code numbers.

Where does WhatsApp fit?

WhatsApp is the better choice where your customers already use it and expect to reach you there, and for conversations rather than one-way alerts. Meta's rules shape how you use it:

  • A customer message opens a 24-hour customer service window; inside it you can reply freely, outside it only with approved templates.
  • Templates are marketing, utility or authentication, and are priced per delivered message since 1 July 2025.
  • Each business phone number gets 1,000 free delivered service messages per month; from 1 October 2026, service messages beyond that are charged.
  • New business portfolios can message 250 unique users per 24 hours outside a service window, rising as the business is verified and sends good-quality templates.

Our Twilio integration work covers SMS, WhatsApp, voice and verification. The same groundwork applies whichever channel you add: status callbacks that record each message, opt-out handling, webhook signature checks and the registration rules for the countries you send to.

How should you choose per message?

Pick the channel per message type, not per company:

Message First choice Fallback
One-time passcode SMS or RCS (verified sender) Voice call
Delivery or appointment update RCS where approved SMS
Customer support conversation WhatsApp, or your support assistant Email
Marketing offer The channel the customer opted into None: respect the opt-in

Record the channel, status and any error code for every message, so you can see whether RCS actually delivers better than SMS for your customers. Twilio notes that in many regions RCS tracks delivered and read statuses more reliably than SMS. If messages trigger follow-up steps, such as rescheduling in a booking system, our workflow automation page covers how we connect those systems.

FAQ

Do iPhone users receive RCS business messages?

RCS on iPhone requires iOS 18 and a carrier that supports RCS on iPhone, according to Apple. Where either is missing, a Messaging Service can fall back to SMS.

Is RCS end-to-end encrypted?

Person-to-person RCS can be, under GSMA Universal Profile 3.0, when every participant's carrier supports it; Apple rolled this out in beta in iOS 26.5. The Apple and GSMA announcements do not say that business messages are covered, so treat business RCS as protected in transit, not end-to-end encrypted.

How long does RCS sender approval take?

Twilio advises allowing four to six weeks or longer if you launch in several regions, and says approval times vary by carrier.

Does RCS replace SMS?

No. RCS reaches only supported devices and carriers, so SMS remains the fallback and the only channel that reaches every phone.

Is WhatsApp cheaper than SMS?

It depends on the country, the template category and whether a customer service window is open. Compare your provider's current price lists for your countries rather than relying on a general rule.

Can one integration send all three?

With Twilio, yes: Programmable Messaging sends SMS, MMS, RCS and WhatsApp messages, and Messaging Services handle sender pools and fallback.

Sources (12 links)
Share this article