What Is A2P 10DLC? Registration Basics in Plain English

A2P 10DLC is the framework United States mobile carriers use to regulate business text messaging sent over standard 10-digit phone numbers. A2P stands for application-to-person, meaning messages sent through software rather than typed by hand on a phone, and 10DLC stands for 10-digit long code, the familiar local number format. If your organization sends texts through any platform, you are sending A2P traffic, and carriers require you to register who you are and what you send before that traffic is fully deliverable.

Key takeaways:

• A2P 10DLC is the carrier-mandated registration system for business texting sent from local 10-digit numbers in the United States.
• Registration happens through The Campaign Registry (TCR), where you register your organization as a brand and your messaging use cases as campaigns.
• Registered senders receive a trust score that influences how many messages they can send per day and how fast.
• Unregistered traffic faces heavy filtering, blocking, and per-message carrier surcharges, so registration is not optional in practice.
• Nonprofits, healthcare providers, schools, and government agencies all need to register, and some qualify for favorable use-case classifications.

A2P vs P2P: two kinds of text messages

Carriers divide text messaging into two categories, and the distinction determines which rules apply to you.

P2P (person-to-person) is what most people think of as texting: one human tapping out a message to another human from a handset. It is low volume, conversational, and roughly balanced in both directions. Carriers leave this traffic largely alone.

A2P (application-to-person) is any message generated or sent through software on behalf of an organization. Appointment reminders, donation receipts, event alerts, two-way conversations routed through a shared inbox, and automated replies all count. The moment a platform sits between your team and the recipient, carriers classify the traffic as A2P, even if a human wrote every word.

This matters because many organizations assume that low volume or conversational tone keeps them in P2P territory. It does not. Volume and tone are irrelevant; the delivery method is what counts. If you use a texting platform such as FRANSiS, a CRM with texting built in, or any messaging API, you are an A2P sender and registration rules apply.

What 10DLC means and why carriers built the framework

A 10DLC number is a standard local phone number, like the one on your business card, that has been sanctioned by carriers for A2P messaging. Before 10DLC existed, organizations had awkward choices: short codes (five or six digit numbers that are powerful but expensive and impersonal) or toll-free numbers, or gray-route traffic pushed through ordinary local numbers without carrier approval.

That gray-route traffic became a problem. Spammers exploited unregistered local numbers to blast unwanted messages, and carriers responded with aggressive filtering that caught legitimate senders in the same net. The A2P 10DLC framework, rolled out by major US carriers over the past several years, was the fix. It gives organizations a sanctioned way to text from local numbers in exchange for transparency about who is sending and why.

The logic is straightforward: carriers wanted three things.

• Accountability: every message traces back to a verified organization with a legal name and tax ID.
• Consent enforcement: senders must describe how recipients opt in, which gives carriers grounds to shut down bad actors.
• Traffic shaping: verified, trusted senders get better throughput, while unknown senders get throttled or blocked.

For legitimate organizations, the framework is a net positive. Registered traffic on 10DLC numbers is delivered more reliably than unregistered traffic ever was, and recipients see a local number they can reply to rather than an anonymous short code.

The Campaign Registry: the system of record

The Campaign Registry, usually abbreviated TCR, is the central database the carrier ecosystem uses to track A2P 10DLC senders. You generally do not interact with TCR directly. Your messaging platform or its underlying provider submits your information to TCR on your behalf, and TCR shares it with the carriers. You can learn more about the registry itself at The Campaign Registry.

Two concepts drive everything in TCR: brands and campaigns.

Brands: who you are

A brand is your organization's verified identity in the registry. Brand registration captures your legal entity name, EIN (tax ID), address, website, and organization type. TCR verifies this information against public records, which is why the details you submit must exactly match your IRS and state filings. A mismatched EIN or an outdated legal name is one of the most common causes of registration failure.

Brand registration is typically a small one-time fee, and for most organizations verification completes quickly, often within minutes to a few days.

Campaigns: what you send

A campaign describes a messaging use case, not a marketing blast. Examples include appointment reminders, account notifications, two-way customer care, or donation updates. For each campaign you declare the use case category, sample messages, how recipients opt in, and how they can opt out. Campaigns carry a small recurring monthly fee and go through a review process before carriers approve the traffic.

Most organizations need only one or two campaigns. A clinic might register a customer-care campaign that covers reminders, confirmations, and two-way conversation. The campaign description needs to be honest and specific, because vague or mismatched descriptions are the leading cause of rejection. If you hit that wall, this guide to why 10DLC campaign rejections happen and how to fix them walks through the common failure points.

