PRICING

A meter that follows the message.

Estimate by country, sender type and volume. Keep route choices visible as your traffic grows.

Pricing that follows the route a message actually takes. Estimate with the variables that matter, compare scenarios before launch and keep cost decisions visible as volume grows.

ESTIMATE / MONTHLY ROUTE$4,820illustrative scenario / US / OTP
01 / BUILD A SCENARIO

Four inputs shape the number.

01MarketUnited States
02Sender typeA2P 10DLC
03Monthly volume1,000,000
04Recovery rate4.5%
02 / ROUTE BREAKDOWN

Compare the path behind the price.

SCENARIO SAVED / AUG 2026
ROUTEDELIVEREDLATENCYMONTHLY
Start with destination reality.01 / CHOOSE A MARKET
98.9%0.7–1.2s$5,180
Model the traffic you actually expect.02 / SET VOLUME
99.2%0.8–1.8s$4,820
See the tradeoff, not just the total.03 / COMPARE ROUTES
97.6%1.4–2.6s$4,240
03 / SCENARIO PLANNING

Budget for the traffic you will actually operate.

01

Build a baseline

Choose markets, message classes, sender types and the monthly volume that represents normal demand.

ImpactBASELINE
02

Stress the scenario

Add peak periods, resend rates and fallback assumptions to see the operating range rather than one optimistic number.

ImpactPEAK +18%
03

Compare the route

Review cost alongside delivery evidence, registration work and the risk of a route change later.

ImpactRECOVERY +4.5%
04

Commit with a record

Save the assumptions, owner and date behind the estimate so finance, product and engineering share the same baseline.

ImpactDECISION READY
04 / COST CONTROLS

Keep the estimate honest as volume moves.

Track assumptions, delivered cost and route variance in the same operating view.

Market estimator

Estimate by country, sender type, carrier path and message class.

Volume bands

Compare baseline, growth and peak traffic without rebuilding the model.

Delivered cost

Separate attempted sends, retries and successful delivery in the scenario.

Route tradeoffs

See latency, acceptance and registration work alongside price.

Assumption history

Keep a dated record of inputs behind a budget or launch decision.

Usage visibility

Track actual traffic against the estimate and investigate variance by route.

05 / PRICING QUESTIONS

A number is useful when its assumptions are visible.

What drives message pricing?

Destination market, sender type, carrier route, volume, retries and any required registration work are the main variables.

Are retries included in an estimate?

They can be. Add a resend or failure assumption to model attempted, recovered and delivered traffic separately.

Can we save an estimate for finance?

Yes. Save the assumptions, scenario owner and date so the estimate can be reviewed when market or volume conditions change.

Will a cheaper route always be selected?

No. Route selection can balance price with sender readiness, acceptance, latency, policy and the business value of the message.

06 / NEXT ESTIMATE

Build a route budget your team can defend.

Talk through your scenario