A2P 10DLC for AI SMS in 2026: Brand, Campaign, and Carrier Reality

If your AI voice agent sends a single SMS confirmation to a US mobile number, you are doing application-to-person messaging. As of February 2025 the US carriers block all unregistered 10DLC traffic outright, and in August 2025 The Campaign Registry added a new "Authentication+" tier for public companies. This is the 2026 reality.

What the rule says

flowchart LR
  Phone["PSTN caller"] --> Carrier["Carrier"]
  Carrier -- "SIP INVITE" --> SBC["Session Border Controller"]
  SBC -- "SIP" --> PBX["Twilio / Asterisk"]
  PBX -- "RTP · Opus" --> Bridge["AI Voice Gateway"]
  Bridge --> AI["OpenAI Realtime"]
  AI --> Bridge
  Bridge --> PBX

A2P 10DLC is the framework US carriers (AT&T, T-Mobile, Verizon) jointly enforce through The Campaign Registry (TCR) for application-to-person SMS sent over standard 10-digit long codes. Every business sending A2P traffic must register a Brand (the legal entity), at least one Campaign (use case, sample messages, opt-in URL, expected volume), and link both to the phone numbers used to send. Since February 2025, carriers block unregistered 10DLC traffic at the network level rather than rate-limiting it. In August 2025 TCR introduced Authentication+ as an optional deeper-vetting tier for public companies, and reseller-ID disclosure became mandatory when a platform registers on behalf of a client.

What it means for AI voice agent operators

If your voice agent sends an appointment-confirmation text, a call-summary recap, or a booking-link follow-up after a call, every one of those messages is A2P SMS. Three things matter for AI builders specifically:

First, your opt-in URL must be live and carrier-verifiable. Vetters click it. A 404 or login wall will reject the campaign. Your privacy policy must explicitly list "you may receive SMS related to your appointments and account" and disclose that messages may be initiated by automated systems.

Second, sample messages must match what your agent actually sends. If your AI confirms appointments, send the vetter a real confirmation example, not a placeholder. Mismatched samples are the most common rejection reason after EIN errors.

Third, throughput is tied to your campaign tier. Standard brand + low-volume mixed campaign caps at roughly 75 messages per second across the carrier set; vetted high-volume campaigns push that ceiling higher. Provision early; vetting and approval take 2-3 weeks for standard brands, longer if the EIN is fresh.

How CallSphere stays compliant

CallSphere uses Twilio across all six verticals (Healthcare AI, Real Estate AI, Sales Calling AI, Salon AI, IT Helpdesk AI, After-Hours AI), and Twilio's Trust Hub orchestrates A2P 10DLC registration on every customer's behalf. New tenants register a Brand under their EIN through the onboarding flow; we file at least one Campaign per use case (appointment reminders for Healthcare, lead nurture for Sales, on-call alerts for After-Hours), and the resulting messaging service is automatically attached to numbers we provision. We disclose AI-generated content in the privacy policy text and ship sample messages that mirror live traffic. The Sales product caps outbound at five concurrent calls per tenant on Twilio with TCPA opt-out wired into the conversation flow. With 6 verticals running across 50+ businesses at a 4.8/5 rating and a 14-day trial, the registration playbook is well-worn.

Compliance checklist

1. Register a Brand in TCR under your legal entity EIN (must be at least 15 days old).
2. File one Campaign per distinct use case; do not lump marketing and account notifications together.
3. Make your opt-in URL publicly reachable, no auth wall, and link to it from the privacy policy.
4. Include explicit SMS consent language at the point of opt-in: business name, message types, frequency, "Msg & data rates may apply", and STOP/HELP keywords.
5. Honor STOP within seconds and HELP with a configured response; log both events.
6. Do not send marketing content on a transactional campaign or vice-versa.
7. If you are a platform sending on behalf of customers, populate the Reseller ID field in TCR.
8. For public companies, complete Authentication+ for the lower-cost trust tier ($12.50).
9. Disclose AI-initiated SMS in the privacy policy and at opt-in.
10. Keep an audit log of opt-ins (timestamp, IP, source, language) for at least four years.
11. Scrub against the National DNC for marketing text, even though the registry is voice-first.
12. Re-vet campaigns annually; carriers re-flag stale registrations.

FAQ

Does my AI voice agent need 10DLC if it only does voice, no SMS? No. 10DLC governs A2P SMS over 10-digit US long codes. If you never send a text, you do not need a campaign. The moment you send a confirmation text, you do.

Can I use a toll-free number to skip 10DLC? Toll-free SMS has a parallel verification process (TFV) with similar rules but different throughput tiers. It is not a loophole; it is a different lane.

Is short code an option? Yes, but short codes cost roughly $1,000+/month and take 8-12 weeks to provision. They make sense for high-volume marketing, rarely for AI receptionist use cases.

What if my opt-in is a phone call, not a web form? You can capture verbal opt-in during the AI call. Record the consent, log the timestamp and recording URL, and disclose the same information you would on a web form. Send the link to your privacy policy via the first SMS.

How long does registration take? Standard brand vetting is 1-3 business days; low-volume campaign approval is typically 1-2 days; high-volume vetted campaigns can take 2-3 weeks.

Sources

• Twilio: Programmable Messaging and A2P 10DLC
• The Campaign Registry: Brand and Campaign Registration
• FCC: Robocall and Robotext Mitigation

Start a 14-day trial with 10DLC pre-wired, see pricing for 1, 3, or 10 numbers, or contact us about Brand registration help.