Executive Summary
Choosing between A2P 10DLC and toll-free SMS is one of the first architectural decisions for any US commercial texting program. Both paths can deliver application-to-person (A2P) messages to consumers, but they use different number identities, registration systems, fee structures, and operational tradeoffs. 10DLC ties traffic to a registered Brand and Campaign through The Campaign Registry (TCR) ecosystem. Toll-free messaging uses a national number that must pass toll-free verification through your communications service provider (CSP). Neither path replaces documented consent under TCPA rules, and neither publishes a single universal messages-per-second (MPS) guarantee. This guide compares registration, identity, fees, throughput caveats, consent, and when to run both—so compliance, marketing ops, and engineering can pick a path with evidence rather than folklore.
Short answer: Use A2P 10DLC when you need a US local 10-digit number with a registered Brand and Campaign. Use toll-free SMS (TFN) when you want one national identity (800/888/etc.) verified for messaging. Use both when local locations and a national support line serve different journeys. Registration does not create consent, and throughput depends on your CSP and carriers—not a blog’s “average MPS.”
Who This Is For / Who It Is Not For
Who this is for
- US businesses choosing a primary SMS sender type for customer care, notifications, reminders, or marketing
- Multi-location brands deciding whether local 10DLC numbers or one national TFN fits better
- Compliance, legal-ops, and marketing ops teams documenting registration and consent side by side
- Product and engineering leads planning CSP onboarding (Twilio, Bandwidth, Telnyx, or others)
Who this is not for
- Teams sending only person-to-person chat from consumer handsets (not A2P platform traffic)
- Pure voice-only programs with no SMS/MMS plans
- Non-US destination messaging (local country rules and sender types differ)
- Anyone looking for a guaranteed MPS figure or a fixed industry fee schedule—those do not exist as universals
Definitions
| Term | Meaning |
|---|---|
| A2P | Application-to-person messaging: traffic from a platform/application to a consumer handset |
| 10DLC | 10-digit long code; a US local phone number used for registered A2P SMS/MMS |
| TFN / Toll-free SMS | Messaging over a NANP toll-free number (800, 888, 877, 866, 855, 844, 833) |
| Brand | Who is sending; business identity registered for 10DLC (often via TCR through a CSP) |
| Campaign | What you send: use case, samples, opt-in/out, HELP, and related compliance details |
| TCR | The Campaign Registry; industry registry used in the 10DLC Brand/Campaign path |
| CSP | Communications service provider / messaging platform that submits registration |
| MPS | Messages (or segments) per second; capacity figure that varies by account and path |
| Trust Score | Vetting outcome that can influence 10DLC throughput eligibility (provider/carrier dependent) |
| Snowshoeing | Spreading traffic across many numbers to evade limits or filters; high filtering risk |
What Is A2P 10DLC?
10DLC means a 10-digit long code: a standard US local phone number used for application-to-person messaging. US carriers treat SMS/MMS sent from messaging platforms over these numbers as A2P traffic, not person-to-person chat.
According to Twilio’s A2P 10DLC overview, anyone sending SMS/MMS over a 10DLC number from an application to the US must register. Registration is built around two pieces:
- Brand — who is sending (business identity, tax ID where required, contact details).
- Campaign — what you send, how people opt in/out, sample messages, and related compliance details.
Brand types commonly discussed in Twilio’s docs include Sole Proprietor, Low-Volume Standard, and Standard. Campaign use cases range from Customer Care and Account Notifications to Marketing and Mixed. Toll-free and short codes are not part of the A2P 10DLC system; they are separate sender paths.
Registration exists because local long codes were originally designed for person-to-person chat. As platforms scaled commercial traffic on those routes, carriers introduced A2P 10DLC to identify senders, require consent practices, and reduce spam. Registered traffic generally receives better filtering treatment and higher eligible throughput than unregistered traffic—subject to your CSP’s enforcement and carrier rules.
For a broader primer, see 10DLC 101 and the step-by-step How to register with TCR.
What Is Toll-Free SMS (TFN)?
Toll-free SMS uses a toll-free number for texting as well as voice. The number presents a national brand identity rather than a local area code. NANP toll-free prefixes include 800, 888, 877, 866, 855, 844, and 833.
Registration for toll-free messaging is typically number- and use-case verification through your CSP—not TCR’s Brand + Campaign model. Twilio’s toll-free verification API docs explain that to use a NANP toll-free number for messaging to the US and Canada, organizations must verify how they plan to send texts. Exact forms, review queues, required URLs, and timelines vary by provider.
Bandwidth notes that toll-free verification is essentially free on their platform while 10DLC registration carries one-time and monthly fees—provider-specific, not an industry-wide law. Bandwidth also highlights handset-level delivery receipts on toll-free versus carrier-level receipts on 10DLC in their comparison guidance (Bandwidth: Toll-free SMS or 10DLC). Treat delivery-receipt behavior as provider/channel documentation and confirm on your account.
Unverified or restricted toll-free numbers face heavy filtering or blocking. Pending verification is not a license to “send anyway.” Plan to complete verification before production traffic.
Registration Paths Compared
| Factor | A2P 10DLC | Toll-free SMS |
|---|---|---|
| Number identity | Local US 10-digit number | National toll-free number |
| Registration model | Brand + Campaign (via TCR / CSP tools) | Toll-free verification for the number and use case |
| Who reviews | CSP submission path into TCR / carrier ecosystem | CSP and carrier / aggregator toll-free verification |
| Typical business fit | Local presence, branches, local conversations | Central support or national brand line |
| Fee shape (examples) | Brand + campaign vetting + monthly campaign fees (CSP-quoted) | Often free verification; number rental still applies |
| Consent still required | Yes | Yes |
10DLC path (high level)
- Collect business information (legal name, tax ID for Standard/Low-Volume brands, website URL, authorized representative).
- Register a Brand.
- Register one or more Campaigns with use case, message samples, opt-in description, and policy URLs as required.
- Assign your 10DLC number(s) to the approved Campaign / Messaging Service.
Twilio’s direct onboarding materials note that campaign vetting can take on the order of two to three weeks in some flows and is not an exact SLA. TCR itself does not approve campaigns in the same way CSPs and upstream partners do—approval timing varies by use case and CSP (Campaign Registry resources).
Toll-free path (high level)
- Provision a toll-free number with voice/SMS capability enabled.
- Submit toll-free verification with business details, messaging use case, samples, opt-in evidence, and (as required by your CSP) Privacy Policy and Terms URLs.
- Wait for approval before relying on US/Canada messaging.
Twilio Help Center guidance has emphasized that missing Privacy Policy or Terms links can cause rejection on new toll-free verification submissions when those fields are required—confirm current field requirements with your CSP before filing.
Neither process is “fill a form and send tomorrow.” Plan for review time and possible remediation if reviewers request fixes.
Fees and What “Free Verification” Actually Means
Fees are provider-published and changeable. Never treat one CSP’s table as a universal industry price.
Illustrative patterns (always get your CSP’s current quote):
- 10DLC: One-time Brand registration, campaign review/vetting fees, and recurring monthly campaign fees that vary by use case and Brand type. Secondary vetting may add cost for Standard Brands on some platforms.
- Toll-free: Verification is often described as free; you still pay for the number and per-message/segment rates. High-throughput toll-free tiers, when offered, may carry additional commercial terms.
Bandwidth’s public comparison states that acquiring a toll-free number can cost more than a local 10DLC number, while TFV is essentially free and 10DLC has ongoing campaign fees. Twilio publishes Brand-type fee bands on its product and help pages—confirm live pricing in your console rather than copying a blog snapshot.
What free verification does not mean
- Free number rental
- Free message segments
- Exemption from consent, STOP/HELP, or content rules
- Unlimited MPS
Related reading: 10DLC pricing and registration fees (draft) and your CSP’s fee schedule.
Throughput and Daily Caps (Carrier and Provider Caveats)
There is no single nationwide MPS that applies to every toll-free number or every 10DLC Campaign.
- Toll-free: Several providers publish a common starting rate around 3 message segments per second (MPS) as a baseline example. Higher tiers exist as paid or account-specific products. Treat these as provider documentation, not universal carrier law.
- 10DLC: Capacity often depends on Brand type, Trust Score / vetting, Campaign use case, and carrier. AT&T commonly discusses campaign-level segments-per-minute tiers; T-Mobile commonly discusses daily brand caps; Verizon emphasizes filtering more than a public MPS table. Your CSP may also cap you below carrier eligibility.
Do not invent universal MPS numbers. Ask your CSP for the limits that apply to your Brand, Campaign, and account. Buying extra 10DLC numbers does not reliably multiply campaign throughput; capacity is often shared at the campaign or brand level. Rotating numbers to evade limits can look like snowshoeing and increase filtering risk.
For a structured comparison with attributed provider figures, see Toll-Free vs 10DLC on A2PCheck—and still verify against your CSP’s current docs.
Consent and Opt-In Proof on Both Channels
Registration identifies the sender and the approved use case. It does not replace documented consumer consent.
Under FCC TCPA rules in 47 CFR § 64.1200, marketing and autodialed texts generally require prior express written consent. Transactional or informational messages may have different consent standards depending on content and context—do not assume registration alone is enough. Keep clear records of how each person opted in, what they agreed to receive, and how they can STOP.
Carrier filtering and CSP Acceptable Use Policies still apply after approval. A verified toll-free number or an approved 10DLC Campaign can still be filtered if content, frequency, or consent practices look noncompliant. Bandwidth’s toll-free materials and CTIA Messaging Principles both emphasize consent/opt-in evidence; mixed marketing and transactional use typically needs clear, separate disclosure and consent design.
Practical consent checklist:
- Capture the language the consumer saw at opt-in
- Store timestamp, source (web form, verbal, paper, keyword), and phone number
- Honor STOP and HELP promptly and consistently
- Align sample messages with the Campaign or TFV use case you filed
- Disclose message frequency and “Msg & data rates may apply” where appropriate
See also: How to document verbal consent for SMS, SMS double opt-in, and Message frequency disclosure.
When to Choose 10DLC, Toll-Free, or Both
Choose 10DLC when
- A local area code builds trust (local shop, clinic, branch, franchise location)
- You need multiple localized numbers for agents or offices under a registered Brand (subject to Campaign and Brand rules)
- Your use case maps cleanly to a Campaign type (Customer Care, Account Notifications, Delivery, Marketing, Mixed)
- You are willing to complete Brand + Campaign documentation, including website and opt-in evidence when required
Avoid choosing 10DLC solely because you need to “launch tomorrow” without registration. Unregistered US-bound 10DLC traffic is blocked on major CSP platforms that enforce full registration (see Twilio error 30034 and related blocking changelogs).
Choose toll-free when
- Customers already know your national support number
- One identity should handle calls and texts
- Local area code is not important to the experience
- You prefer number-level verification rather than TCR Brand + Campaign complexity (still not “no compliance work”)
- Handset-level delivery confirmation matters for your operations (per provider documentation such as Bandwidth’s)
Avoid choosing toll-free because you assume you can send before verification, or because you think consent rules somehow do not apply.
When both make sense
Large enterprises with local affiliates often run:
- Toll-free for national support, OTP fallback, or brand-wide alerts
- 10DLC for location-specific appointment, delivery, or sales conversations
Each number and use case must follow its own registration path and consent rules. Do not share one opt-in for unrelated programs without clear disclosure.
Short codes (brief context)
Short codes remain a third path for high-volume or specialized programs. They involve a separate leasing and provisioning process, typically higher cost, and different approval workflows. If volume or brand requirements outgrow both toll-free and 10DLC, ask your CSP whether a short code is appropriate.
Decision Framework: Six Steps Before You Commit
- Identity: Local trust → lean 10DLC. National support line → lean toll-free.
- Registration appetite: Can you supply EIN (or equivalent), website, privacy/terms, and sample messages for TCR? If not, fix that first—or evaluate toll-free verification readiness instead.
- Use case clarity: Marketing vs transactional vs mixed. Misaligned samples are a common rejection cause for both paths.
- Consent: Document prior express written consent for marketing texts. Registration does not create consent.
- Volume: Ask your CSP for your MPS / daily caps. Do not plan capacity from a competitor’s blog post.
- Budget: Registration and monthly Campaign fees differ by Brand type and use case; CSPs and carriers mark up and change fees—get a quote from your provider.
Optional seventh step: if you need both local and national journeys, map consent separately per program and document which number consumers will see.
Risk and Failure Modes
| Risk | Why it happens | Mitigation |
|---|---|---|
| Unregistered 10DLC blocked | Sending before Brand/Campaign approval | Complete registration; monitor CSP error codes (e.g., Twilio 30034) |
| TFN filtered while pending | Treating “submitted” as “approved” | Wait for Verified status; keep volume off until approved |
| Consent gap | Assuming registration = permission | Maintain opt-in evidence trail; align samples |
| Sample mismatch | Copying another brand’s messages | Write samples that match your Brand and use case |
| Website / privacy rejection | Parked, login-gated, or missing SMS disclosures | Fix public pages before resubmit (9108 guide) |
| Throughput surprise | Planning from a blog’s MPS | Confirm account limits with CSP |
| Snowshoeing | Buying many numbers to evade caps | Request legitimate capacity; keep numbers mapped to approved campaigns |
| Mixed use without disclosure | Marketing on a care campaign | Separate campaigns or obtain clear mixed-use consent |
Implementation Checklist
| Step | Owner | Artifact |
|---|---|---|
| Choose primary sender type (10DLC, TFN, or both) | Product + Compliance | Decision memo |
| Confirm CSP fee schedule and timelines | Finance + Ops | Quote / rate card |
| Collect Brand/business identity docs | Legal-ops | EIN, address, authorized rep |
| Publish privacy + SMS terms (public HTTPS) | Marketing / Web | Live URLs |
| Draft sample messages + opt-in description | Compliance + Marketing | Campaign packet |
| Capture consent storage design | Engineering | Data schema + retention policy |
| Submit Brand + Campaign or TFV | Ops | Submission IDs / statuses |
| Map numbers to approved use case | Engineering | Messaging Service config |
| Test STOP/HELP and quiet hours | QA | Test log |
| Monitor filtering and error codes | Ops | Dashboard + alert runbook |
If you are stuck on TCR packaging (samples, opt-in language, rejection codes), diagnostic tools on MyTCRPlus Tools can help you check consistency before you resubmit—without replacing your CSP’s official registration flow or promising approval rates.
Common Mistakes
- Treating registration as consent. They are separate obligations.
- Assuming toll-free is “easier compliance.” Verification still reviews use case and practices; TCPA still applies.
- Copying another brand’s sample messages. Samples must match your Brand and Campaign description.
- Ignoring website / privacy issues on 10DLC. Unreachable or noncompliant sites are a frequent Brand/Campaign failure point.
- Inventing throughput plans. Confirm with your CSP.
- Skipping TFN verification because “we already have the number for voice.”
- Using one opt-in for unrelated marketing and transactional programs without clear language.
FAQ
Is toll-free SMS the same as A2P 10DLC?
No. Both can carry A2P traffic, but toll-free uses a national number with toll-free verification, while A2P 10DLC uses a local 10-digit number registered through a Brand + Campaign model. Twilio’s docs treat toll-free and short codes as separate from the A2P 10DLC system.
Which is approved faster: toll-free or 10DLC?
Neither is universally faster. Review time depends on your CSP, queue depth, completeness of materials, and whether reviewers request corrections. Bandwidth has published survey commentary that lead-time differences can be negligible. Use your provider’s current onboarding guide for planning—not a fixed industry average.
Which has higher throughput?
It depends. Some providers publish ~3 MPS as a common toll-free starting rate, with higher paid tiers available. 10DLC eligibility can be higher or lower depending on Brand score, Campaign type, and carrier. Always confirm the limits on your account.
Does buying more 10DLC numbers increase throughput?
Not necessarily. Throughput is often assigned at the Campaign or Brand level and shared across numbers. Buying numbers to evade limits can increase filtering risk.
Does verification or TCR registration replace SMS consent?
No. Registration identifies the sender and use case. Documented consent, STOP/HELP handling, accurate samples, and privacy disclosures remain required.
Can I use both toll-free and 10DLC?
Yes. Many businesses use toll-free for national support and 10DLC for local locations or specific programs. Each number and use case must follow its own registration path and consent rules.
What if I send from an unregistered 10DLC number?
On Twilio, US-bound SMS/MMS from an unregistered +1 10DLC number is blocked with error 30034. Other CSPs have their own enforcement—check with yours. Unregistered traffic may also incur additional carrier fees where still allowed; do not rely on that path.
Is toll-free verification free?
Often yes for the verification review itself on major CSPs, but you still pay for the number and messages. Confirm current terms with your provider. Free verification never means free compliance.
Do I need a website for either path?
For 10DLC Standard Brands, a working public site and privacy/SMS disclosures are practically required by many CSPs even when a TCR field is labeled optional. Toll-free verification increasingly expects Privacy Policy and Terms URLs. Plan for public HTTPS pages either way.
Key Takeaways
- 10DLC vs toll free is primarily an identity and registration-path decision: local Brand+Campaign versus national TFN verification.
- Consent under TCPA and carrier rules applies on both paths.
- Fees and MPS are provider-specific; never invent universal prices or throughput.
- Unregistered 10DLC and unverified TFN traffic face blocking or heavy filtering.
- Buying more 10DLC numbers does not reliably multiply throughput.
- Running both channels is valid when journeys and consent are separated cleanly.
- Fix website, privacy, samples, and opt-in evidence before you blame the number type.
Disclaimer
This article is for informational purposes only and is not legal advice. A2P 10DLC, toll-free verification, carrier policies, fees, and TCPA obligations change. Confirm requirements with your CSP, carriers, and qualified counsel before sending commercial messages.