TL;DR
- Yes. A2P 10DLC registration is required for business texts sent to US numbers from a 10-digit long code.
- The rule depends on the traffic type and the destination, not your company size or location.
- Unregistered A2P traffic is now blocked by carriers, not just filtered.
- Because it is blocked outright, the symptom is messages stopping completely rather than degrading slowly.
- A business based anywhere that texts US customers needs to register.
- Registration also needs to be renewed, so an expired filing puts you back into blocked traffic.
If you are asking is A2P 10DLC registration required, here is the short, direct answer: yes, for any business sending application-to-person messages to US phone numbers from a 10-digit long code. There is no volume threshold that exempts you and no geographic loophole. If your messages reach American phones and they come from ordinary local numbers, registration is the condition under which carriers will deliver them.
That is the headline. The rest of this article explains the details behind it, because the specifics are what actually help you decide what to do next.
What "required" really means here
It is worth being precise about the nature of this requirement. This is not a law you might get fined for ignoring in some distant future. It is an operational condition set by the carriers themselves. AT&T, T-Mobile, and Verizon decide what traffic they will carry, and they have decided that A2P traffic from 10-digit numbers must be registered.
That makes the requirement immediate and practical rather than theoretical. The consequence of not registering is not a penalty notice. It is that your messages do not get delivered. In a sense, that makes compliance simpler to reason about. You are not weighing a risk of enforcement. You are deciding whether you want your texts to arrive.
Blocked, not filtered
The most important thing to understand about the current rules is how they changed. In the early days of 10DLC, unregistered traffic was heavily filtered, but the filtering was imperfect and some messages still slipped through. That created a false sense of security, because senders could look at partial delivery and assume things were basically fine.
That era is over. The major carriers now block unregistered A2P traffic at the network level. The distinction between filtering and blocking sounds technical, but it changes everything about how the failure shows up.
The gap between unregistered and registered delivery is close to total.
Why the failure mode is a useful clue
Because unregistered traffic is blocked rather than filtered, the symptom is distinctive and easy to recognize. A content problem or a reputation issue degrades your delivery gradually, shaving off a percentage here and there. A registration gap does something different. It makes your messages stop arriving almost entirely.
So if your texts went from working to nothing, more or less overnight, that pattern points strongly at registration rather than content. It is one of the cleaner diagnostics available in a space that is often murky.
Gradual decline usually means content or reputation. A sudden, near-total stop usually means a registration gap.
It applies wherever your business is based
A common misconception is that 10DLC only applies to American companies. It does not. The rule follows the recipient's number, not the sender's headquarters.
A business based in London, Toronto, Sydney, or anywhere else that sends texts to US phone numbers needs to register exactly as much as a company in Ohio. If any meaningful portion of your recipients are in the United States, you are subject to the requirement. Where your servers sit or where your business is incorporated does not change that.
Volume does not exempt you
Another frequent hope is that low volume provides a way out. It does not. The requirement is about the type of traffic, not the amount. Whether you send ten messages a month or ten million, application-to-person messages to US numbers fall under the same rules.
This catches out a lot of small businesses that assume registration is something only large senders need to worry about. In reality, a solo practitioner sending appointment reminders to a few dozen clients is subject to the same core requirement as a national retailer. The scale differs, but the obligation is the same.
What about toll-free and short codes?
10DLC specifically governs 10-digit long codes, which are standard local numbers. There are other messaging routes, such as toll-free numbers and short codes, and they have their own separate verification and approval processes.
The point to take away is that there is no unregistered route to reliable business texting. If you switch to a toll-free number to avoid 10DLC registration, you simply encounter toll-free verification instead. Every legitimate path to sending business messages at scale involves some form of registration or verification. 10DLC is the one that applies to ordinary local numbers.
Registration is not permanent
Here is a detail that surprises even businesses that registered correctly the first time. Registration has to be renewed. It is not a one-time stamp that lasts forever.
If a registration lapses, you fall back into the same blocked state as a business that never registered at all, and the failure looks identical. Messages simply stop arriving. This is an easy problem to prevent and an annoying one to diagnose, so the practical advice is to diary your renewal date the moment you complete registration. A calendar reminder is cheaper than a week of blocked traffic.
So what should you actually do?
If you have read this far, the answer is probably clear, but let us make it concrete.
- If you send any business texts to US numbers from 10-digit numbers, plan to register.
- If your messages recently stopped arriving entirely, check your registration status first.
- If you are based outside the US but text American customers, you are included.
- If you are small or low-volume, you are still included.
The good news is that registration is neither expensive nor especially difficult once you know the steps. Our guide on how to register for 10DLC walks through the whole process, and the overview of what A2P 10DLC registration is explains the two layers in plain terms if you want the full picture first.
What counts as A2P traffic in the first place?
Since the requirement hinges on sending "application-to-person" messages, it is worth being clear about what that actually includes, because the definition is broader than many people assume.
A2P covers essentially any message sent by software or a platform rather than typed by a person on their own phone. That includes appointment reminders scheduled through a booking system, order updates triggered by an e-commerce platform, verification codes generated by your login system, and marketing sent through a campaign tool. If a system rather than a human thumb is sending the message, it is A2P.
The contrast is person-to-person messaging, which is you texting a friend from your own device. That is not subject to 10DLC registration. But the moment a business uses software to send messages to customers at any scale, it crosses into A2P territory, and the registration requirement applies.
The cost of ignoring the requirement
It is worth being concrete about what non-compliance actually costs, because "your messages get blocked" can sound abstract until you translate it into your own operations.
Think about what each message type does for your business. A blocked appointment reminder can mean a no-show, which is lost revenue and a wasted slot. A blocked delivery notification can mean a confused customer and a support ticket. A blocked verification code can mean a customer who cannot log in and gives up entirely. None of these are hypothetical. They are the daily consequences of unregistered traffic being blocked, and they add up quickly.
Set against those consequences, the modest effort and cost of registering looks like an easy decision. This is exactly the calculation our ROI calculator is built to make visible, by turning your blocked messages into an estimated revenue figure.
Getting ahead of the requirement
If you are reading this before you have started sending, you are in the best possible position, because you can register before you ever hit a delivery problem. Building registration into your launch plan means your very first campaign sends cleanly, rather than discovering the requirement the hard way when messages fail to arrive.
If you are already sending and things are working, it is still worth confirming your registration status and your renewal date rather than assuming you are permanently in the clear. Registrations lapse, rules evolve, and a quick check now is cheaper than a scramble later.
Frequently asked questions
A handful of related questions come up whenever people confirm whether they need to register, so here are quick, direct answers.
Do I need to register if I only send verification codes?
Yes. One-time passcodes and verification messages are application-to-person traffic, and sending them to US numbers from a 10-digit code falls under the requirement. In fact, verification traffic is one of the most common 10DLC use cases, precisely because so many businesses send login and security codes.
What if I use a third-party tool that sends on my behalf?
If a booking system, marketing platform, or any other tool sends texts to your customers using your business identity, that is still your A2P traffic and it still needs to be registered. The tool provides the plumbing, but the messages represent your business, so the registration obligation is yours.
Does registration expire, and what happens if it lapses?
Registration is renewed periodically rather than being permanent. If it lapses, you fall back into the blocked state of an unregistered sender, and messages stop arriving. The failure looks identical to never having registered, which makes a lapsed renewal easy to misdiagnose. Setting a calendar reminder for your renewal date is the simplest possible safeguard.
I send to both US and international numbers. Does the rule cover everything?
10DLC specifically governs messages delivered to US numbers. Your international traffic is subject to the rules of those destinations rather than to 10DLC. But the moment any meaningful portion of your recipients are in the US, you need to register for that portion, so in practice most businesses texting a mixed audience end up registering.
Is there any legitimate way to avoid registering?
Not for business texting at scale to US numbers. Alternative routes like toll-free numbers and short codes have their own verification and approval processes, so switching to them does not remove the compliance step, it just changes which one applies. There is no unregistered path to reliable delivery.
The bottom line
Is A2P 10DLC registration required? For business texting to US numbers from 10-digit codes, yes, without exception for size or location. The carriers now block unregistered traffic outright, which means registration is not really a compliance box to tick but the basic condition for your messages to be delivered at all. The sooner you register, the sooner your texts start arriving reliably. If you want to see what that reliable delivery is worth in real money, the ROI calculator will show you in about two minutes.