CS Business Messaging (RBM) is branded, verified, interactive messaging that renders in the native Messages app with no app install. In 2026 it is a real channel — Apple added RCS in iOS 18 and rich business features from iOS 18.1 — but reach still depends on handset, carrier, and provisioning, so SMS fallback remains mandatory for guaranteed delivery.
What changed: Apple, scale, and encryption
For a decade RBM's biggest gap was the iPhone. That closed. Apple shipped RCS support in iOS 18 in September 2024, and RCS Business features began rolling out from iOS 18.1, bringing verified sender branding and rich cards to a base that had been SMS-and-iMessage only. The addressable audience for RBM roughly doubled overnight in markets where carriers had RCS live.
The user numbers followed. Juniper Research put RCS at about 1.1 billion active users in 2024, with a forecast near 3.8 billion by 2026. On the enterprise side, Omdia forecasts A2P RCS revenue reaching $4.2 billion by 2029, with traffic climbing from roughly 1.5 trillion messages in 2024 to about 6 trillion by 2029. And on privacy, cross-platform end-to-end encryption for RCS began rolling out through 2026 — appearing in the iOS 26.5 beta in May 2026 — closing the gap that let SMS-style interception apply to earlier RCS.
What RBM gives you over SMS
| Capability | SMS | RCS Business Messaging |
|---|---|---|
| Verified brand identity | Sender ID only (spoofable) | Verified sender: name, logo, brand colour, checkmark |
| Rich content | 160 chars, text only | Cards, carousels, images, video, buttons |
| Suggested actions | None | Dial, open map, open URL, quick replies |
| Delivery feedback | Coarse DLR | Structured delivered / read / typing events |
| Encryption | None in transit at the SMS layer | End-to-end encryption rolling out cross-platform (2026) |
| Guaranteed reach | Effectively universal | Only where handset + carrier have RCS provisioned |
The problem RCS does not solve: universal reach
RBM only works if the recipient's handset, on its current network, has RCS provisioned. That is not knowable from the phone number alone. A number that was RCS-reachable yesterday may not be today — the SIM changed, the device changed, or the user is roaming on a network that does not carry RCS. Treating RCS as guaranteed is the single most common deployment mistake, and it silently strands messages on handsets that never receive them.
This is why capability variance, not raw adoption, is the real design constraint. Even at a forecast 3.8 billion users (Juniper Research), a meaningful share of any given send list will not be RCS-reachable at the moment you send. The architecture has to assume that and route accordingly.
The fallback architecture that actually works
The correct pattern is capability-check-then-cascade. Query whether the number is RCS-reachable at send time; deliver over RCS if it is; and fall through to a lower-tier channel if it is not — without the sender having to orchestrate any of it.
- Capability check — is this MSISDN RCS-reachable on its current network right now?
- If yes — send the verified, rich RBM message and collect delivered/read callbacks.
- If no — fall back to WhatsApp Business (where you have opt-in) or straight to SMS.
- Always keep SMS as the terminal fallback — it is the only channel that is effectively universal.
- Reconcile events — normalise RCS, WhatsApp, and SMS delivery signals into one view so reporting is channel-agnostic.
BroadNet's RCS messaging runs the capability check and the fallback cascade inside a single request: you send one payload, and the platform delivers over the richest channel that will actually arrive — RCS where provisioned, SMS everywhere else.
When to invest in RCS in 2026
Start where coverage is mature and the use case rewards rich, verified messaging — order updates, appointment management, and post-purchase notifications are strong first candidates. Get your verified agent approved early; brand verification with an operator can take two to four weeks. Model RCS on conversion lift and reduced support escalations, not on unit price — it usually is not cheaper than SMS, but branded verified messages convert better and generate fewer 'is this real?' support calls. For a plain-language primer to circulate internally, see our answer on RCS Business Messaging.
Frequently asked questions
Does the iPhone support RCS Business Messaging now?
Yes. Apple added RCS to iOS 18 in September 2024, and RCS Business features — verified sender branding and rich cards — began rolling out from iOS 18.1. Reach on any specific iPhone still depends on the carrier having RCS provisioned for that line, so it is broad but not automatically universal.
Why do I still need SMS fallback if RCS is growing?
Because RCS delivery depends on the handset and carrier having RCS provisioned at the moment you send, which is not knowable from the number alone. Even with a forecast 3.8 billion users (Juniper Research), part of any send list will not be reachable over RCS, so SMS remains the terminal fallback that guarantees the message can land.
Is RCS end-to-end encrypted?
Cross-platform end-to-end encryption for RCS began rolling out in 2026 — it appeared in the iOS 26.5 beta in May 2026 — extending E2EE beyond single-platform chats. Coverage depends on both endpoints and their client versions supporting it, so E2EE is arriving rather than guaranteed on every RCS conversation today.
Is RCS cheaper than SMS or WhatsApp?
Usually not. RBM in most markets sits between SMS and WhatsApp on cost and is billed per message or per conversation depending on the operator. The economic case is conversion lift and lower support load from branded, verified, interactive messages — not a lower unit price. Model it on outcomes.
References
- Apple Newsroom — iOS 18 availability (RCS support): apple.com
- Juniper Research — RCS market forecasts: juniperresearch.com
- Omdia — A2P and RCS messaging research: omdia.tech.informa.com
- GSMA — RCS Business Messaging: gsma.com