10DLC

10DLC, short for 10-Digit Long Code, is the framework US carriers use to permit application-to-person text messaging from ordinary local phone numbers. Before it existed, businesses routinely blasted messages from unregistered long codes that were never designed for bulk traffic, and carriers responded by filtering that traffic aggressively or blocking it outright.

The framework replaced that guesswork with a registration system. A business registers its brand and each individual messaging campaign, receives a trust score, and is granted throughput limits in proportion. For anyone sending SMS from a local number in the United States, 10DLC registration is not optional in any practical sense: unregistered traffic is heavily filtered, and in many cases simply does not arrive.

The framework applies specifically to the United States. Canadian carriers operate their own arrangements, and messaging into other countries follows entirely different rules, so a business sending across borders is managing several regimes at once rather than one.

Related reading

• How to clean a phone list for SMS
• Bulk phone number validation
• Check if a number is mobile or landline

What is 10DLC?

A long code is any standard ten-digit phone number, the same format a person uses. 10DLC is the set of rules governing how such a number may be used to send application-to-person messaging, meaning messages originated by software rather than typed by a human.

The framework emerged because carriers needed a way to distinguish legitimate business messaging from spam without banning local numbers outright. Short codes already existed for high-volume campaigns, but they are expensive, slow to provision, and impersonal. Businesses wanted the familiarity of a local number with the reliability of a sanctioned channel, and 10DLC is the compromise that resulted.

• ✓Brand — the legal entity behind the traffic, verified against official records.
• ✓Campaign — the specific use case, such as marketing, two-factor authentication, or customer care.
• ✓Numbers — each sending number is attached to one registered campaign, and only one at a time.

Registration operates through The Campaign Registry, a central body that carriers rely on to vet senders. A business registers a brand, which identifies the legal entity behind the traffic, and then registers one or more campaigns describing the specific use case: marketing, two-factor authentication, customer care, delivery notifications, and so on.

Each registered campaign is assigned throughput allowances based on the trust score attached to the brand. Trust score is influenced by how thoroughly the business is verified, its history, and the nature of the use case. A well-verified brand running a low-risk campaign gets substantially more message-per-second headroom than an unverified one running promotional traffic.

Use case classification carries real consequences beyond fees. A campaign registered as low-volume mixed content receives modest throughput and light scrutiny, suitable for a small business sending a few hundred messages. A declared marketing campaign attracts more scrutiny and a higher per-campaign fee, but unlocks the throughput volume senders need. Choosing the wrong classification is a frequent source of unexplained throttling.

Special use cases exist for traffic carriers treat as inherently higher trust, including public utility notifications, emergency alerts, and certain charitable and political messaging. These carry different vetting requirements and are not available to general commercial senders, but they matter for organisations that qualify because the throughput and filtering treatment differ substantially.

How 10DLC works

The registration chain has three links. The business registers its brand with identifying details including its legal name and tax identifier. It then registers each campaign, describing the message content, the opt-in mechanism, and sample messages. Finally, phone numbers are associated with a registered campaign, and only then may they carry A2P traffic at sanctioned throughput.

Carriers enforce the framework at the network edge. Traffic arriving from a number tied to a registered campaign is evaluated against that campaign's declared use case and throughput allowance. Traffic from an unregistered number is treated as suspect and filtered, which in practice means messages disappear without a clear error returned to the sender.

Throughput is expressed in messages per second and varies considerably. A thoroughly vetted brand can achieve throughput sufficient for large campaigns, while an unvetted sole trader may be limited to a trickle. This is why two businesses sending identical content can see completely different delivery outcomes.

Carriers also levy fees that flow through the messaging provider: a one-time brand registration charge, a recurring per-campaign fee that varies by use case, and per-message carrier surcharges. Those costs are modest per message but material at volume, which makes sending to numbers that cannot receive the message a direct and avoidable waste.

• ✓Unregistered traffic on a long code is filtered hard and frequently disappears without an error.
• ✓Throughput is granted in messages per second, in proportion to your brand's trust score.
• ✓Carrier surcharges apply per message attempt, including attempts that fail.
• ✓Content filtering runs independently, so a registered campaign can still have messages blocked.

Content filtering operates independently of registration. Even a properly registered campaign can see individual messages blocked for containing prohibited content, shortened URLs from public shorteners, or language patterns that resemble known spam. Registration buys throughput and legitimacy; it does not exempt a sender from content review.

Number association is worth understanding as a distinct step. A phone number is not inherently registered; it is attached to a campaign, and a number can only serve one campaign at a time. Businesses that move numbers between campaigns, or that assume buying a number from a provider registers it automatically, frequently find traffic filtered because the association was never made.

