A2P (application-to-person) SMS is a text message sent by a business system to a person's phone, such as a one-time passcode, an alert or a delivery notice. BroadNet carries 300M+ of them a day to 200+ countries over 1,000+ direct operator connections — direct to the operator in 86 countries, over labelled partner routes elsewhere, never over grey routes — for Google, Meta, Uber and the world's largest enterprises since 2003.
Trusted by the platforms that power the modern internet
Headline network figures, as published on the BroadNet fact sheet.
Sustained A2P traffic across all routes.
Interconnects, not aggregator hops.
Every dialable destination, MENA-first.
Operating carrier-grade since 2003.
No grey routes. Traffic rides a direct SMPP bind to the destination operator wherever a direct route is commercially available (1,000+ direct operator connections), otherwise a partner-managed route, labelled per operator on each country page. Latency is measured at every hop.
REST, SMPP 3.4/5.0, or webhook submit. Keep the returned message ID to avoid double sends.
Auth, schema validation, content screen, HLR lookup, sender-ID policy applied.
Per-route quality scoring picks the fastest legal path. Failover in milliseconds.
Direct bind to the destination MNO. No grey routes. No intermediaries.
MT delivered to handset; DLR pushed to your webhook.
REST, SMPP 3.4/5.0, or webhook submit. Keep the returned message ID to avoid double sends.
Auth, schema validation, content screen, HLR lookup, sender-ID policy applied.
Per-route quality scoring picks the fastest legal path. Failover in milliseconds.
Direct bind to the destination MNO. No grey routes. No intermediaries.
MT delivered to handset; DLR pushed to your webhook.
The four things every CTO who has lived through an aggregator failure asks about — answered before the demo.
We hold our own SMPP and SS7 binds with destination operators in 86 countries, and every other route is a labelled partner route. No grey routes, no surprise re-routing, no opaque price markups in the middle.
Operating since 2003, headquartered in Dubai. We carry 300M+ application-to-person messages a day for banks, governments, airlines, and the platforms that power the modern internet.
Local presence across the Middle East and North Africa, plus pan-African, South Asian, and South-East Asian operator relationships that make global rollouts feel like a single market.
ISO 27001 / 9001 / 22301, SOC 2 Type II, GSMA Associate Member, HIPAA-aligned, GDPR-ready. Sender-ID registrations handled by an in-region compliance team in every regulated market.
Inside each hop
REST, SMPP 3.4/5.0, or webhook. Keep the returned message ID to avoid double sends.
Engine selects optimal path by destination, operator, sender ID, regulation.
HLR lookup, content screen, anti-fraud filters, encoding detect.
Direct SMPP bind to operator MNO. No grey routes, no intermediaries.
DLR pushed to your webhook.
Pick a destination and replay three outcomes: delivered, rejected, and delivered by fallback. Each run shows the nine checkpoints with timestamps, the route decision, the operator reached and the delivery receipt (DLR) posted to your webhook.
API request accepted, message ID issued
Number format, encoding and segment count checked
UAE content and send-window rules: pass
Sender ID registered with TDRA: pass
3 operator routes scored, direct bind selected
Message submitted to Etisalat / e& on the direct bind
Handset reached, operator status DELIVRD
Delivery receipt (DLR) posted to your webhook
Route, latency and outcome logged in your console
Direct bind to Etisalat / e&
Destination operator identified from the number, then the direct route scored above the alternatives.
{
"messageId": "bn-5f2a9c1e",
"to": "+971 ••• 4567",
"channel": "sms",
"status": "DELIVRD",
"operator": "Etisalat / e&",
"mccmnc": "424-02",
"latencyMs": 2600
}Illustrative payload. Field names and delivery options are in the API reference.
Sample data: timings are illustrative, built from the destination's published median latency. Your console shows the real trace for every message.
Capabilities
Direct SMPP binds across 1,000+ operator connections. Per-route quality scoring chooses the fastest path that respects regulation.
If a primary route degrades, traffic re-pins to a secondary in milliseconds — without re-billing or duplicate delivery.
Long codes, short codes, and shared numbers with inbound webhooks. Keyword routing, opt-out compliance, conversation threading.
Pre-registered alphanumeric senders rotated by region and use case. Approval handled across the MENA regulators in 5–15 business days.
Delivery receipts (DLRs) delivered to your webhook. Tamper-evident logs retained 90 days; enterprise tier extends to 7 years.
Local entities and regulatory teams in UAE, KSA, Egypt, Jordan, Bahrain, Qatar, Lebanon, Oman, Kuwait, Iraq, Morocco, Tunisia, Algeria.
Audit-ready in every market we route — regulator-recognized, continuously certified.
Compliance
Sender IDs, content rules, and data residency are handled by an in-region regulatory team — so you stay compliant in every market you serve, without filing a single PRA yourself.
EU customer data isolated to EU-only routes and storage. DPA standard. Right-to-erasure tooling exposed via API.
BAA availability confirmed during contracting. PHI-safe templates, restricted logging, AES-256 at rest, TLS 1.3 in transit.
Sender-ID registration and content approval across the MENA regulators. See the per-country rulebooks for UAE (TDRA), KSA (CST), Egypt (NTRA), Jordan (TRC) and Lebanon (TRA).
Built against IR.71 (SMS interworking), IR.81 (SMS firewall), IR.82 (anti-spam) — the same test packs operator security teams run during regression.
Every message produces a tamper-evident log entry. 90-day standard retention, 7-year enterprise tier, SIEM export.
Direct where commercially available. BroadNet runs 1,000+ direct operator connections across 200+ countries and uses a direct SMPP bind wherever one is available for your destination. Where it is not, traffic goes over a partner-managed route, and each country page lists every operator with its route status, so you know which path your traffic takes. No grey routes. Every connection is contractually committed traffic, which is why our delivery numbers hold across audit cycles.
Request test access and we reply within one business day. Production traffic to UAE, KSA, Egypt, Lebanon, Bahrain, and Qatar can be live in 3–10 business days, gated by sender ID approval from the relevant regulator. We handle the PRA filings — you do not file paperwork yourself.
Per-country, per-route, with volume tiers from 100K messages a month. UAE list pricing starts around $0.0123/MT, and sustained high volume qualifies for enterprise tiers. AED, EUR, and USD billing supported. No setup fee, no monthly minimum.
Pre-registered alphanumeric senders are rotated by region, use case, and risk class. When a regulator changes rules — like TDRA's 2024 sender ID overhaul — our local compliance team re-registers within the grace window and pushes the new configuration to your account without code changes on your side.
Per-route quality scoring is computed every 60 seconds from operator DLRs. When latency, delivery rate, or pDR drops below threshold, traffic re-pins to the next-best legal route in milliseconds. No duplicate billing, no duplicate delivery — the failover is idempotent on the message ID.
Both. REST is the recommended modern integration; SMPP 3.4 and 5.0 binds are available for high-throughput pipelines and for customers migrating off legacy aggregators. Both interfaces share the same routing, DLRs, and billing — and you can run them simultaneously.
DLRs are pushed to the webhook URL configured on your account, keyed to the message ID the API returned at send time, and the same statuses are available in your delivery reports. Reconcile by message ID and treat the webhook as the fast path.
Dedicated SMPP binds, named technical account manager, 24/7 NOC pager, 99.99% routing SLA, quarterly performance reviews, and a direct Slack/Teams channel with our engineering team. MENA-headquartered enterprises also get on-site quarterly visits from the Dubai HQ team.
Question not here? Ask our engineering team
Pricing
Volume discounts apply from 100K messages a month. Per-country rates published in your dashboard, billed in USD, EUR, or AED. No setup fees.
Explore the platform
A2P SMS is the pillar of BroadNet's messaging stack. Each channel below rides the same 1,000+ direct operator interconnects, sender-ID compliance, and DLRs.
REST plus SMPP 3.4/5.0, delivery webhooks, an official TypeScript SDK and an OpenAPI 3.1 spec on the same direct routes.
Audience segmentation, opt-out handling, and per-country compliance for marketing at 30,000 messages a second per node.
Speed-tuned authentication with SMS-to-Voice fallback and sub-second median delivery.
Verified business messaging as an Official Meta Business Partner — templates, sessions, and rich media.
Verified branded messaging on Android — rich cards, carousels, and read receipts, with automatic SMS fallback.
Comparing vendors? Read our Best A2P SMS provider in 2026 buyer's guide.
No grey routes: a direct operator bind wherever one is commercially available, otherwise a labelled partner-managed route. One API to every channel, on a network built since 2003.
Talk to our team about volume pricing, regional compliance, and a deployment timeline that fits your launch.
Resources
A2P SMS datasheet
Go deeper on the concepts behind this product.