BroadNet
Operations BroadNet answer

What is OTT bypass?

Last reviewed 1 min readReviewed by BroadNet engineering
Quick answer

OTT bypass is the slow replacement of operator SMS revenue by Over-The-Top messaging apps (WhatsApp, Telegram, iMessage, Signal). Globally, P2P SMS traffic has declined ~30% since 2019 as users move conversational messaging to OTT. For operators, OTT bypass is the loss of the consumer messaging tariff. For enterprise senders, it is the rebalancing of channel mix toward WhatsApp and RCS.

Plain-language definitionVendor-neutralReviewed May 27, 2026
DiagramWhere an SMS firewall sits in the operator network
  1. Inbound A2P and interconnect trafficFrom aggregators and international partners
  2. SMS firewallInspects every message in real time
  3. Operator SMSCOnly clean traffic is delivered
  4. Subscriber handset
  • Grey routes, spoofed sender IDs and spam are blocked
  • Legitimate A2P traffic is identified and billed
The long answer

Everything worth knowing, nothing that isn't.

§01

The two flavours

Consumer OTT bypass: people texting friends use WhatsApp instead of SMS. Operator loss: P2P SMS volume. Enterprise OTT bypass: businesses send order confirmations via WhatsApp Business instead of SMS. Operator loss: A2P SMS volume (partially offset by operator-hosted RCS revenue, where deployed). In MENA, P2P-OTT bypass is essentially complete in UAE/KSA/Lebanon; enterprise A2P-OTT bypass is at ~30% penetration and growing.

§02

Why it isn't a wipeout

Three structural reasons SMS persists. Universal reach (every handset, no app install). OTP requirement (banks and regulators still mandate SMS for 2FA in many markets). Operator-grade deliverability (RCS and WhatsApp depend on the user being signed-in and data-connected; SMS works on a flip phone in a basement). Even in saturated markets, SMS A2P volume continues to grow because OTP and emergency-alert use cases keep expanding.

§03

What the channel mix looks like in 2026

Marketing: 60% WhatsApp / RCS, 30% SMS, 10% other (push, email-to-SMS). Transactional: 70% SMS, 25% WhatsApp, 5% push. Authentication (OTP): 75% SMS, 15% WhatsApp, 10% Flash Call / silent verify. The trend lines: marketing continues to shift toward rich channels; OTP shifts slowly toward silent-verify; transactional remains SMS-dominant because of universality.

§04

What enterprise senders should do

Don't pick a channel; pick an orchestrator. BroadNet's omnichannel router (see /products/omnichannel) picks the cheapest delivering channel per recipient per use case — fallback chains like WhatsApp → SMS → Voice for OTPs, RCS → SMS for marketing. The mix self-tunes over time as channel costs and reach shift.

BNWritten by the BroadNet engineering team·Operating carrier-grade messaging since 2003, headquartered in Dubai·Editorial standards
Build with this

Need help wiring this up?

The pages below are the products and integration guides that put this concept on the wire. If you'd rather walk through it live, our engineering team takes calls same-day during MENA working hours.

Talk to our engineering team
Feedback

Was this answer helpful?

Your vote helps us prioritise which answers to expand with examples, diagrams, and code snippets.

Was this answer helpful?
Thanks — noted. We'll keep this answer maintained.
Got it. Tell us what was missing — send a quick note.

How we write and review content

Related questions
See the full library
Still need help?

Talk to a real engineer about your build.

We reply within one business day, and production accounts get 24/7 support. Our solutions engineers ship code, not scripts.

Talk to support Speak with sales
$ curl -X POST https://api.broadnet.me/sms/sendSms
Response SLA
Test-access requestsReply within 1 business day
Production24 / 7 · < 15 min
Operator NOC24 / 7 · pager
support@broadnet.me · +971 4 456 7768