CS spent a decade as the channel that was always two years away. Then Apple shipped RCS Universal Profile support in iOS, Android had already made it the default messaging experience, and the reach question that kept enterprise budgets away stopped being the blocker. For operators the strategic question has sharpened accordingly: RCS as a P2P service generates no direct revenue — it rides the data bundle exactly as OTT messaging does. The revenue is in RCS Business Messaging, and whether an operator captures it depends on decisions being made now: who hosts the infrastructure, who verifies the senders, and who sets the price of a branded message to the operator's own subscribers.
The P2P trap, stated plainly
An operator that launches RCS P2P and stops there has upgraded its subscribers' messaging experience and its own cost base, and nothing else. P2P RCS messages are IP traffic; there is no per-message billing event, no interconnect fee, no termination revenue. That is not an argument against launching it — subscriber experience and churn matter — but it means the business case must be written on the A2P side from the start. The parallel with SMS is exact: P2P SMS revenue has been declining for fifteen years while A2P monetisation became the profit pool. RCS compresses that history into a much shorter window.
Where the money actually flows in RBM
RCS Business Messaging has a billing anatomy that operators should understand before signing anything. An enterprise sends through an RBM aggregator or platform; the message terminates on subscribers via a MaaP (Messaging as a Platform) infrastructure that is either operator-hosted or hosted by a third party on the operator's behalf; the operator's leverage is that termination to its subscribers is the thing everyone else in the chain is selling. Three revenue components follow: a per-message or per-session termination fee (the analogue of the A2P SMS rate), a share of premium rich-media pricing, and onboarding or verification fees for registered senders. Operators that host their own MaaP — or contract it with clear commercial terms — keep the termination economics. Operators that let the ecosystem route around them discover that branded traffic to their subscribers is being sold with no operator line item at all.
Typical commercial shapes in 2026
| Model | Unit | Industry-typical range | Notes |
|---|---|---|---|
| Basic message | Per message | At or near A2P SMS parity | Text-only RBM; priced against the SMS alternative |
| Rich single message | Per message | 1.5–3x SMS rate | Cards, carousels, media; premium justified by engagement |
| Conversation / session | Per 24h session | 2–6x single-message rate | Caps enterprise cost for two-way flows; mirrors OTT pricing |
| Verified-sender onboarding | Per sender, annual | Low-to-mid three figures | Verification is an operator-anchored trust product |
The ranges are wide because the market is young and corridor-specific, but the structure is stable — and it is the structure operators should negotiate for, not the individual numbers.
What an operator has to stand up
- A MaaP hosting decision — self-hosted, third-party hosted with revenue terms, or hub-based. The wrong version of 'free hosting' costs the termination margin forever.
- Sender verification authority — the process that decides which enterprise gets a verified brand identity on the operator's subscribers' screens. This is a trust product, and it should not be given away unpriced.
- Anti-spam and anti-fraud policy from day one — RCS spam and phishing with branded look-and-feel already exist in early markets, and a channel sold on trust dies quickly without enforcement. The firewall discipline from SMS carries over directly.
- Interconnect posture — RBM traffic between operators and from international senders needs the same route-quality and revenue-assurance thinking as SMS interconnect.
The realistic revenue model
The honest forecast for most networks: RBM will not replace A2P SMS revenue one-for-one in its first years, and modelling it that way produces disappointment and underinvestment. The pattern in early-adopting markets is that RBM opens as a premium tier alongside SMS — marketing and conversational commerce traffic upgrades first, OTP and transactional traffic stays on SMS far longer because nothing beats its reach and simplicity. The compounding upside is in engagement-priced products: branded OTP with the bank's verified identity, rich delivery notifications with reschedule buttons, conversational support sessions. Those carry pricing that SMS never could. For the MENA-specific rollout picture — which operators have launched, and the regional sequencing — see the RCS in MENA piece.
The window is the strategy
The genuinely time-sensitive part is that RBM commercial structures are being set now, market by market, and they harden quickly. Operators that arrive early set verification pricing, termination rates, and hosting terms; operators that arrive late inherit whatever the early movers and the platform ecosystem agreed. The SMS lesson applies unedited: the operators that built sender-ID registries and firewalls early still run the best-monetised A2P businesses today. RCS is the same institutional muscle, pointed at the next channel.
BroadNet works on both sides of the RBM equation — RCS messaging for enterprise senders, and MaaP, verification, and monetisation strategy inside operator engagements.