A2P 10DLC in 2026: What Changed, What SMBs Actually Need to Know

Short version: if your business SMS is suddenly hitting throughput limits, getting flagged for vetting, or returning 30007 carrier blocks, you've landed in the same place every SMB does at some point in 2026. Here's the honest map of A2P 10DLC: what it is, what tightened in 2024-2025, what your provider handles on your behalf, and what's still your responsibility no matter who you pick.

What A2P 10DLC actually is

A2P stands for Application-to-Person — messages sent from a software platform (your CRM, your SMS provider, a marketing tool) to a real human's phone. 10DLC stands for 10-Digit Long Code — a regular US/Canada phone number, the same shape as the one in your pocket. Put them together: A2P 10DLC is the regulated channel for businesses to send SMS to consumers using ordinary phone numbers.

Before 2021 there was no such regulated channel. Businesses sent SMS from long codes and short codes through a mostly-unregulated path that carriers tolerated more than approved. Spam grew, complaints grew, and carriers responded by mandating registration — every business sending A2P SMS now has to be vetted and registered before their messages will reliably deliver. The Campaign Registry (TCR) is the central database carriers query at message-send time to decide whether to deliver, throttle, or block.

The model has three layers, in order:

• Brand: your business, registered with legal name, EIN, address, website, vertical. One brand per legal entity.
• Campaign: a specific use case — "appointment reminders for medical practice," "marketing promos for retail," "lead-response for real estate." Each campaign has approved sample messages and an opt-in flow.
• Phone numbers: assigned to a campaign. A number can only carry traffic for the campaign it's registered to.

