Everything worth knowing, nothing that isn't.
What SMS is, and why it endures
SMS rides the GSM signalling channel (SS7 MAP), which means it works with no data connection, on every handset built since the early 1990s, in every country, over 2G through 5G. That universality is its superpower: an OTP or a critical alert sent by SMS will reach essentially any live number. The cost is capability — 160 characters in GSM-7 (70 in UCS-2 for Arabic/emoji), no media, no interactivity, and a sender that is at best an alphanumeric string with no verified identity.
- Universal reach: every handset, every network, no data required.
- 160 GSM-7 chars per segment (70 UCS-2); longer messages are billed per segment.
- No media, no branding, no read receipts — plain text only.
- The default for OTP and critical alerts precisely because it always arrives.
What RCS adds
RCS Business Messaging turns the native Messages inbox into a branded, app-like surface. You get a verified sender (your brand name, logo, and colour, with a verified badge the carrier grants after vetting), rich cards and image carousels, quick-reply and action buttons, read receipts, and typing indicators — all inside the phone's default messaging app, with no app to install. Because it is carried over data via the GSMA Universal Profile and MaaP (Messaging-as-a-Platform), it behaves far more like a chat app than like SMS.
- Verified branded sender: name, logo, colour, verified badge.
- Rich cards, carousels, suggested replies and action buttons.
- Read receipts and typing indicators — real conversational signals.
- Runs in the native Messages app; nothing to install.
Reach and the SMS fallback
This is the practical crux. SMS is ~100% of live numbers. RCS reach depends on device, OS, carrier enablement, and data connectivity — large and growing (Android has shipped Universal Profile since 2019; Apple added RCS in iOS 18 in 2024) but not universal. The standard pattern is RCS-with-SMS-fallback: attempt RCS, and if the recipient is not RCS-capable or offline, automatically deliver an SMS. You get the rich experience where it is available and reliable SMS delivery everywhere else — but you must design content that degrades gracefully.
- SMS: effectively 100% of live numbers.
- RCS: modern Android + iOS 18, carrier-enabled, data-connected.
- Best practice: RCS first, automatic SMS fallback.
- Design the message so the SMS fallback still makes sense on its own.
Billing and where each wins
SMS is billed per segment at a well-understood per-message rate. RCS is billed per message or per session at operator-set rates that are typically higher than SMS but buy engagement — branded, interactive RCS consistently outperforms plain SMS on open and conversion for marketing and rich notifications. The rule of thumb: use SMS for anything that must always arrive instantly and cheaply (OTP, transactional alerts, delivery-critical notices), and use RCS (with SMS fallback) for branded, interactive, higher-value experiences where richer content lifts conversion.
- SMS: per-segment, lowest cost, maximum reliability.
- RCS: per-message/session, higher cost, higher engagement.
- SMS for OTP and critical alerts; RCS for branded, interactive journeys.
- RCS with SMS fallback captures both when it matters.
RCS vs SMS at a glance
| RCS Business Messaging | SMS | |
|---|---|---|
| Message length | Multi-thousand characters + media | 160 GSM-7 / 70 UCS-2 per segment |
| Rich media | — | |
| Verified branded sender | — | |
| Read receipts & typing | — | |
| Suggested replies / buttons | — | |
| Bearer | Data (GSMA Universal Profile / MaaP) | Signalling channel (SS7 MAP) |
| Reach | Modern Android + iOS 18, carrier-enabled | Every handset, every network |
| Works without data | — | |
| Best for | Branded, interactive, higher-value journeys | OTP, critical alerts, universal delivery |