Trust scores and throughput: why registration quality matters

When TCR verifies your brand, it assigns a trust score based on factors like your organization's verifiable history, entity type, and the completeness of your registration. That score is not just a badge. It directly determines your throughput tier: how many message segments you can send per minute and per day across carriers.

The practical effects break down like this:

• Higher-trust brands get higher daily message caps and faster sending rates, which matters for time-sensitive alerts sent to large lists.
• Lower-trust or unverified brands get restrictive caps that can delay or drop messages during a big send.
• Optional secondary vetting is available for organizations that need more throughput than their initial score allows; an independent reviewer takes a deeper look and can raise the score.

For a small nonprofit texting a few hundred supporters, the base tier is usually plenty. For a county agency sending emergency notices or a health system sending thousands of daily reminders, throughput tiers are worth understanding before launch day, not after messages start queuing.

What happens to unregistered traffic

Carriers have moved from encouraging registration to enforcing it. Unregistered A2P traffic on 10DLC numbers now faces several consequences:

• Filtering: carriers silently drop messages they suspect are unregistered A2P. The sender often sees the message as sent while the recipient never gets it.
• Blocking and error codes: providers increasingly reject unregistered traffic outright, returning delivery errors that reference registration requirements.
• Surcharges: carriers apply higher per-message fees to unregistered traffic, so noncompliance costs more even when messages get through.
• Number suspension: repeated violations can get a number, or an entire account, shut off by the platform or the upstream carrier.

The pattern is one-directional: enforcement gets stricter over time, never looser. Organizations that delay registration are betting on delivery rates that are already unreliable and getting worse.

Who needs to register (and nonprofit considerations)

The short answer: any organization that sends text messages through software to US recipients from a 10-digit local number. That includes nonprofits, churches, schools, clinics, local governments, and small businesses. There is no exemption for low volume, for conversational messaging, or for tax-exempt status. A five-person nonprofit sending event reminders through a platform is an A2P sender just like a national retailer.

Nonprofits do get some favorable treatment inside the framework. TCR recognizes registered 501(c)(3) organizations, and qualifying nonprofits may access charity-specific use-case classifications with pricing and vetting paths designed for them. The registration data still has to match IRS records exactly, so have your determination letter and EIN documentation handy before you start.

A good platform handles most of the mechanics for you. FRANSiS, for example, manages TCR submission as part of onboarding so nonprofit and public-sector teams do not have to navigate the registry alone. Whatever platform you use, the step-by-step process, required documents, and timelines are covered in our full 10DLC registration guide. Registration also pairs naturally with broader messaging rules; our SMS compliance checklist covers consent and opt-out requirements that apply alongside 10DLC.

Frequently asked questions

Is A2P 10DLC required by law?

No. A2P 10DLC is a carrier industry requirement, not a statute passed by Congress. However, carriers enforce it through their networks, so it is mandatory in practice for anyone who wants messages delivered. Separate laws like the TCPA govern consent and can carry statutory damages of $500 to $1,500 per message for violations.

Does 10DLC apply to toll-free numbers or short codes?

No. Toll-free numbers have their own separate verification process, and short codes have their own provisioning and approval path. 10DLC rules apply specifically to standard 10-digit local numbers used for A2P messaging. Many organizations choose 10DLC anyway because a local number feels more personal and supports two-way conversation.

How much does 10DLC registration cost?

Brand registration is a small one-time fee, and each campaign carries a small monthly fee. Exact amounts vary by provider and can change, and some platforms absorb or bundle these costs. Ask your messaging provider how fees are passed through before you register.

Can I send texts while my registration is pending?

Sending unregistered A2P traffic while you wait is risky: it faces the same filtering and surcharges as any unregistered traffic. Brand approval is often fast, but campaign review commonly takes days to a few weeks. Plan your launch around the approval, not before it.

What if my organization texts from employees' personal phones?

Texts typed by hand on a personal handset are P2P and outside 10DLC scope. But this approach creates other problems: no record keeping, no opt-out management, and no coverage under privacy rules for regulated industries. Most organizations are better served moving to a registered platform.

Conclusion

A2P 10DLC is the price of admission for reliable business texting in the United States. Register your brand, describe your campaigns honestly, and the framework works in your favor: better deliverability, higher throughput, and a local number your community can actually reply to. Skip it, and carriers will filter your messages no matter how legitimate your mission is.

Ready to get registered and start texting with confidence? FRANSiS handles 10DLC registration as part of onboarding for nonprofits, healthcare, education, and government teams. Talk to the FRANSiS team and get your registration moving this week.