or a decade, RCS Business Messaging (RBM) was a channel everyone promised and nobody could actually deliver at scale. That changed. Apple shipped RCS support in iOS 18 in 2024 and broadened carrier coverage through 2025, which removed the single largest gap in the addressable base. In MENA specifically, the Google Jibe RBM platform is now interconnected with several Gulf operators, and verified-agent onboarding is open. RCS in the region went from a roadmap item to a deployable channel in roughly eighteen months.
Where the Gulf operators stand
- UAE — du and e& (Etisalat) both have RBM live via Jibe; verified-sender onboarding is open through aggregators, with sender verification handled by the operator's brand team.
- Saudi Arabia — STC and Mobily are in progressive rollout; Zain KSA is in technical trials. Coverage is real but not yet universal across all device/network combinations.
- Qatar and Kuwait — Ooredoo and stc Kuwait have RBM in pilot, primarily for large enterprise and government agents.
- Egypt — RBM is later-stage; SMS and WhatsApp remain the practical channels there through 2026.
What RCS actually gives you over SMS
RBM is branded by default: a verified agent name, logo, brand color, and a verification checkmark render directly in the native Messages app — no app install, no link-out. It supports rich cards, carousels, suggested replies, suggested actions (dial, open map, open URL), and high-resolution media. Critically for transactional senders, RBM gives you read receipts and typing indicators, and delivery/read events come back as structured callbacks rather than the coarse DLRs you get from SMS.
The capability-check problem
RBM only works if the recipient handset, on its current network, has RCS provisioned. That is not knowable from the MSISDN alone. The correct pattern is a capability check before send: query whether the number is RCS-reachable, and if not, fall through to SMS or WhatsApp. Treating RCS as a guaranteed channel is the single most common deployment mistake — it strands traffic on handsets that silently never receive the message.
BroadNet's omnichannel API runs the RCS capability check automatically and falls back to WhatsApp or SMS in the same request. You send one payload; the platform picks the channel that will actually arrive.
Pricing reality
RBM in MENA is billed per conversation or per message depending on operator, and in 2026 it generally sits between SMS and WhatsApp on cost. The economic case for RCS is not that it is cheaper — it usually isn't — it's that branded, rich, verified messages convert materially better for marketing and produce fewer support escalations for transactional traffic. Model RCS on conversion lift, not on unit price.
How to plan a 2026 RCS deployment
Start with a single high-value use case — order updates or appointment management are good first candidates — in the UAE, where coverage is most mature. Build the fallback chain from day one (RCS → WhatsApp → SMS) so no traffic is ever stranded. Get the verified agent approved early; brand verification with the operator can take two to four weeks. Then expand market by market as Saudi coverage fills in. RCS is ready enough to deploy in 2026; it is not yet ready to deploy as your only channel.