How to choose an A2P SMS provider
A supplier evaluation that produces evidence: traffic first, route transparency, sender registration, handset testing and a fallback plan.
Choosing an A2P SMS provider starts with your traffic, not a country list. Coverage is an inventory; route transparency, sender registration and handset testing are the product. A good evaluation produces named routes, approval references and test results, not adjectives.
Key facts
- Coverage is an inventory of reachable networks; it does not prove a route is direct.
- Route transparency, sender registration and handset testing are the product.
- A provider that cannot name the route cannot be held to a delivery claim.
- A good evaluation produces evidence: registered strings, approval references and test results.
On this page
Start with your traffic
Write down the destination markets, the monthly volume, the peak rate, the sender types, the reply path and the content categories. That sheet decides the questions. A monthly volume means little without the peak, and a peak means little without the busiest hour. A provider that quotes before it has the sheet is guessing, and a comparison built on guesses compares nothing.
Separate authentication, transactional and promotional traffic. They need different senders, different routes and different content checks. A provider may be strong on one and weak on another. If the sheet mixes them, every answer becomes an average and the weak part disappears.
Weight the sheet. Authentication is the most time-sensitive, promotional is the most filter-sensitive, and transactional sits between. A provider that is strong on promotional volume may be weak on the authentication route you need at login. Say which line matters most before you compare answers.
The RFQ checklist
The ticks stay in this browser view; nothing is stored or sent.
Coverage is an inventory, not a route
Coverage lists the networks a provider can reach. It does not say whether the route is direct, whether the sender is registered on that route, or whether a handset in that market will show the message. Two providers can list the same countries and deliver very differently. Ask for the route under the country, not the country alone.
A direct route is not automatically better. It is easier to name, easier to test and easier to hold to account. An aggregator route can be the right choice for a small market or a short campaign. The provider must tell you which one carries your traffic and what changes when it changes. Record the route per destination, not one route for the region.
A route scorecard
| Item | What you ask | Weak answer | Strong answer |
|---|---|---|---|
| Named route | A country list | The networks, the handset test and the date | |
| Sender registration | A promise that it is handled | The registered string, the approval reference and the renewal owner | |
| Testing | A coverage map | Named handsets in named markets, with results and the content used | |
| Failure handling | A support address | The fallback route, the switch trigger and the notice | |
| Change notice | A status page | Who tells you, how early, and what happens to the sender |
The same scorecard works for a first quote and for an annual review.
Sender registration and testing
Sender registration is part of the product. A provider that submits the application, holds the approval and tells you the registered string is easier to hold to account than one that forwards your documents. Ask who owns the registration, what evidence you will receive and what happens if the sender is rejected.
Testing is the other half. A route test on named handsets in the markets you will launch, with the content you will send, proves more than a coverage map. The route testing guide explains what a test proves and what it does not. The SMS rules tool lists the market rules we hold.
Ask what the test covers before you accept the word "tested". A provider that tests one handset and calls the market covered is describing a sample. A provider that names the handsets, the networks and the date is telling you how to repeat the result. A short list with evidence beats a long list with adjectives.
Good answers and bad answers
| Question | Weak answer | Strong answer |
|---|---|---|
| Which networks carry the traffic? | Many networks | These named networks, direct or aggregator, tested on this date |
| Is the sender registered? | Yes, it is handled | This string, this approval reference, this renewal owner |
| Can you test before launch? | We have coverage | We will test these handsets in these markets with this content |
| What if a route fails? | We monitor it | This fallback route, this trigger, this notice |
| What does the receipt mean? | Delivered means delivered | This network state, these codes, this reconciliation path |
Record the answer and the date. An answer without a date is a memory.
Onboarding and the RFQ
Ask for the onboarding sequence: who collects the documents, who submits the sender, who tests, who turns on production and who answers when a route fails. Put those names and dates in the RFQ. A provider that answers with a process is easier to evaluate than one that answers with adjectives.
Ask what happens after launch: how route changes are announced, how a sender rejection is handled and how a failure is escalated. Ask for the receipt format and the error-code list, so your team can debug without a call. The A2P SMS product page describes our service; use this page to compare any provider, including us.
Score every answer on the same sheet and keep the evidence. A provider that scores well on route transparency and testing but poorly on change notice carries a different risk from one that scores the reverse. The point of the exercise is to see the trade-off, not to produce a single number.
Check what you learned
-
A provider lists a long country list. What does that tell you?
That it can reach many networks. It says nothing about direct routes, sender registration or handset delivery in your markets.
-
Which answer is stronger: a coverage map or a test on named handsets?
The test, because it names the handset, the market, the content and the date. A coverage map is an inventory.
-
Why separate authentication, transactional and promotional traffic in the RFQ?
They need different senders, routes and content checks. A single average hides the part that will fail.
Answers are revealed on request. Nothing is scored, stored or sent.
FAQ
How many providers should we compare?
Is a direct route always better?
What should a route test include?
Do we need a sender in every market?
What if the provider will not name the route?
Terms you'll meet
Related
- Connecting over SMPP and HTTP
Take a test route to production without breaking binds, windows or receipts: bind, throughput, keep-alive, encoding, callbacks and failure handling.
- Global A2P sender-ID playbook
How sender IDs work across markets: alphanumeric, numeric and short-code paths, registration expectations and country examples.
- A2P SMS
Application-to-person SMS is traffic an application sends to a handset, such as a verification code or a transaction alert, via a registered sender.
Related products
Put this to work
Tell us the traffic, the destination and the measurement you need; we reply with the next step.