10DLC and toll-free verification are the two main paths for US A2P sender registration: 10DLC registers the business behind a standard local number, while toll-free verification protects a branded toll-free number from spam abuse.
Both declare the business identity and use case to the carriers, and both affect delivery: registered senders get higher throughput and better reputation, while unregistered traffic is filtered. The choice between them follows the number strategy and the message use case, and the SMS gateway configuration carries the registration per route.
The guide assumes US-market traffic; other markets follow their own registration paths.
This guide is the first sub-article of the A2P compliance hub, and it pairs with the consent and opt-out workflow guide for the full US stack.
US A2P Sender Registration Happens in Two Parallel Tracks
US carriers route business text traffic through registered channels: a local number registered under 10DLC, or a toll-free number verified for messaging. The two tracks serve different numbers and use cases, and a business sending from both needs both registrations. The SMS gateway configuration should carry the correct registration per route.
The two tracks also differ in cost and throughput, and the choice should be modeled: a business that sends high-volume marketing from a local number pays 10DLC fees, while a toll-free route carries verification and alert traffic with a different fee structure. The model should run before the registration.
The choice is not permanent: a business can run both tracks, and many do, with local numbers for marketing and toll-free for verification. The gateway routes each traffic class to the registered channel, which is why the route configuration and the registration must match.
10DLC Aligns Business Identity With a Local Number
10DLC, short for 10-digit long code, registers a local number with the business brand, use case, and expected volume. The registration happens through the carrier's ecosystem and is scored, and the score affects throughput and fees. For most US business messaging on local numbers, 10DLC is the baseline requirement, and sending without it invites filtering.
The registration data should be reviewed by someone who understands the traffic, because a misdeclared use case is the most common cause of filtering. The declared volume should match the actual peak, and the brand should match the sender ID. The fees should be modeled against volume before choosing the route.
The scored nature of 10DLC means the registration is not a formality: a higher score improves throughput and lowers fees, while a low score or a complaint spike can reduce delivery. The business should treat the score as an operational number to manage, not a one-time application.
Toll-Free Verification Protects the Branded Sender ID
Toll-free numbers display a recognizable branded sender ID, but carriers require verification that the business owns the number and has a legitimate use case. Verification protects the channel from spam abuse and unlocks higher throughput. It is the right path when the brand identity of the sender matters more than a local number.
The verification should be paired with a content plan, because the toll-free sender ID is only protected if the messages match the declared use case and the complaint rate stays low. A verified number that sends off-declaration traffic loses the protection. The same declaration discipline applies to both tracks.
The verification process also declares the expected use case and volume, so a toll-free number used for both alerts and marketing needs both declared, and the message templates should match the declarations.
The Registration Checklist Differs by Use Case
| Use case | Likely path | Registration focus |
|---|---|---|
| Marketing on local number | 10DLC | Brand, use case, volume |
| Transactional on local number | 10DLC | Use-case declaration |
| Branded sender on toll-free | Toll-free verification | Number ownership |
| Mixed traffic | Both | Two-track compliance |
Expect a Ramp, Not a Switch, in Delivery
Registration does not guarantee full throughput on day one: carriers ramp delivery based on reputation, complaint rate, and volume history. The ramp means the first weeks should be watched closely, with opt-out and complaint rates kept low. The same monitoring discipline protects SMS verification at scale and every other registered route.
The ramp metrics to watch are delivery rate, complaint rate, and opt-out rate, each against the baseline from the first week. A complaint spike in the ramp is the fastest way to lose the throughput the registration was meant to unlock.
| Ramp phase | Expectation | Action |
|---|---|---|
| Week one | Partial throughput | Watch complaints closely |
| Weeks two to four | Improving delivery | Scale volume gradually |
| Month two | Near steady state | Compare against baseline |
| After a change | Re-ramp | Re-run the review |
The ramp also means the launch plan should expect lower delivery early and scale volume as the reputation builds, rather than treating the first day as the steady state.
The ramp also affects launch timing: a campaign that must land by a date should not start on the first day of a new registration. Plan the ramp buffer so the delivery rate reaches the required level before the deadline.
Keep Registration Current as the Business Changes
Registration is not a one-time event: a new use case, a new brand, or a significant volume change should trigger a registration update. Carriers use the declared use case to score the traffic, and a mismatch between the declaration and the actual messages hurts reputation. Review the registration whenever the business changes its messaging.
The review should also cover the SIM and route configuration in the gateway, because a registration that is current on paper but misconfigured in routing is still a delivery failure. A stale registration is the quietest way to lose delivery.
The review should be scheduled: quarterly for most senders, and immediately after any acquisition, rebrand, or campaign change. A registration that is stale is a registration that invites filtering.
The review should also confirm the route configuration matches the registration, because a registration that is current on paper but misconfigured in routing still fails delivery. The registration and the gateway should be one source of truth.
The one-source-of-truth rule also means a registration change should trigger a routing review in the same change window, so the two never drift apart.
The consent and opt-out rules that pair with registration are covered in the consent workflow guide.
Telarvo Expert Views
The ramp is where most US senders lose the battle: they register, see partial throughput, and either over-send or give up. We tell teams to expect the ramp, keep complaints near zero, and treat registration as a living record that changes with the business.
— Messaging Compliance Consultant, Telarvo Store
Validation note: 10DLC and toll-free rules and fees change; confirm the current requirements with the carrier ecosystem at registration time.
Conclusion
US A2P delivery depends on registering the sender through 10DLC or toll-free verification, matching the path to the use case, and managing the ramp with low complaint rates and current declarations.
Key Takeaways for US Senders
Register every number and use case before sending. Match 10DLC to local-number traffic and toll-free verification to branded senders. Expect a delivery ramp and watch complaints. Update registration when the business changes. Pair registration with provable consent and honest opt-outs.
Questions to Ask Before You Register
Ask which path fits your number strategy, what the registration fees and scoring implications are, and how the ramp behaves for your use case. Ask Telarvo Store for the gateway configuration that separates your registered routes.
FAQs
What is the difference between 10DLC and toll-free verification?
10DLC registers a local number with the business and use case; toll-free verification protects a branded toll-free number from abuse, and the two tracks differ in fees and throughput, so the choice should be modeled before registering.
Do I need both?
If you send from both local and toll-free numbers, yes, because each track covers a different number type and a different fee and throughput profile.
Why is my delivery lower after registration?
Carriers ramp throughput based on reputation and volume history, so the first weeks should keep complaints and opt-outs low, and the launch plan should include a ramp buffer before any deadline and compare the ramp against the week-one baseline.
When should I update registration?
Whenever the business adds a use case, changes a brand, or significantly changes volume, and on a scheduled quarterly review even when nothing obvious changed, because registration drifts quietly.
Can I send without registration?
Unregistered A2P traffic is filtered and unreliable, so registration is effectively required for US business messaging, and the declared use case must match the actual traffic and be reviewed on a schedule.