Toll-Free SMS vs. A2P 10DLC: Throughput, Approval & Use Cases
Toll-free SMS is usually the simpler national identity; A2P 10DLC is the local-number option with campaign- and carrier-based capacity. Compare registration, throughput, queue time, daily caps, and the use cases each sender handles best.
Figures and official documentation checked July 10, 2026. Throughput, fees, review queues, and carrier policies change. MPS means message segments per second unless noted otherwise.
Quick answer
The short answer
Choose toll-free SMS when one recognizable national number should handle calls and texts. Choose A2P 10DLC when local identity, local conversations, or a registered US local number matters. Neither sender bypasses verification or consent.
Toll-free vs. A2P 10DLC at a glance
| Factor | Toll-free SMS | A2P 10DLC |
|---|---|---|
| Number identity | 800, 888, 877, 866, 855, 844, or 833 | Local US 10-digit number |
| Registration | Toll-free verification for the number and use case | Business profile, brand, campaign, and assigned numbers |
| Common provider starting rate | 3 MPS at Twilio, AWS, and Bandwidth[2][10][14] | Often 1 MPS until registration and/or a rate increase is applied[11][14] |
| Potential throughput | Twilio advertises 150+ MPS on high-throughput toll-free[2] | Up to 75 MPS per major carrier in high-score standard campaign examples[1] |
| Capacity model | Usually number- and account-based | Campaign, brand, carrier, and provider limits |
| Best identity | National business or support line | Local business, branch, agent, or conversation |
MPS counts segments, not conversations
SMS throughput is normally measured in message segments. A GSM-7 message fits up to 160 characters in one segment; concatenated messages generally fit 153 characters per segment. Unicode can reduce that to 70 characters for one segment or about 67 per concatenated segment. AWS likewise defines MPS as Message Parts per Second.[10]
Published toll-free throughput by provider
Three MPS is a common baseline, not a universal toll-free ceiling. Provider products and account controls can create very different practical rates.
| Provider | Published SMS rate | Important qualifier |
|---|---|---|
| Twilio | 3 MPS to start; 150+ MPS advertised | Paid high-throughput launch tiers began at 25 MPS[2][3] |
| AWS | 3 SMS MPS; 3 MMS MPS | AWS recommends 10DLC or short code above 3 MPS[10] |
| Bandwidth | 3 SMS MPS; 1 MMS MPS by default | 15-minute default queue; up to four hours[14] |
| Telnyx | 20 MPS per toll-free sender by default | 50 MPS default account SMS ceiling; sender selector lists 3–150 MPS[7][8] |
How 10DLC capacity changes by carrier
There is no single nationwide 10DLC speed limit. AT&T commonly applies campaign-level segments per minute, T-Mobile applies a daily brand limit, and Verizon emphasizes filtering rather than publishing a comparable public carrier table. Providers can impose an additional account or sender ceiling.[6][15]
AT&T standard campaign tiers
| Brand score / campaign | SMS segments/minute | Approx. MPS |
|---|---|---|
| 75–100 | 4,500 | 75 MPS |
| 50–74 | 2,400 | 40 MPS |
| 1–49 | 240 | 4 MPS |
| Low Volume Mixed | 75 | 1.25 MPS |
| Sole Proprietor | 15 | 0.25 MPS |
Sources: Telnyx and Vonage carrier-throughput documentation.[6][15]
T-Mobile daily brand limits
| Brand score / type | Published daily cap | Scope |
|---|---|---|
| 75–100 | 200,000/day | Shared across campaigns under the brand |
| 50–74 | 40,000/day | Shared across campaigns under the brand |
| 25–49 | 10,000/day | Shared across campaigns under the brand |
| 1–24 | 2,000/day | Shared across campaigns under the brand |
| Sole Proprietor | 1,000/day | Shared across campaigns under the brand |
Published provider interpretation of T-Mobile limits; special business reviews and eligible special-use campaigns can differ.[6][11]
Carrier eligibility is not always your starting API rate
AWS starts an associated 10DLC number at 1 MPS and requires a separate sending-rate increase request; vetting and campaign approval do not automatically raise it. Bandwidth also publishes a 1 MPS default for local A2P traffic. Your provider or account ceiling can therefore be lower than the campaign's carrier eligibility.[11][14]
Estimate your queue time
SMS throughput calculator
Estimate how long your provider needs to dequeue a send. This is not an estimate of carrier or handset delivery time.
Formula: recipients × segments per message ÷ MPS. Queues, daily caps, account limits, filtering, retries, and carrier distribution can extend real delivery time.
| Throughput | 10,000 segments | 100,000 segments |
|---|---|---|
| 1 MPS | 2 hr 46 min 40 sec | 27 hr 46 min 40 sec |
| 3 MPS | 55 min 34 sec | 9 hr 15 min 34 sec |
| 4 MPS | 41 min 40 sec | 6 hr 56 min 40 sec |
| 20 MPS | 8 min 20 sec | 1 hr 23 min 20 sec |
| 40 MPS | 4 min 10 sec | 41 min 40 sec |
| 75 MPS | 2 min 14 sec | 22 min 14 sec |
| 150 MPS | 1 min 7 sec | 11 min 7 sec |
Approval cycles: plan for the queue, not the form
Purchasing a number or completing a form is not approval. Review time varies with provider queues, business verification, use case, consent evidence, and whether the reviewer requests corrections.
| Official documentation | Toll-free | A2P 10DLC |
|---|---|---|
| Twilio | Verification required before US/Canada messaging; no guaranteed duration in the onboarding guide[5] | About 15 minutes to complete the application; current help pages cite roughly 5–15 days for campaign review[4][1] |
| AWS | Up to 15 business days[12] | US brand and vetting steps: 1–2 business days each; campaign: up to 4 weeks; number request: up to 10 days[11] |
| Telnyx | Typically 1–2 weeks, depending on queue and completeness[9] | Provider selector describes 2–3 business days for provisioning; review and vetting can add time[8] |
Practical planning range: allow roughly 1–3 weeks for toll-free and 1–4+ weeks for the complete 10DLC path, then add time for corrections.
When toll-free is the better fit
Use toll-free when
- Customers already recognize your national support number.
- One identity should handle both calls and texts.
- A local area code is not important to the experience.
- You want simpler, number-level capacity planning.
- A central brand sends alerts, support, or account messages.
Avoid choosing it because
- You assume the number can send before verification.
- Local branches or representatives need familiar area codes.
- You plan to buy many numbers to evade throughput limits.
- You need extreme burst volume better suited to a short code.
When A2P 10DLC is the better fit
Use 10DLC when
- A local area code supports trust or recognition.
- Offices, franchises, or agents need local conversations.
- You send appointments, delivery updates, care, or account alerts.
- Your use case can be clearly registered and documented.
- You need a campaign capacity tier above a basic 3 MPS sender.
Avoid choosing it because
- You need to launch tomorrow without registration.
- You cannot prove how recipients consent.
- You expect every number to multiply campaign throughput.
- You need one national identity more than local presence.
Choosing A2P 10DLC?
Before registration, check the campaign description, sample messages, opt-in flow, policy URLs, and cross-field consistency that can trigger a rejection. A2PCheck provides independent readiness guidance; the provider, TCR, and carriers still make the final decision.
Run a free campaign pre-scanOfficial sources
Provider defaults are shown as provider-specific examples, not universal carrier guarantees. All sources below were reviewed July 10, 2026.
- [1]Twilio — Message throughput and Trust Scores for A2P 10DLC
- [2]Twilio — Toll-free numbers and high-throughput toll-free
- [3]Twilio — High Throughput Toll-Free SMS launch
- [4]Twilio — A2P 10DLC registration application quickstart
- [5]Twilio — Toll-free verification console onboarding guide
- [6]Telnyx — 10DLC rate limits and throughput
- [7]Telnyx — SMS messaging rate limits
- [8]Telnyx — Choosing a sender type
- [9]Telnyx — Toll-free verification
- [10]AWS — Message Parts per Second limits
- [11]AWS — United States 10DLC registration
- [12]AWS — United States toll-free number registration
- [13]AWS — Choosing an origination identity
- [14]Bandwidth — Breaking down messaging rate limits
- [15]Vonage — 10DLC throughput limits
Frequently asked questions
Is toll-free SMS considered A2P messaging?
Yes. Toll-free numbers can carry application-to-person traffic. The precise comparison is toll-free SMS versus A2P 10DLC, which uses registered US local 10-digit numbers.
Which is approved faster: toll-free or A2P 10DLC?
Neither is universally faster. AWS says toll-free registration can take up to 15 business days. Twilio currently cites roughly 5–15 days for 10DLC campaign review across different help pages, while AWS warns that some 10DLC registration steps can take several weeks. Corrections extend either timeline.
Which has higher throughput: toll-free or 10DLC?
It depends on the provider and registration tier. Toll-free commonly starts at 3 message segments per second, while Twilio advertises paid high-throughput toll-free above 150 MPS. A well-vetted standard 10DLC campaign can be eligible for 75 MPS per major carrier, but low-volume and sole-proprietor campaigns can be much lower and T-Mobile also applies daily brand caps.
Does buying more 10DLC numbers increase throughput?
Not necessarily. 10DLC throughput is commonly assigned at the campaign or brand level and shared by its numbers. Buying or rotating numbers to evade limits can look like snowshoeing and increase filtering risk.
Can toll-free and 10DLC numbers receive replies and calls?
Both can support two-way SMS, MMS, and voice when those capabilities are enabled by the provider. Confirm the capabilities of the specific number before purchasing it.
Does verification replace SMS consent?
No. Registration identifies the sender and approved use case. It does not replace documented consent, accurate message samples, STOP and HELP handling, privacy disclosures, or other legal and carrier requirements.