What Is 10DLC? The Registration Standard Behind US Business Texts

10DLC is an industry standard for application-to-person messaging on 10-digit long codes, the ordinary local numbers customers already recognize. Registration is the real product you are buying when you text from a business number, not the number itself. The registration determines how fast your messages move, whether carriers filter them, and how much of your brand’s reputation rides on each send.

Table of Contents

• A Registration Standard Hiding Inside Your Normal Phone Number
• How the Registry, Carriers, and Your Platform Connect
• From Brand to Live Traffic in Six Screenable Steps
• Where Senders Lose Throughput and Trust
• Registered Long Code, Short Code, or Toll-Free: Choosing With Your Eyes Open
• Frequently Asked Questions

A Registration Standard Hiding Inside Your Normal Phone Number

A 10-digit long code is the local-looking number your customers already dial, and 10DLC is the registration layer that makes it legal and deliverable for application-to-person traffic. It exists because carriers had no way to tell a plumber confirming an appointment from a spammer blasting the same area code.

Before this framework, businesses sent application-to-person SMS from two places: shared short codes, which looked nothing like a local number and carried a monthly cost, or unregistered long codes, which carriers increasingly filtered as spam. Neither option gave a small business a recognizable number with a known identity behind it. For a business, that registration is not paperwork bolted onto a number. It is the thing that tells carriers who is sending and why.

10DLC and SMS are different questions. One is a compliance and identity framework; the other is the underlying protocol. If you want the protocol itself untangled, the 160-character workhorse explained covers it. Our own 10DLC business text basics walk through the same framework from the buyer’s side.

How the Registry, Carriers, and Your Platform Connect

The Campaign Registry is a third-party company chosen by AT&T, Verizon, T-Mobile, and U.S. Cellular for registering application-to-person 10-digit-long code messaging campaigns (ServiceTitan’s registration FAQ explains the structure). Nobody built this internally, and that is the point. A single industry registry means one brand record and one campaign record per use case, sitting between your platform and the carriers who decide what reaches a handset.

When your platform submits on your behalf, three records get created and they are not interchangeable. The brand record names the entity sending. The campaign record names what the messages are for: marketing, reminders, account notifications, or mixed. The number itself is the third piece, attached to the campaign so carriers know which long code carries which use case. A brand with no campaign sends nothing. A campaign with no number is a promise with no line.

Carrier filtering runs on the identity those records carry. Vetting is the step that raises a sender’s trust and buys higher throughput, and it exists because carriers assign sending limits per use case. A registered sender with a clean vetting record gets more room per minute. An unregistered one gets a fraction of that room, or none.

From Brand to Live Traffic in Six Screenable Steps

Do this through a messaging platform. Direct carrier filings are not a realistic project for a business team.

1. Pick the long code you will send from, ideally a local number your customers recognize.
2. Complete brand registration with the entity’s legal name, EIN, and address, and keep all three consistent with what carrier records show.
3. Choose the campaign use case that matches the real traffic. Mixed use cases register as mixed, and a mismatch with what you actually send is a filter trigger.
4. Submit the campaign for vetting, which is what raises sending throughput above the default tier.
5. Connect the individual phone numbers to the campaign, so each long code carries a registered use case.
6. Wire the registration into your customer data platform, review software, and self-serve preferences, so opt-in records and sender identity stay current after you go live.

Telnyx lists campaign vetting at $15 per submission and campaign monthly recurring costs of $2 to $30 depending on use case. That price applies whether you send a hundred messages a month or ten thousand, which is why the throughput question, not the fee, drives most improvement projects after registration. Carrier billing models in this space are documented separately from the platforms, and the 10DLC messaging registration gate walks through the details.

Where Senders Lose Throughput and Trust

Registering the number and forgetting the campaign that drives it is the mistake that costs most senders their speed. Carriers score the campaign, not the phone line. A registered brand with a stale use case description and zero sample messages will queue just like an unregistered sender.

