Is A2P 10DLC registration legally required?

It's a carrier requirement rather than a law: the US mobile carriers built the program and enforce it themselves through the network, so there's no government citation for skipping it. That's a narrower statement than it sounds. Your provider can refuse to send or close your account, and telemarketing law like the TCPA still applies to your texting regardless of registration status.

Do I need A2P 10DLC if I only send appointment reminders?

Yes. Reminders are application-to-person messages sent from a 10-digit local number, which is the whole test. They're also one of the easier use cases to get approved — informational, expected by customers, routinely registered. Being helpful rather than promotional affects how your campaign is reviewed, not whether you need one.

Does A2P 10DLC apply if I text customers from my personal cell phone?

If you genuinely type each message in your phone's messaging app, that's person-to-person texting and sits outside the program. It stops being true the moment those texts run through a CRM, a texting app, or a shared inbox. Carriers can also filter a personal number that starts sending in business patterns, so this isn't a durable place to stand.

Can I avoid A2P 10DLC by using a toll-free number?

You'd be swapping one verification for another. Toll-free numbers use a separate toll-free verification process rather than A2P 10DLC, and it asks many of the same questions about business identity and how customers consent. It's a legitimate choice on its merits, but there's no lane left that lets a business send unverified.

Do I still need to register if my business is brand new?

Yes — the requirement attaches to the traffic, not to how long you've been operating. New businesses do hit one practical wrinkle: brand registration is checked against official records, so a very recently formed entity may need its EIN and address on file before the details match. Registering early is easier than untangling filtered texts later.

Do You Need A2P 10DLC Registration? Who It Applies To

The short answer

If your business sends text messages to customers from a regular 10-digit US local number, and those messages go out through software rather than your thumbs on a handset, then yes — A2P 10DLC registration is required before carriers will deliver them reliably. That covers far more businesses than owners expect: appointment reminders, "your tech is ten minutes out" dispatch texts, quote follow-ups fired from a CRM, messages typed into a softphone on your laptop. If a system sends it, it is application-to-person traffic, even when the message reads exactly like one human writing to another.

The word "required" deserves a footnote, because it gets misunderstood in both directions. A2P 10DLC is not a federal law, and no government agency issues you a citation for skipping it. It is a registration program the US mobile carriers built and enforce themselves, administered through an industry clearinghouse called The Campaign Registry. They enforce it through the network, not the courts: unregistered traffic gets refused by providers or filtered by carriers, and the bill for non-compliance arrives as texts that quietly stop landing rather than as a penalty notice.

What A2P 10DLC actually covers

The name is the definition. "A2P" is application-to-person: a message an application sends to a human being. "10DLC" is a 10-digit long code — an ordinary local phone number, the kind your business already has. Put together, the 10DLC requirements apply to business messaging sent from normal local numbers through any kind of sending platform.

What that includes in practice, and the one thing it doesn't:

Any texting feature inside a CRM, scheduling tool, review-request tool, or field-service app.
A softphone or web-based business line, including the text tab you barely use.
Automated sequences: reminders, confirmations, "we missed your call" replies, drip follow-ups.
Messages a person types by hand — if they leave through a platform and an API rather than a handset, they are still A2P traffic. Carriers classify by how the message is sent, not by how personal it sounds.
Both marketing and pure customer-service messaging. There is no "but mine aren't promotional" exemption; your use case affects how your campaign is reviewed, not whether you register.
Outside it: genuine person-to-person texting, where a human types on a phone and hits send in the native messaging app. That is the exception people try hardest to stretch, and it breaks the moment business texting routes through anything automated.

Does this apply to me? The cases owners get wrong

Most people asking whether A2P 10DLC compliance applies to them are really asking whether their particular situation is the exception. Usually it isn't. Here are the specific cases that trip owners up, with the honest answer for each.

"I text from my own cell phone." If you genuinely type every message on the handset, that is person-to-person messaging and sits outside the program. Two things end that quickly: the moment you add a texting app, a shared inbox, or a CRM, you are sending A2P traffic — and carriers can still filter a personal number that starts behaving like a business sender.
"My texts are one-to-one, not blasts." Volume and personalization aren't the test. A single appointment reminder sent by software is A2P. Registration is about who is sending and how, not how many recipients are on the message.
"They're just appointment reminders." Reminders are a routine, readily approved use case, and they still have to be registered. Informational beats promotional at review time; it doesn't exempt you from filing.
"I'm a sole proprietor without an EIN." You're still in scope, on a different path. See below — this is the one case where the answer meaningfully changes shape.
"My texting platform handles compliance." Some platforms file a basic registration for you. What they can't do is fix the things reviewers actually reject on: your consent checkbox, your opt-in language, your privacy policy. A filing that never passes review leaves you exactly as filtered as no filing at all.
"I only text a few people a day." Common enough that it gets its own section below.
"I'm not sure whether my number is registered." That's answerable in one phone call — see how to tell where you stand for the exact question to ask your provider.

"But I only text a few people a day"