When your provider sends a message, the carrier checks: is the sending number assigned to a registered campaign? Is that campaign approved? Does the message content match the campaign type? If any answer is no, the message gets blocked (and you'll see a 30007 error code in your logs).

What changed in 2024-2025

The system existed in rougher form back in 2021-2023, but the past 18 months tightened it significantly. The shifts that actually matter for SMBs in 2026:

TCR vetting got stricter

Brand registrations that would have been approved in 2022 now get rejected, partially because the carriers started catching the obvious problems (mismatched EIN to legal name, addresses that don't match Secretary of State filings, websites that don't reference the brand at all) and partially because external vetting firms (Aegis, CMTrust) got more aggressive about what they'd attest to.

If you're seeing your brand registration rejected, the usual culprits are: (a) the legal name you submitted doesn't exactly match your EIN registration, (b) your address doesn't match your business filings, (c) the website on your registration doesn't have your business name prominently visible, or (d) your privacy policy doesn't disclose how phone numbers are collected and used.

Trust Score replaced the binary "approved/not approved"

The Campaign Registry assigns each brand a Trust Score (0-100) based on vetting depth, business age, EIN type, and external attestation. Your trust score determines:

• Throughput cap — how many messages per second (MPS, also written TPS) you can send
• Daily message cap — per-campaign, per-carrier
• Vetting requirements for higher-volume campaigns

A trust score in the high 70s+ unlocks the highest carrier tiers. A score in the 30s-50s caps you at low throughput regardless of your traffic patterns. External vetting (paying $40-100 for an Aegis or CMTrust review) typically pushes trust scores up 10-25 points.

The Sole Proprietor tier matured

Originally introduced 2023, refined in 2024, the Sole Proprietor tier is for genuine single-person businesses without an EIN — freelancers, independent consultants, solo practitioners. Lower registration cost, lower throughput cap (roughly 1 message per second), and simpler vetting that uses personal identity rather than EIN-backed business identity.

Where it works: a solo real-estate agent, a one-person consulting practice, a freelance graphic designer who sends appointment reminders. Where it doesn't: any organization with employees. If you have a payroll, you have a business, and the standard tier applies. Carriers have gotten more aggressive about catching abuse here — registering as Sole Proprietor when you have staff is increasingly a path to having your brand frozen.

T-Mobile's pass-through fees increased in 2024

Carriers have always charged a per-message fee on A2P traffic. T-Mobile's 2024 increase notably bumped the cost-per-message at the carrier level, which providers pass through to you (some bake it into bundled rates; others charge separately as a "carrier fee" line item). For high-volume senders, the practical impact is a 15-25% increase in per-message cost on T-Mobile traffic compared to 2023.

30007 became more common — and more aggressive

Error code 30007 — "Carrier Violation" — fires when a message's content matches a carrier-side filter. Common triggers in 2026: financial-services language (loans, debt, "approved"), SHAFT content (sex/hate/alcohol/firearms/tobacco/gambling — even if state-legal), URL shorteners that have been abused (bit.ly, tinyurl, etc.), and certain phrases that match phishing templates. The filters are opaque — carriers don't publish their rule sets — and they update without notice. If you're seeing 30007s on previously-fine content, your provider is your best diagnostic resource because they see industry-wide patterns.

The four registration tiers (and which one you actually need)

Three of the four most SMBs ever interact with:

1. Standard (low-volume) — the default tier for most SMBs. Brand registered with EIN, single campaign or a few related campaigns, throughput up to ~75 MPS depending on trust score. Setup: brand reg ~$4/mo, campaign reg ~$10/mo per campaign, plus carrier fees per message. This is what almost every Texter customer falls into.
2. Standard (high-volume) — same registration shape but requires external vetting (Aegis or CMTrust) for the higher throughput tiers. Useful if you're sending 50K+ messages/day and need 100+ MPS sustained. The vetting cost is real ($40-100) but pays for itself in throughput.
3. Special use case — for charities (501c3), public-utility messaging (school districts, government), emergency notifications. Different campaign type, often reduced fees, sometimes elevated throughput. Most SMBs don't qualify and shouldn't try to.
4. Sole Proprietor — described above. Single-person business, no EIN, lower throughput cap. Real and useful for the right shape of business; over-claimed and the carriers are tightening.

What your SMS provider should be handling

The whole point of using a managed platform like Texter (or SimpleTexting, EZTexting, TextMagic, SlickText — see our compare pages for the rest) is that the provider handles the operational complexity of A2P 10DLC for you. What that should specifically mean:

• Brand registration with TCR — submitting your business info, paying the registration fee, monitoring the trust score
• Campaign registration — drafting the use case, sample messages, opt-in language; submitting and resubmitting on rejection
• Phone number assignment — provisioning numbers and linking them to your campaign at the carrier level
• Trust score monitoring — flagging when your score drops, helping you remediate
• Carrier fee handling — collecting the pass-through fees, showing them on your invoice line-item or bundling them transparently
• Vetting submission — if you need higher throughput, submitting to Aegis or CMTrust on your behalf
• 30007 diagnostics — when your content gets blocked, telling you which trigger fired and how to revise

If your provider isn't handling these, you're effectively running an unmanaged 10DLC operation, which is the operational shape that drove most SMBs to managed platforms in the first place.

What's still your responsibility — even with the provider handling registration

This is the part that catches every SMB once. Your provider can submit your registration, but they can't fix bad inputs. The things that have to be right and that nobody else can fix for you:

• Legal business name matching your EIN exactly — including "LLC" vs "L.L.C." vs "Inc." spelling, and any registered DBA. A mismatch here is the single most common rejection cause.
• Business address matching state filings — Secretary of State, not just your office address
• Website with your business name visible — the carrier vetting bot literally looks at your site and tries to find your brand name. If you're a doctor and your site says "Dr. Smith Family Practice" but your registration says "Smith Medical PLLC," that's a flag.
• Privacy policy that discloses SMS data collection — language like "we collect phone numbers for appointment reminders and marketing" or similar. Generic boilerplate gets flagged.
• Sample messages that match your campaign description — if your campaign is "appointment reminders," your samples need to be appointment reminders, not a mix of reminders and marketing
• Opt-in language and records — what does the user actually agree to when they sign up? You should be able to produce the exact wording on demand. See our HIPAA guide for the parallel rules on healthcare opt-in.
• Volume forecasting — over-shooting your tier gets you throttled or rejected. If you go from 1,000 messages/day to 50,000/day overnight, expect carrier filters to fire.
• SHAFT compliance — even when content is state-legal. Cannabis is legal in California; cannabis SMS marketing is still SHAFT and still blocked by carriers. Same for alcohol delivery, firearms, gambling, etc. The state-vs-federal distinction doesn't help you here; the carrier is the gatekeeper.

The error codes you'll actually see — and what they mean

If you live in the operational side of SMS, these error codes will become your friends. Bookmark this section.

• 30001 — Queue overflow. You're sending faster than your throughput tier allows. The message will likely retry, but if you're sustained-over-cap, expect drops. Fix: pace your sends, or upgrade your tier with external vetting.
• 30003 — Unreachable destination handset. The recipient's phone is off, out of coverage, or has a problem. Retries will deliver eventually if the issue is temporary.
• 30004 — Message blocked. Generic carrier block. Often spam filter, sometimes campaign-mismatch.
• 30005 — Unknown destination. The number has been deactivated, ported with porting issues, or never existed. Time to clean it from your list.
• 30006 — Landline or unreachable carrier. You sent SMS to a landline (which can't receive it) or to a carrier your provider can't reach. Clean the list.
• 30007 — Carrier violation. Content matched a carrier filter (covered above). This is the one that requires real diagnosis.
• 30008 — Unknown error. Often vetting-related — your brand or campaign is in a strange registration state. Your provider has to dig in.
• 30032 — Toll-free verification required. Different system entirely — see the toll-free section below.

Throughput tiers in 2026 — current numbers

Approximate per-second throughput by trust score (varies slightly by carrier and provider):

• Trust score 75-100, externally vetted: 75+ MPS — high-volume marketing, large notification fleets
• Trust score 60-75: ~40 MPS — established SMBs with vetting
• Trust score 40-60: ~25 MPS — typical SMB, no external vetting
• Trust score under 40: ~10 MPS — newer brands, lower vetting
• Sole Proprietor: ~1 MPS — single-person businesses

These numbers shift periodically as carriers tune. If you're sending high volume, your provider should be telling you your current trust score and what it would take to move up a tier.

Toll-free SMS vs 10DLC — when to use which

Toll-free SMS is a different system and is often confused with 10DLC. Quick map:

• 10DLC — uses regular 10-digit phone numbers. TCR registration. Campaign + brand model. Carrier per-message fees. The default for most SMB SMS use.
• Toll-free SMS — uses 8XX numbers. Different verification process called Toll-Free Verification (TFV). No carrier per-message fees in the same shape. Higher throughput in some cases. Often used for high-volume transactional/notification work where the recipient won't recognize the number anyway.

The honest framing for most SMBs: use 10DLC unless you have a specific reason for toll-free. The 10-digit number is more trustworthy to recipients (it can be a local-area-code number, looks like a person), conversational replies work cleanly, and the regulatory shape is now well-understood. Toll-free is for cases where the recipient relationship is heavily transactional (bank notifications, healthcare appointment reminders for large hospital systems) and conversational reply isn't expected.

The honest framing: A2P 10DLC is necessary but not sufficient

Registering correctly avoids carrier blocks. That's necessary. It does not automatically mean:

• Your messages won't be flagged. Even with perfect registration, content filters fire on certain patterns. Good practices on content help; registration doesn't substitute.
• You're TCPA/DNC compliant. A2P 10DLC is a carrier-side regulatory layer. TCPA is a federal consumer-protection statute, separate. DNC is the federal Do Not Call list, also separate. You can be carrier-compliant and TCPA-noncompliant simultaneously — and the TCPA exposure is the bigger financial risk ($500-$1,500 per violation, class-actionable).
• You're meeting HIPAA requirements. If you're handling PHI in SMS, A2P 10DLC registration is a prerequisite, not a substitute, for HIPAA — see our HIPAA-compliant texting guide for what's actually required there.
• You can ignore opt-in/opt-out hygiene. STOP must work. HELP must respond. Opt-in records must be preserved. None of that is in the 10DLC layer.

What Texter handles vs what you do — concrete split

For full transparency on the operational shape:

Texter handles, on your behalf:

• Brand registration submission to TCR and follow-through
• Campaign drafting and submission (with your input on use case and sample messages)
• Phone number provisioning and campaign assignment
• Trust score monitoring; alerts if it drops
• External vetting submission (when you need higher throughput)
• Carrier fee billing — bundled monthly, no surprise line items
• 30007 diagnostics — when a content filter fires, we tell you which trigger and how to revise
• Toll-free verification submission (if your use case fits toll-free)
• A2P 10DLC compliance updates as carrier rules change

You handle:

• Accurate business info (legal name, EIN, address, website)
• Privacy policy with explicit SMS-data-collection language
• Opt-in records (we provide the tooling; you preserve the records)
• STOP/HELP responses (we wire these into your templates; you're responsible for honoring them)
• Volume forecasting (we can advise; you decide your send pace)
• SHAFT compliance review on your content
• TCPA + DNC compliance on your underlying consent flows (we ship the compliance plumbing; the legal posture is yours)

The same operational split applies whether you pick Texter or any other managed platform — see our vs Twilio, vs SimpleTexting, vs EZTexting, vs TextMagic, or vs SlickText pages for the platform-by-platform comparison. Twilio runs at the API layer (more configurability, more of the work falls on you); the others run at the application layer (more handled for you, less knob-turning required).

Bottom line

A2P 10DLC isn't going away and isn't getting simpler. The 2024-2025 tightening is the regulatory shape this stays at for the foreseeable future, with periodic carrier-policy updates layered on. The practical implications:

• Get your brand info right at registration time. The cost of fixing a bad brand registration later is real.
• Match your campaigns to your actual use cases. Don't register one campaign and send four use cases through it.
• If you're sending high volume, get external vetting. The cost is trivial compared to the throughput unlock.
• Watch your error codes. 30007 is the one that requires content thinking; the others are mostly operational hygiene.
• Pick a managed platform unless you have a specific reason to run unmanaged. The complexity has crossed the threshold where DIY isn't worth the engineering cost for most SMBs.

For the parallel compliance posts on top of A2P 10DLC: our HIPAA-compliant texting guide covers the healthcare-specific overlay, and our automated SMS workflows guide covers the operational patterns that turn raw send capacity into actual customer outcomes.