Trusting old shared short codes as a replacement is a mistake several guides still suggest. Short codes had their moment, and they are still legitimate for mass alerts at volume, but throughput alone does not tell a business how it ends up filtered. A short code with no registered identity behind it gets no more trust from a carrier than a long one.

The mistake that hurts trust fastest is opt-in written for the registration form and not for the customer. Reviewers grading opt-in language want to see consent words a real customer gave. If your site says “I agree to receive marketing texts” but your form fails to identify the business, the campaign gets flagged, and the flag stays visible to carriers for months.

Another trap: submitting the brand name that matches your DBA rather than your EIN. Platforms check against the entity that pays taxes. A brand record that names a trademark but not the legal entity gets rejected, and each rejection costs you the vetting fee and the queue time.

Sample messages submitted with the campaign are supposed to represent what you send. Most registrations fail here because the samples describe appointment reminders while the live traffic is promos. Align the samples to the use case, not to the prettiest message in your sequence.

Registered Long Code, Short Code, or Toll-Free: Choosing With Your Eyes Open

Choose a registered 10DLC number when your customer already knows your local line, when you text from the same number customers call, and when you want to avoid the shared-code cleanup. That is the common case for most businesses.

Choose a short code only when your traffic is genuinely at the scale that justified code rental, and when you can stand the lead time. Fine for mass alerts. Wrong for a two-person shop that texts customers through the day. If you need help telling messaging formats apart, what’s the difference between SMS and MMS changes what a short code costs to operate.

Choose a toll-free number when you accept that registration there is a separate process with its own verification, and that a toll-free line often reads as unlocal to a customer who dials area codes. For most small businesses, the toll-free process adds a second registration for a channel most customers do not recognize.

The signal that settles it for us: does the number need to stay consistent with a phone line the customer already has on file? If yes, register the long code and treat the registration as a durable asset. If no, pick the format that matches how you actually reach people and register the same way.

That is how we approach it at Sociocs. WhatsApp Business messaging with click-to-chat and Instagram DMs, story mentions, and story replies carry the same customer history. Google Reviews and Google Q&A management sit beside the same conversation thread. The online form builder blocks spam and exposes a no-code API your team can wire into the tools it already runs. Telegram Business Bot messaging and Android app reviews from Google Play round out the channels. Register the entity that owns the number, and list the legal name, EIN, and a physical address your carrier records can match.

The businesses that treat registration as the start of the relationship, not the end of a filing, are the ones whose texts keep arriving.

Frequently Asked Questions

What is 10DLC compliance?

Compliance means your brand and campaign are registered in the industry registry the carriers recognize, with an entity name, EIN, use case, and opt-in record that match what you actually send. It also means keeping the campaign current after approval: sample messages, use case, and sender identity stay aligned with live traffic. A registered brand whose campaign language drifts from its actual texts loses throughput just like an unregistered sender.

Does 10DLC apply to every US business that texts customers?

It applies to application-to-person messaging from a 10-digit long code, which is what most businesses send. Person-to-person texting between two people is outside the framework. The moment a business sends a campaign, reminder, or notification at scale, the registration layer applies, even if the volume is small.

How long does registration take?

Timelines depend on your platform’s documentation and vetting queue, not on your number. A clean filing moves quickly. Filings that get rejected for entity name mismatches or inconsistent opt-in language restart that clock, so the practical lever is getting the first submission right rather than sending more documents.

Is registration the same as a short code?

No. A short code is a different number type with its own approval process and its own carrier relationships, and registering a long code does not register a short code. A registered 10-digit long code carries location and identity; a short code carries volume and a separate review. If you need help, ask the reader’s platform what covers their use case.

What stops a registered sender from being filtered?

Deliverability after registration depends on opt-in records, sample messages that match real traffic, and sender identity that stays consistent. Registration is what gets a sender considered at all; the ongoing signals decide the throughput and the filtering.