BroadNet
Outcome economics

What does one completed verification really cost?

A per-message rate is not what you pay for a sign-in. Resends, Unicode segments, fallback calls and pumped fake requests all land on the bill, while only completed verifications create value. Set your mix and see the spend and the cost per successful verification.

Your verification flow

First channel
Message encoding
Fallback when the first channel fails
10%

Share of requests where the user taps “resend”.

5%

Share of requests generated by SMS pumping bots.

Assumptions (adjust to your data)
95%
90%
85%

Defaults are round planning figures, not BroadNet measurements. Replace them with your own funnel data.

Cost per completed verification
$0.0168
1.37× the headline message rate
Monthly spend
$1,349.48
Completed verifications
80,346
Headline rate per message
$0.0123

Where the money goes

  • First sends$1,168.50
  • Resends$116.85
  • Fallback$64.13
  • Pumped requests$0.00

Blocking pumped requests saves $67.65 a month.

Fallback adds 3,634 completed verifications a month.

Rates used

  • SMS list rate in UAE: $0.0123 per segment
  • WhatsApp authentication list rate: $0.0135 per delivered template message (Meta list; per-country tariffs differ)
  • Voice list rate for Middle East and North Africa: $0.0450 per minute (one 60-second increment assumed)

Indicative list rates, reviewed September 24, 2026. Volume pricing available.

BroadNet OTP can also be billed per successful verification rather than per message. See OTP pricing

Request a quote
How it is calculated
  1. Genuine requests = requests × (1 − fake share). Fake requests cost money only when they are sent.
  2. First-channel sends = genuine requests × (1 + resend rate) × segments.
  3. Undelivered = genuine requests × (1 − delivery rate); these go to the fallback channel when one is set.
  4. Completed = delivered × share of users who enter the code.
  5. Cost per completed verification = total spend ÷ completed verifications.

Questions about OTP cost

Why measure cost per completed verification instead of cost per SMS?

Because you pay for every message sent, but only a completed verification signs a user in. Resends, failed deliveries and fake requests raise the real cost of each sign-in above the per-message rate.

Does a fallback channel make verification cheaper?

Often it raises the spend a little but lowers the cost per completed verification, because users who would have failed now finish. Set your own delivery rates to see which way it goes for your market.

How much does SMS pumping add?

Every pumped request that is sent is paid for and never completes. Blocking those requests before the send removes that cost entirely, which is why the explorer shows the saving separately.