There is also a vetting escalation path. Where the automatic trust score assigned at registration is lower than a business needs, a secondary manual vetting process is available through third-party evaluators. It costs more and takes longer, but for an established business whose automated score does not reflect its legitimacy it is often the difference between viable and unviable throughput.

Why 10DLC matters for SMS and outreach teams

10DLC turns sender reputation into a measurable asset. Throughput and delivery depend on how carriers score your traffic, and that score is shaped by the outcomes of the messages you send. Consistently sending to numbers that cannot receive messages produces the failure pattern carriers treat as a spam signal.

This is the point at which list quality stops being an efficiency question. A list carrying a meaningful proportion of landlines and disconnected numbers will generate failures at a rate that degrades delivery for the rest of the list. The undeliverable portion is not merely wasted spend, it actively harms the deliverable portion.

The economics compound. Carrier surcharges are billed per message attempt regardless of outcome, campaign fees recur monthly, and the throughput you are granted is a finite resource. Spending any of it on numbers that were never going to receive the message is pure loss.

Registration also demands accuracy about your opt-in process. The campaign registration describes how consumers consent, and that description is expected to match reality. A business that cannot articulate its opt-in flow clearly enough to register a campaign usually has a consent problem that predates its messaging problem.

Finally, the framework interacts directly with the TCPA. Registering a campaign does not grant permission to message anyone; it grants carrier permission to carry the traffic. Consent remains a separate legal requirement, and a registered campaign sending without consent is a compliant pipe carrying non-compliant messages.

Throughput constrains campaign design in ways teams often discover late. If a campaign is granted a modest messages-per-second allowance, a send to a large list does not fail, it simply takes far longer to drain the queue than expected. Time-sensitive messaging such as a flash promotion or an appointment reminder loses its value entirely if it arrives hours after it was triggered, so knowing your real throughput before scheduling matters as much as knowing your delivery rate.

Getting started with 10DLC

Begin by identifying which use cases you actually run. Marketing, transactional alerts, two-factor codes, and customer care are registered separately and carry different fees and throughput. Bundling everything into one campaign is a common mistake that leaves the high-value transactional traffic constrained by the scrutiny applied to promotional traffic.

1. 1
   Gather verification details — Collect your legal entity name, tax identifier and address exactly as they appear on official records — mismatches are the most common cause of a low trust score.
2. 2
   Register the brand — Submit the entity for verification first; this is usually quick because much of the checking is automated against public records.
3. 3
   Register each use case separately — Keep two-factor and transactional traffic on their own campaigns so they are not throttled by the scrutiny applied to marketing.
4. 4
   Attach your numbers — A number is not registered by default. Associate each sending number with a campaign, or its traffic will be filtered.
5. 5
   Clean the list before the first send — Validate and remove landlines, VOIP numbers that discard SMS, and dead numbers so you establish a good reputation rather than repairing a bad one.

Then monitor delivery by segment rather than in aggregate. A single overall delivery rate hides the pattern that matters: whether failures cluster in a particular carrier, a particular line type, or a particular batch of numbers acquired from one source.

Key takeaways: 10DLC

• ✓10DLC is the US carrier framework permitting application-to-person SMS from standard ten-digit local numbers.
• ✓Registration runs through The Campaign Registry in three steps: brand, campaign, then the numbers attached to it.
• ✓Throughput is granted in proportion to a trust score, so two senders with identical content can see very different delivery.
• ✓Unregistered A2P traffic on a long code is heavily filtered and frequently fails without a clear error.
• ✓Sending to landlines and dead numbers generates the failure signals that degrade the sender reputation registration earned.
• ✓Registration authorises carriers to carry your traffic; it does not supply the consent the TCPA separately requires.
• ✓A number must be explicitly associated with a registered campaign, and can serve only one campaign at a time.
• ✓Campaign fees recur monthly per campaign and carrier surcharges apply per message, so cost scales with both structure and volume.

Frequently asked questions about 10DLC

• Do I have to register for 10DLC to send business text messages?

• What is a 10DLC trust score and how does it affect message throughput?

• How is 10DLC different from using a short code for SMS campaigns?

• Does 10DLC registration mean my messages will always be delivered?

• Why do landlines in my list hurt my 10DLC campaign performance?

• Does registering a 10DLC campaign make my messaging TCPA compliant?

• How long does 10DLC brand and campaign registration usually take?

• What does 10DLC actually cost beyond the per-message price?

Related terms and concepts

• A2P messaging — Application-to-person SMS — messages sent by software to a person, rather than between two people.
• Short code — A five- or six-digit number leased for high-volume, carrier-approved SMS campaigns.
• SMS deliverability — The proportion of sent SMS messages that are actually delivered to a recipient handset.
• Toll-free number — A number, such as an 800 or 888 prefix, where the recipient rather than the caller pays for the call.
• Opt-in — A recipient explicitly granting permission to be contacted by call or text.