Regional SMS API vendors are easy to find. Many are based in Europe, Latin America, India or Southeast Asia, offer a white label dashboard you can put your logo on, and quote per-message prices that look appealing next to US providers. Some of them are excellent. Others resell routes they don't control, report "delivered" on texts that never arrived, and have never heard of 10DLC.
This post covers what to check before you sign with a niche or regional vendor. The most important question is where your recipients' phones are. If they are on US carriers, the sending rules are set by US carriers, wherever your vendor is based. If they are elsewhere, a good local vendor is often the right pick, and we'll say when that's the case.
Start with where the recipients are, not where the vendor is
A provider's headquarters doesn't decide whether a text gets delivered. The receiving carrier does. That splits the decision in two.
Recipients mostly outside the US. A regional vendor with direct connections to carriers in that country is usually the better fit. Each country has its own rules, such as sender ID registration, template pre-approval and local opt-out rules, and a local vendor will know them better than a US platform. Ready is built around US 10DLC registration, so we're not the natural choice for traffic that terminates abroad.
Recipients mostly on US numbers. Every application-to-person text to a US 10-digit number needs a registered brand and campaign. Carriers filter unregistered traffic, and an overseas vendor sending into the US still has to register you through The Campaign Registry. If they can't explain how, that's your answer. Our 10DLC outside the US explainer covers which rules carry over to Canada and Australia and which don't.
What to check on delivery routes
"Direct routes" is the most overused phrase in this market. These are the questions that show whether the claim holds up:
- Who holds the carrier connection? Ask whether the vendor connects directly or through an aggregator, and how many hops sit between your API call and the handset. Every extra reseller is another margin and another place where delivery receipts can be faked.
- Are delivery receipts real? Grey routes, meaning SIM-box farms and unofficial interconnects, sometimes return a synthetic "delivered" status. Send test texts to phones you control on each major carrier and compare the actual arrivals against the vendor's dashboard.
- What sender types do they support for the US? Alphanumeric sender IDs, which are common in Europe and Asia, don't work for US recipients. You need a registered 10DLC number, a toll-free number or a short code. If the vendor's US offer is "we'll send from a shared pool", expect filtering. Our comparison of 10DLC vs toll-free vs long code vs RCS covers the tradeoffs.
- What throughput will you actually get? For US 10DLC, a fresh standard campaign without vetting typically gets about 1 to 4 segments per second, and T-Mobile caps daily volume by brand trust score, from roughly 2,000 to 200,000 messages per day. These are approximations, because carriers publish no official rate card. A vendor promising hundreds of messages per second on an unvetted 10DLC brand is either wrong or sending on routes you don't want.
What to check on compliance
This is where regional vendors vary most, and where a mistake costs the most. TCPA exposure runs $500 to $1,500 per text, and the sender carries that liability, not the API vendor.
The compliance checklist
- 10DLC registration for each end customer. If you're white labeling, each of your customers needs its own brand and campaign. A vendor that registers everyone under your brand mixes their reputations: one customer's bad list can throttle all the others. Our post on 10DLC for SaaS platforms explains who should be the registered brand.
- STOP handling that propagates. An opt-out on one campaign should block that contact across every campaign on the account. Ask whether that happens automatically or whether you have to build it yourself.
- Quiet hours by recipient area. A vendor in another time zone might schedule by your server clock. TCPA risk depends on the recipient's local time.
- Litigator and DNC scrubbing. This is rarely offered by non-US vendors because it's a US-specific risk.
- An audit trail. You want a record of who sent what, to how many recipients, and when.
The fines and filtering that follow unregistered US sending are covered in 10DLC enforcement and penalties.
What "white label" should mean in practice
Some vendors' white label means a custom logo on a shared account. For a platform reselling SMS, it should mean real isolation:
| Question | Weak answer | What you want |
|---|---|---|
| Numbers | Shared pool | Numbers owned by each customer sub-account |
| Registration | One brand for all customers | A brand and campaign per sub-account |
| Opt-outs | Global list you maintain | Honored across every sub-account automatically |
| Billing | One bill, you split it | Itemized by sub-account, carrier fees separate |
| API | Dashboard only | REST endpoints for sub-accounts, numbers and sends |
Ready works this way. Each customer gets a sub-account with its own numbers and its own 10DLC registration. You can create sub-accounts through the API (POST /v1/sub-accounts), and a send looks like this:
POST https://api.tryready.com/v1/messages with header X-API-Key: <key>, an Idempotency-Key UUID so a retry never double-sends, and body {"to": "+12125550199", "body": "Your order #1042 has shipped.", "consent_attested": true}.
Texts to opted-out and numbers on your Ban list are refused up front and not charged. A text sent during the recipient's quiet hours is held and charged only when it sends if the window opens within 6 hours; otherwise Ready answers 409 QUIET_HOURS_BLOCK and queues nothing. Full reference: docs.tryready.com/api/messages and the API quickstart.
The pricing comparison, done honestly
Regional vendors often quote per message. US carriers bill per segment. A GSM-7 segment holds 160 characters, or 153 per part when a message splits. One emoji, or certain accented characters common in Spanish and Portuguese, switches the whole message to Unicode, which caps each segment at 70 characters (67 per part). A 140-character Spanish reminder with an "á" in it is 3 segments, not 1. Ask any vendor how they count segments before you compare prices.
Example: one customer sub-account, 10,000 segments a month
These numbers are an example with stated assumptions: one brand, one campaign, one number, 10,000 segments sent and received.
- Messaging: 10,000 × $0.0075 = $75, plus 10,000 × $0.0045 = $45 carrier fee
- Registration monthly: $25 for registration + $2 = $27 a month
- Total: $147 a month for the sub-account
- Optional: scrubbing and landline validation, $0.003 per segment each if you switch them on. Both are off by default and not included above.
That's our Standard rate, one flat rate. Twilio lists about $0.0083 per segment and LeadConnector about $0.0083 per message, both lower per segment than our rate. If you have engineers who'll build registration flows, opt-out propagation, quiet-hours logic and per-customer billing on a raw CPaaS, that can be the right call. What our rate covers is the parts above that you'd otherwise build and maintain yourself. Bulk SMS pricing models and what gets hidden goes deeper on how quotes compare once fees are added.
When a US-registered provider is the safer pick
Choose a regional vendor when your recipients are in that region and the vendor can show direct local routes and honest delivery receipts.
Choose a US-registered provider when:
- Most recipients have US numbers
- You resell to many customers and need each one's 10DLC reputation kept separate
- You'd rather not build STOP propagation, quiet hours and scrubbing yourself
- You need registration that a customer can complete in-app. Most approvals take 2 to 7 days, and registration has no setup fee: the first $25 month is charged at submit.
Plenty of platforms do both: a regional vendor for local traffic and a US provider for US numbers, routed by country code in their own code. That's a reasonable architecture, not a sign of indecision.
The practical takeaway
Decide by where recipients are, then test routes with real phones, confirm per-customer registration and opt-out handling, and price everything per segment, including registration. Remember that compliance stays your responsibility whichever vendor you pick. Good tooling reduces risk; it doesn't remove it.
If your traffic is US-bound and you want to see how sub-accounts and registration work, create an account. A card on file is required, and your first 20 one-to-one texts are free, so use them to test delivery before you register.