Critical messages delivered.
Operator networks protected.

Per message, per destination operator — the rate depends on the country, the operator and the route it takes. We publish reference rates by market and a calculator rather than quoting only on request, volume tiers apply automatically above 100K a month, and there is no platform fee.

Most enterprises go from request to production in 5–15 business days, on a five-step path: we reply within one business day with test credentials, your first test message goes out about five minutes after you have them, integration takes 2–5 business days while approval (sender identity, traffic purpose and sender-ID registration) runs in parallel in 3–10, and then production is switched on. Markets with longer regulator timelines take longer. Our six-step onboarding playbook is the same path with an owner and deliverables for each step, plus commercial setup in parallel and monthly optimization after go-live.

Message metadata and delivery records are retained under a documented retention policy, and regional deployments are available for customers with data-residency obligations — including GDPR in Europe and PDPL in Saudi Arabia and the UAE. Message content is not retained beyond what delivery and receipt reconciliation require. The specifics are contractual and covered in the DPA, which we will share before signature rather than after.

A 99.99% platform availability SLA, with service credits and escalation paths written into the contract. When a route misbehaves you reach a named telecom engineer: a P1 incident gets a response within 15 minutes, 24/7, and our engineers work in the region, on your time zone. Traffic runs across redundant operator connections, so one route degrading does not become your outage: it re-routes, and the delivery monitoring shows you it happened.

Exactly like everyone else's. BroadNet's own enterprise traffic reaches subscribers through the same firewall and the same rules as every other sender, with no vendor exemption. The operator's teams own the ruleset: changes are version-controlled and need a second approver, and false-positive whitelists are operator-controlled. Every decision is logged with the rule that fired, so a dispute about BroadNet traffic is settled against the same records as any other.

Either. Enterprises typically start with the REST API or SMPP for messaging traffic. Operators deploy our firewall and registry products inside their networks. Many customers use both layers.

SMS pumping, also called artificially inflated traffic, is fraud where a party drives one-time-passcode requests to numbers on routes they profit from. The messages are real and billable; the users are not. We score every message at nine checkpoints, watch for the destination-range and velocity patterns that distinguish pumping from genuine signups, and can block or challenge before the message is submitted — which is the only point at which it is still free to stop.