# SMS Routing & Least-Cost Routing

- Canonical URL: https://www.broadnet.me/academy/sms-routing-and-least-cost-routing
- Language: en
- Last updated: 2026-07-18
- Publisher: BroadNet (https://www.broadnet.me)
- Markdown version of the page above, generated from the rendered page.

Routing & Quality Intermediate

How messages find a path to the destination network — direct routes, grey routes, least-cost routing, and quality-based failover.

5 lessons 4 min read Standards-based · self-paced

What you'll learn

- What a route is and how a destination is resolved by MCC/MNC
- Direct routes vs grey routes and the quality trade-off
- How least-cost routing works and where it goes wrong
- Quality-based and adaptive routing with DLR feedback
- Why route transparency is the key vendor question

Course outline

1. 01What a route is
2. 02Direct routes vs grey routes
3. 03Least-cost routing (LCR)
4. 04Quality-based and adaptive routing
5. 05Evaluating routing transparency
6. ★Key takeaways

[All courses](https://www.broadnet.me/academy)

Diagram Operator-direct vs multi-hop routing

Operator-direct route Every hop is known and accountable

1. Your application
2. BroadNet platform
3. Operator SMSC
4. Subscriber handset

Multi-hop route Hops can change without notice and receipts can be lost

1. Your application
2. Aggregator
3. Reseller
4. Unknown hop
5. Operator SMSC
6. Subscriber handset

Lesson 01

## What a route is

A route is a path from your platform to the subscriber's home operator. Every mobile network is identified by a Mobile Country Code and Mobile Network Code (MCC/MNC); resolving the destination — including handling ported numbers via MNP lookup — decides which network must terminate the message.

Because no single provider connects directly to every operator on earth, traffic often crosses one or more intermediaries. Each hop adds latency and a point where the message can be filtered, altered, or dropped.

A route therefore has a type and a quality, not just a price. The type describes how the traffic is delivered; the quality is measured by delivery rate, latency, sender-ID preservation, and DLR fidelity.

Lesson 02

## Direct routes vs grey routes

A direct route is an official, contracted connection to the terminating operator that delivers A2P traffic as A2P and pays the proper termination fee. It preserves the sender ID, returns accurate DLRs, and is compliant with the operator's rules.

A grey route delivers A2P traffic through unofficial paths — commonly by dressing it up as person-to-person traffic — to avoid the A2P termination fee. It is cheaper, but the operator's firewall may block it, sender IDs may be overwritten, and delivery is unpredictable.

Grey routes are the reason deliverability can look fine in a demo and collapse in production. A provider that refuses to disclose route type per destination is a warning sign; direct connectivity is what a carrier-grade platform sells.

Lesson 03

## Least-cost routing (LCR)

Least-cost routing selects, for each destination, the cheapest available path that still meets a quality threshold. Providers maintain a table of routes per destination with their costs and observed performance, and the router picks accordingly per message.

Naive LCR that optimises for price alone drifts toward grey routes and low delivery rates. Sound LCR is constrained: it only considers routes above a minimum delivery-rate and latency bar, so cost is minimised within a quality envelope rather than at its expense.

For transactional traffic like OTPs, cost is usually the wrong primary objective — a few cents saved is meaningless against a failed login. Separating transactional and promotional traffic into different routing policies is a core operational practice.

Lesson 04

## Quality-based and adaptive routing

Delivery receipts are the feedback signal that turns static routing into adaptive routing. By scoring each route on live delivery rate, latency, and error mix, a platform can shift traffic away from a degrading path automatically.

Failover is the safety net: when the primary route for a destination degrades or goes down, traffic reroutes to a healthy alternative. Well-built failover is transparent to the sender and fast enough that end users never notice.

This is where reach and redundancy pay off. A platform with many direct connections — BroadNet operates 1,000+ direct operator connections, direct to the operator in 86 countries and reaching 200+ — has more healthy alternatives to fail over to, which is what sustains high delivery rates and a 99.99% uptime posture.

Lesson 05

## Evaluating routing transparency

The single hardest thing to see in a demo is route quality, so make providers disclose it. Ask for route type (direct vs grey) per destination, delivery-rate and latency reporting per country and operator, and a contractual policy against grey routes and SIM-farm termination.

Independent verification matters: test numbers on each target route, third-party deliverability monitors, and DLR-backed reporting keep a provider honest. Numbers that only appear in a sales deck are not evidence.

Finally, confirm how route changes are communicated. Adaptive routing is good; silent, undisclosed rerouting onto cheaper grey paths is not. Transparency is the difference between delegating routing and losing control of it.

Key takeaways

- A route has a type and a quality, not just a price; destinations are resolved by MCC/MNC and MNP.
- Direct routes preserve sender ID and DLRs; grey routes trade compliance and reliability for cost.
- Sound least-cost routing minimises price within a quality envelope — never below it for OTP traffic.
- DLR feedback enables adaptive routing and failover; route transparency is the key vendor question.

Keep going

### Related answers, products & tools

- [What is a grey route?](https://www.broadnet.me/answers/what-is-grey-route-sms)
- [What is route failover?](https://www.broadnet.me/answers/what-is-route-failover)
- [What is HLR lookup?](https://www.broadnet.me/answers/what-is-hlr-lookup)
- [MCC/MNC lookup (free tool)](https://www.broadnet.me/tools/mcc-mnc-lookup)
- [Coverage & operators](https://www.broadnet.me/coverage)

References

- [GSMA · IR.71 SMS interworking](https://www.gsma.com/solutions-and-impact/technologies/networks/)
- [ITU-T E.212 — mobile network identification (MCC/MNC)](https://www.itu.int/rec/T-REC-E.212)

Up next in the curriculum

[Intermediate · Verification OTP & Number Verification How one-time passwords and number verification work — TOTP/HOTP, delivery channels and fallback, autofill conventions, and defending against AIT.](https://www.broadnet.me/academy/otp-and-number-verification) [Intermediate · Channels Omnichannel Messaging Orchestrating SMS, WhatsApp, RCS, voice, and email as one conversation — channel capabilities, the WhatsApp 24-hour window, and fallback design.](https://www.broadnet.me/academy/omnichannel-messaging)

Put it into practice

## Build with what you just learned.

Talk to a real engineer about your use case, or open the developer docs and send a message across the routes this course describes.

[Talk to engineering](https://www.broadnet.me/contact) [Developer docs](https://www.broadnet.me/developers)

Why learn from BroadNet

- Since 2003
- Countries 200+
- Operator links 1,000+