10DLC vs Toll-Free SMS: Which Should Your Business Use?

Application-to-person messaging in the United States cannot be anonymous. Carriers require A2P traffic to identify itself, and the two ways to do that are the subject of this guide.

10DLC is a registered 10-digit long code. Your brand and campaigns are registered through The Campaign Registry (TCR), the industry body that administers 10DLC, and the number carries A2P traffic with a local area code. Recipients see a familiar local number, and the number supports two-way conversations.

Toll-free SMS uses a text-enabled toll-free number, the kind that already appears on a business card or website, for A2P traffic. The number must be verified before it can carry application traffic, it supports two-way messaging, and recipients see a national rather than local sender.

Both exist because neither fits every traffic profile. The decision comes down to registration burden, sender appearance, expected volume and the use case your messages serve. Choosing by habit rather than by profile is how businesses end up with filtered traffic or with a sender type that works against them. The comparison below exists to make the trade-offs explicit, and the honest answer is that the right choice depends on your traffic, not on which option sounds more modern.

Set marketing language aside. The differences that matter for a decision are registration, appearance, reply capability, throughput and use-case fit. The table below summarises them at the level of a decision, not a specification.

The rows are deliberately non-prescriptive. Throughput in particular should not be read as a published number: supported rates depend on destination, sender type, registration and upstream connectivity, so treat the profiles above as shapes rather than guarantees.

Decide from your traffic, not from a preference.

Choose 10DLC when volumes are moderate and local presence matters. It is the mainstream route for transactional and OTP traffic at moderate scale, it supports two-way replies, and recipients see a local number, which is often the right signal for appointment reminders, delivery updates and verification flows. The cost is the work: brand and campaign registration through TCR must be in place before launch, and trust score and campaign vetting shape throughput across carriers.

Choose toll-free when you need national reach and higher expected volume, or a mixed programme of transactional and marketing traffic on one sender. It supports two-way replies, must be verified before A2P use, and in some cases may be preferred where 10DLC filtering is biting, although that depends on carrier behaviour rather than on any rule, so do not switch on a hunch.

Choose neither when the profile is genuinely different. Short codes exist for dedicated peak-volume campaigns where a short, memorable number and response capacity justify a different cost profile. Alphanumeric sender IDs are generally not supported to US numbers, but they are common in the UK and other markets, so a global programme may deliberately use different sender types per destination.

Whichever route you choose, the launch checklist is the same, and registration lead time is the part that catches people out.

Handle consent before launch, not after a complaint. Record when a recipient opted in and honour opt-outs on every send, because filtering and compliance both reward discipline. Allow real lead time for registration and carrier sync; the compliance guide covers the requirements as they stand, was last updated on 11 March 2024 and is not legal advice, and service-provider rules may require originator pre-registration in some cases, so check the rules that apply to your traffic.

Test on real numbers before switching traffic. A test send verifies sender appearance, two-way replies and receipts end to end, which simulation cannot. Then monitor delivery receipts and message state codes in production rather than relying on send counts, because a message that fails review is not the same as one that failed to send. If replies are part of your use case, test those too: the reply path depends on number configuration that is easy to assume and hard to notice when broken.