How wholesale SMS routing works, end to end

An application-to-person message looks instantaneous from the outside: a bank sends a code, a phone buzzes. Underneath, the message has crossed several organisations, each of which could have refused it, altered it, or delayed it. Understanding that chain is what separates a messaging partnership that can be reasoned about from one that produces mysterious failures nobody can explain.

The chain, step by step

It starts with the business that wants to send — a bank, a retailer, a health service. That business connects to an aggregator, which offers an interface and takes responsibility for getting the message onward. The aggregator hands the message to a wholesale partner, or to several, each of which has arrangements with the operators that actually own the subscribers. The last operator in the chain delivers to the handset. Every hop is a commercial relationship as much as a technical one, and each one keeps its own record of what happened.

• →The sender decides the content, the sender identity, and how urgent the message is.
• →The aggregator validates the request, applies the sender's rules, and chooses where to send it next.
• →The wholesale partner selects a path towards the destination operator and passes the message on.
• →The destination operator applies its own filtering and delivers to the subscriber, or does not.

Why the route is chosen, not fixed

Routing is also where the sender's intent has to be preserved. A message written for a customer who is waiting for it has different needs from one sent to a list, and the decisions taken here are what carry that difference forward. For any given destination there is usually more than one way to reach it, and the choice is not only about cost. Routes differ in whether the sender identity survives intact, whether long messages are reassembled correctly, whether delivery receipts come back and how honest they are, and how the destination operator treats the traffic. A path that is cheaper on paper can cost far more in retries, support time and abandoned transactions. This is why serious messaging partners talk about routes in terms of behaviour rather than price alone, and why a route that is right for marketing may be entirely wrong for authentication.

Delivery receipts and what they are worth

The receipt that comes back saying a message was delivered is generated somewhere in that chain, and where it was generated determines what it means. A receipt produced by the operator that actually reached the handset is meaningful. A receipt produced further upstream, by a party that has merely passed the message on, tells you only that the message left. Both look identical in an interface. When delivery figures look implausibly good, this is usually the reason, and the only way to know is to ask where the receipt comes from and to compare it against something the sender can observe independently — a code being entered, a link being followed.

One consequence is worth stating plainly: the sender identity a business chooses is not guaranteed to survive the journey. Some destinations require it to be registered in advance, some rewrite it, and some accept it as sent. Which of the three applies is a property of the destination and the route, not of the message, and it is the sort of thing worth confirming before a campaign rather than after recipients start asking who wrote to them. None of this makes messaging complicated to use. It does mean that a wholesale partner is worth choosing on the questions they are willing to answer about their routes rather than on the number at the bottom of a rate sheet. If you are evaluating routes for a specific use case, tell us what the messages are for and what happens when one does not arrive. That shapes the answer far more than volume does.