Low volume can genuinely change your experience, which is why this belief survives. On platforms that still hand unregistered long-code traffic to the carriers at all, small volumes sometimes trickle through — enough that texting feels fine for a while. Then you grow, or add a second location, or a busy week doubles your sends, and delivery falls off a cliff. Your registration status didn't change. Your traffic pattern crossed a filtering threshold.

The 10DLC registration requirements are keyed to what you are, not how much you send: a business sending application-originated messages from a US local number. What volume does affect is your throughput tier and the fee structure — the program has lower tiers built specifically for small senders — and how long you can go unregistered before something notices.

There's a quieter cost, too. Because filtering is silent, "a few texts a day" is exactly the volume at which you'll never spot the failures. Nobody calls to say your reminder never landed. They just don't show up.

Sole proprietors and businesses without an EIN

If you're a sole proprietor with no EIN, you aren't exempt — you're on a separate, smaller path. The registry supports a sole-proprietor registration that verifies your identity by other means instead of an EIN. The trade is real constraints: typically a single campaign, only a handful of numbers attached to it, low daily throughput, and a restricted set of permitted use cases. It is a legitimate route for a genuinely one-person operation, but confirm the current caps with your provider before you commit to it, because outgrowing this path means registering again from the top.

Two practical notes. First, if you do have an EIN, use the standard path even if you're small — it gives you more headroom as you grow. Second, sole-proprietor verification includes a one-time passcode sent by text to a US mobile number you control; a landline or a VoIP business line won't receive it, so be ready with a mobile handset even if someone else is filing on your behalf.

The identity requirements differ by path — the standard route matches your legal name, EIN and address against official records, while the sole-proprietor route verifies a person instead. The standard route's matching rules, field by field, are in the registration checklist.

Toll-free and short codes: the alternatives, honestly

A2P 10DLC applies to 10-digit local numbers. There are two other lanes, and the important thing to know before you pick one to dodge registration is that none of the three lets you send unverified. "Just don't register" stopped being an option when the carriers finished rolling this out. Switching to toll-free means doing a different verification, not skipping verification. The trade-offs, briefly — and at length in 10DLC vs toll-free:

Toll-free numbers use a separate toll-free verification process instead of A2P 10DLC. The paperwork is often simpler, and it asks many of the same questions about business identity and how customers consent. The trade-off is perception: a toll-free number reads as a call center to some customers, which matters if you're a local business whose area code is part of your credibility.
Short codes are the five- or six-digit numbers big brands use. They have their own application process, they are by far the most expensive lane, and they are overkill for anyone reading this guide.

What actually happens if you skip it

Nothing dramatic, which is exactly the problem. There's no citation and no shutdown notice — the consequences are all delivery-side, and they compound quietly. The honest framing of the risk: this is a revenue leak, not a legal exposure. Every filtered reminder is a potential no-show; every filtered follow-up is a lead that thinks you ghosted them. The full diagnostic — including how to rule out the other causes of undelivered texts — is in why business texts stop delivering. The sequence usually runs like this:

Your provider may simply refuse to send. Many platforms now block unregistered US long-code traffic outright rather than pass it to carriers, so messages fail before they leave.
Where messages do go out, carriers filter them. Your dashboard may show the message as sent, or as undelivered with a code nobody explains, while the customer's phone shows nothing.
Delivery goes inconsistent by carrier, because each one filters on its own thresholds — which is why partial delivery is such a reliable tell.
Providers can suspend or close accounts over sustained unregistered or violating traffic, and carrier-side penalty charges for violations pass through your provider's bill.

What registration is not

Two boundaries worth stating plainly, because both get oversold.

Registration is not legal cover. A2P 10DLC satisfies the carriers so your messages deliver. Telemarketing and consent law — the TCPA and its state cousins — is a separate layer that depends on how you collected consent and who you're texting. Good registration builds the consent evidence that supports that side, but we build carrier plumbing; we're not a law firm, and consent language is worth your counsel's review.

Registration is also not a one-and-done checkbox. Your campaign describes a specific use case. If what you send drifts materially away from what you registered — you filed for customer care and start sending promotions — you update the campaign rather than hoping nobody looks. And an approved campaign only covers numbers actually linked to it, so adding a second line without attaching it recreates the whole problem.

If the answer is yes, here's the order

Assuming this applies to you, the sequence below is the one that avoids burning review cycles on guesses. If you'd rather hand the whole thing off, that's what our A2P registration and setup service is for — and if you're not sure texting is even your biggest leak, the $75 audit looks at the whole lead flow first. Either way, the order is:

Confirm your current status. Ask your texting provider for your A2P 10DLC campaign status — the answer is one of "none on file," "in review," "rejected," or "verified," and it decides everything else.
Fix your website before you file: the consent checkbox in plain HTML, complete opt-in language, a privacy policy that doesn't contradict it. Reviewers visit your live site.
File the brand, then the campaign, with details that match your official records.
If it comes back rejected, decode the actual reason rather than resubmitting a guess — the rejection guide maps the common codes to their real causes.
Link your sending number to the approved campaign. An approved campaign with an unattached number still can't send.

A2P / SMS Compliance — the service Texts not delivering?10DLC vs toll-free Registration checklist How long it takes Campaign rejected?← All guides

Do you need A2P 10DLC registration? How to tell if it applies to you