BroadNet
Enterprise onboarding

From route review
to production traffic.

Six published steps, and test credentials come first: we reply within one business day, and your first test message goes out about five minutes after you have them. Request to production in 5–15 business days for most markets; longer where sender-ID approval is gated by regulator timelines.

Request test accessSee support SLA
From request to production

One path to your first message, with the clock on every step.

  1. 01

    Request test access

    Reply within 1 business day

    A messaging engineer replies with your test credentials and books a 30-minute call on your countries, volumes and use case.

  2. 02

    First test message

    About 5 minutes after credentials

    Send a test message to your own verified number with the quickstart code. The delivery receipt comes back to your webhook.

  3. 03

    Integration

    2–5 business days

    Build and test with your test credentials against the same endpoint as the code samples. A BroadNet engineer pairs with you on REST or SMPP.

  4. 04

    Approval

    3–10 business days

    Sender identity, traffic purpose and destination rules are reviewed, and sender IDs are registered with each regulator, in parallel with your integration.

  5. 05

    Production

    Cutover day

    Production access and routes are switched on for your account. Your integration already calls https://api.broadnet.me.

Overall: 5–15 business days from request to production for most markets; longer where a regulator's sender-ID lead time is longer.

How the two fit together: the playbook below is the same path, with an owner and deliverables for each step. Your request and first test message are step 01, commercial setup runs in parallel with integration and approval, and optimization is the monthly work after go-live.

01
Test access and discovery
Reply within 1 business day
02
Technical integration
2-5 business days
03
Commercial setup
3-7 business days
04
Approval and route validation
3-10 business days
05
Go-live
Cutover day
06
Optimization
Monthly
Step 01

Test access and discovery

A telecom engineer replies within one business day with your test credentials and books a 30-minute call on use case, countries, volume, traffic type and compliance needs. Your first test message goes out about five minutes after you have the credentials.

Reply within 1 business day · owned by Solutions engineering

Deliverables

  • Test credentials (sends to your own verified numbers)
  • Use-case summary document
  • Country + operator coverage report
  • Sender ID registration timeline per market
  • Compliance scope (HIPAA / PDPL / GDPR as applicable)
Step 02

Technical integration

Build and test with your test credentials: IP allowlisting, webhook setup, test traffic to your verified numbers over REST or SMPP. Pair with a BroadNet engineer for the first 100 messages.

2-5 business days · owned by Integration engineering

Deliverables

  • Working test integration
  • IP allowlist configured
  • Webhook URL registered
  • Quickstart code samples in your stack
Step 03

Commercial setup

Pricing, contract, SLA and sender ID requirements, in parallel with integration. Per-country pricing is finalized after discovery; the SLA tier is matched to the use case.

3-7 business days · owned by Commercial + Legal

Deliverables

  • Master Services Agreement (MSA) signed
  • Order form with per-country rates
  • Data Processing Agreement (DPA) executed
  • BAA / industry-specific addenda as needed
Step 04

Approval and route validation

Sender identity, traffic purpose and destination rules are reviewed, and sender IDs are registered with each regulator, in parallel from day one. Then destination testing, DLR checks and a latency baseline on the approved routes.

3-10 business days · owned by Solutions engineering + Compliance

Deliverables

  • Sender ID approval status per market
  • Per-country route quality report
  • Latency + delivery-rate baseline
  • Fallback chain configured + tested
Step 05

Go-live

Production access enabled for your account on https://api.broadnet.me, the endpoint your integration already calls. Monitoring on, support escalation paths shared, reporting cadence agreed. Named on-call rotation for the first 7 days post-cutover.

Cutover day · owned by NOC + Customer Success

Deliverables

  • Production access enabled on https://api.broadnet.me
  • Production traffic enabled
  • NOC monitoring active with named on-call
  • Slack / Teams shared channel for ops
  • Reporting cadence (daily / weekly / monthly) set
Step 06

Optimization

Route quality review, delivery analysis, fraud watch, country expansion plan. Quarterly business review with named TAM on enterprise tier.

Monthly · owned by Technical Account Manager

Deliverables

  • Monthly route quality + delivery analysis
  • Fraud + abuse pattern review
  • Cost optimization recommendations
  • Country expansion roadmap

Start at step one,
not at a sales call.

Book a 30-minute discovery with a telecom engineer. We'll review your routes, sender IDs, and regulators before any contract.

Book discovery