An SMS aggregator is the company that sits between a texting platform and the mobile carriers. It holds the direct connections to AT&T, T-Mobile, Verizon and the rest, so that a business does not have to negotiate with each network separately.
Most businesses never deal with one directly and do not need to. It is worth understanding anyway, because the aggregator behind your platform determines your delivery rates, your throughput, and what happens when messages start disappearing.
What an aggregator actually does
Carriers do not sell messaging access to individual businesses. Building a direct connection to a mobile network means technical integration, commercial terms, compliance obligations and volume commitments that only make sense at scale.
Aggregators solve that by building those connections once and reselling access. They handle four things:
- Carrier connections. Direct links into each network, maintained and monitored.
- Routing. Working out which network a number belongs to and sending the message the right way, including numbers that have been ported between carriers.
- Registration and compliance. Submitting brand and campaign registrations, and enforcing carrier content rules.
- Delivery reporting. Passing back whether a message arrived, failed, or was filtered.
Where the chain actually runs
A business text passes through more hands than most people expect:
- You write a message in a texting platform.
- The platform handles contacts, scheduling, replies and compliance, then hands the message off.
- The aggregator routes it to the right carrier over a direct connection.
- The carrier applies its own filtering, checks your registration, and delivers to the handset.
TextSpot sits at step two. We are the platform, and we work with aggregators underneath, which is the normal arrangement for business texting software. It is also why our rate card lists carrier fees separately at volume: those are set at step four and passed through, not invented by us.
Aggregator, gateway, platform
These three get used interchangeably and they are not the same thing.
An aggregator holds carrier relationships and moves traffic. Its customers are usually other companies, not end businesses.
A gateway is the technical interface that converts a message from one protocol to another so it can enter the carrier network. Some aggregators run their own gateways; the word often refers to the API you send to.
A platform is the software you actually use: contacts, lists, scheduling, two-way conversations, templates, reporting, opt-out handling. It sits on top of the other two.
The practical distinction is what you get for your money. Buying aggregator or gateway access gets you a pipe and an API, and you build everything else. Buying a platform gets you software that already works, at a higher per-message price. Neither is better; they answer different questions.
Tier 1 and Tier 2
Aggregators get described as Tier 1 or Tier 2, and the distinction is about how directly they connect.
Tier 1 aggregators hold direct contracts with the carriers. Fewer intermediaries means better delivery visibility, faster resolution when something is being filtered, and generally higher throughput.
Tier 2 aggregators buy access through someone else. That can be cheaper, and it can be perfectly fine. It also means an extra link in the chain, less direct reporting, and slower answers when delivery problems need escalating to a carrier.
Treat these labels as descriptive rather than certified. There is no independent body awarding tiers, and plenty of companies describe themselves generously.
What actually matters to you
If you are choosing a texting platform rather than an aggregator, the questions that matter are downstream ones:
- Are delivery reports real? “Sent” is not “delivered”. Ask which one the dashboard shows.
- Who handles carrier registration? If the answer is you, budget time for it.
- What happens when messages get filtered? Carriers filter traffic that looks like spam, sometimes wrongly. Ask who chases it and how long it takes.
- Are carrier fees passed through at cost or marked up? Both are legitimate; only one is usually disclosed.
- Is throughput capped? It matters if you send large volumes in short windows.
None of those require knowing your aggregator’s name. They tell you what its quality means for you, which is the part you actually experience.
When you should care directly
Going to an aggregator or gateway yourself makes sense if you are building messaging into your own product, sending at a volume where per-message economics dominate everything else, and you have engineers to build and maintain the layer a platform would otherwise give you.
Short of that, it is a lot of work to arrive at what a platform already does. Our page on whether you actually need an SMS API covers the same decision from the other direction.