A2P 10DLC is the framework US carriers use to govern application-to-person SMS sent from regular 10-digit phone numbers. If your AI agent texts customers from a normal-looking phone number (versus a short code like 5-6 digits), you are operating under A2P 10DLC rules. The rules matter because they determine whether your messages reach the customer at all (or get filtered as spam by the carrier), what you can charge per message, and what your monthly carrier fees are.
This post is the working version. We will cover what the rules require, why the carriers care, what trust scores actually mean, and how Ajeris handles compliance so your agent's messages reach the customer.
What A2P 10DLC actually is
The acronym: Application-to-Person, 10 Digit Long Code. It is the formal framework all major US carriers (T-Mobile, AT&T, Verizon and their MVNOs) adopted in 2021-2023 to govern non-person-to-person SMS traffic on regular phone numbers.
The motivation, in plain English: SMS spam from automated senders was destroying the inbox. Carriers needed a way to distinguish "Mary texts her sister" from "an automated marketing system texts a million numbers it bought." Short codes (5-6 digit numbers) were the original automated-traffic surface, but they are expensive ($1,000+ per month) and hard to provision. 10DLC let businesses use regular phone numbers for automated messaging, with rules attached.
What the rules require
Three layers of requirement.
- 1Brand registrationVerify your business identity with The Campaign Registry (TCR).
- 2Campaign registrationPer use case (transactional, marketing, customer care, 2FA), register with sample messages.
- 3Number provisioningBind your phone number(s) to the registered campaign(s).
- 4Ongoing complianceHonour STOP/HELP/UNSUBSCRIBE replies, keep consent records, monitor opt-out rates.
Each layer takes time. Brand registration is typically 1-3 days. Campaign approval depends on the use case (transactional approves fastest, marketing slowest). Most businesses self-running this go through the same setup at various levels of speed and pain.
What the trust score means
Brands get a TCR trust score (0-100 typically) based on the verification depth, the brand's history, and the registered use cases. The score determines how much message throughput your numbers get. A high-trust brand can send 10,000+ messages per minute; a low-trust brand might be capped at 60.
For most small businesses sending under 1,000 messages a day, the throughput cap rarely matters. For businesses doing time-sensitive bulk messaging (election campaigns, large customer-service blasts), the trust score becomes a planning constraint.
The score is not gameable. Carriers do background checks. Pretending to be a Fortune 500 when you are not gets caught and downgrades you.
What happens if you do not comply
A few honest failure modes.
Filter-and-drop. Non-compliant traffic gets filtered by the carrier. Your messages "send" successfully from your perspective but never arrive at the user. The user thinks you ghosted them. You think your tool is broken. Both sides lose.
Surcharge fees. Non-registered or non-compliant traffic is surcharged at higher per-message rates. The economics get worse silently.
Number reputation damage. Repeated non-compliance can mark your number as a problem. Even after you fix the registration, the reputation lag is real. Some businesses have to switch numbers entirely after a long non-compliance period.
Customer complaints to carrier. A customer who reports your messages as spam (regardless of whether they are spam) feeds carrier signals that lower your trust score. Your downstream throughput suffers.
How Ajeris handles compliance
Three layers, mostly invisible to you.
Brand + campaign registration during setup. When you provision an Ajeris business agent, the wizard collects the information TCR needs (legal entity, EIN, use case description, sample messages). We submit it on your behalf. You wait the 1-3 days for approval; we shepherd it.
Use-case mapping per message type. Different messages fit different use cases. A 2FA code goes through the 2FA campaign; a customer service reply goes through the CS campaign; a marketing message goes through marketing. The agent picks the right campaign per message; you do not configure this manually.
Compliance enforcement at send time. The agent honours STOP/HELP replies automatically. It respects TCPA quiet hours (8am-9pm local time). It maintains a per-customer opt-in/opt-out ledger. It does not send marketing messages to customers who opted out. These are infrastructure-level guarantees, not features you have to remember to use.
What you can ignore
The boring engineering stuff:
- Provisioning the carrier connection.
- Maintaining the brand record at TCR.
- Submitting new campaigns when you add use cases.
- Throttling outbound to stay under per-minute carrier caps.
- Handling delivery webhooks for compliance auditing.
You do not have to think about any of this. The agent's text-message infrastructure is set up so the rules are enforced automatically.
- Register your brand with TCR.
- Submit campaigns. Wait for approval.
- Configure your provider's compliance hooks.
- Maintain opt-in records, monitor opt-out rates.
- Pivot when carrier rules change.
- 5-minute setup wizard collects what TCR needs.
- We submit + shepherd approval.
- Compliance hooks are baked in.
- Opt-in records are kept automatically.
- Carrier rule changes are absorbed by us; you keep going.
Frequently asked
Does this matter outside the US?
What about toll-free numbers?
Can I use a personal phone number?
What happens if my campaign gets rejected?
Can I see my trust score?
Try it
You probably do not need to know more than this post for daily operation. The compliance work happens behind the scenes; the agent texts customers, the messages land, the rules are honoured. If you are migrating from another tool that did not handle this, the difference is that your messages start arriving reliably again.
