A2P 10DLC Explained for Voice Agent Builders
If your voice agent sends SMS from a standard 10-digit US phone number, A2P 10DLC compliance is part of your stack — whether you know it or not.
If your voice agent sends SMS from a standard 10-digit US phone number, A2P 10DLC compliance is part of your stack — whether you know it or not. The US carriers implemented A2P 10DLC as a gated registration system to reduce spam, and if you're not registered, your SMS deliverability tanks. For voice AI builders, understanding the registration process, the costs, the throughput tiers, and the content rules is practical production knowledge.
TL;DR
- A2P 10DLC = Application-to-Person messaging from 10-digit long-code numbers.
- Required for reliable SMS delivery in the US.
- Registration has two levels: Brand and Campaign.
- Costs: one-time + per-message + monthly fees.
- Without registration: heavy filtering, blocks, low deliverability.
What A2P and 10DLC mean
- A2P: Application to Person. Automated messaging from a business to a person. (Opposite: P2P, person-to-person.)
- 10DLC: 10-digit long code. The standard 10-digit US phone number. (Opposite: short code, 5–6 digit; or toll-free.)
A2P 10DLC = business-sent SMS from 10-digit numbers.
Why it exists
Before A2P 10DLC:
- Businesses used 10-digit numbers to send SMS.
- Spam and fraud proliferated.
- Carriers filtered aggressively, hurting legitimate senders.
- No way to tell legitimate from spam.
Carriers + The Campaign Registry (TCR) built A2P 10DLC as a registration system so:
- Legitimate senders identify themselves.
- Content types are pre-declared.
- Throughput tiers align with verification.
- Spam gets filtered without catching legit traffic.
The two-level registration
Level 1: Brand. Your company. Registered once, covers all your messaging.
Level 2: Campaign. Specific use case. You can have multiple campaigns per brand.
Campaigns are categorized:
- Notifications.
- Customer care.
- 2FA.
- Marketing.
- Mixed.
- Low-volume, standard-volume, high-volume.
The process
Typically via your messaging provider (Twilio, Bandwidth, Telnyx):
-
Brand registration.
- Legal business name.
- EIN.
- Address.
- Website.
- Industry vertical.
- Vetting score assigned (affects throughput).
-
Campaign registration.
- Use case category.
- Sample messages (usually 2–5).
- Call-to-action flow (how users opt in).
- Opt-out handling.
- Volume estimates.
-
Approval. Review period: typically 1–4 weeks.
-
Activation. Campaign tied to specific phone numbers.
Brand vetting
Vetting score is assigned based on business verification depth:
- Unverified: lowest throughput.
- Standard verified: better throughput.
- Enhanced vetted: highest throughput, high-volume tiers.
Enhanced vetting involves third-party verification (Aegis, WMC Global) and costs $30–$75.
Campaign use case categories
Pick the right one:
- Notifications. One-way alerts (appointment reminders, shipping updates).
- Customer care. Two-way customer support.
- 2FA / OTP. Authentication codes.
- Marketing. Promotional content.
- Account notifications. Billing, security alerts.
- Mixed. Multi-purpose.
Category mismatch = rejection or content filtering.
Content rules
Once registered, content is filtered by carriers:
Allowed (with proper registration):
- Transactional messages (order updates, appointment reminders).
- Consent-based marketing.
- Account alerts.
Restricted:
- SHAFT content (Sex, Hate, Alcohol, Firearms, Tobacco) often filtered.
- Loans / financial services — extra scrutiny.
- Political — strict.
- Gambling — strict.
- CBD / cannabis — often blocked.
If your use case is in restricted categories, plan for rejection or additional approval.
Throughput tiers
Based on brand vetting + campaign type:
- Low tier: 10 messages per second per number.
- Medium tier: 40–120 MPS.
- High tier: higher volumes for enhanced-vetted brands.
For most voice agent use cases (a few thousand SMS/day), low-medium is plenty.
Costs
Typical 2026 cost structure:
- Brand registration: $4 one-time.
- Enhanced brand vetting: $40–$75 one-time.
- Campaign registration: $10–$50 one-time + $1.50–$10/month per campaign (varies by use case).
- Per-message: $0.005–$0.01 (on top of carrier fees).
Add to base per-message cost.
Timeline
- Brand registration: instant to a few days.
- Brand vetting (if enhanced): few days.
- Campaign registration: 1–4 weeks approval.
- First message sent: after campaign activated.
Plan ahead. Don't start deployment assuming SMS goes live day 1.
What happens without registration
- Throughput capped hard.
- Messages filtered by carriers.
- Deliverability low (often under 50%).
- Sender reputation damaged — hard to recover.
Don't skip registration.
Re-registration / changes
- New use case? New campaign registration.
- New brand entity? New brand registration.
- Content changes? May trigger re-review.
Manage like any compliance process.
Sample campaign submission
Use case: Customer care (appointment reminders + confirmations).
Sample messages:
- "Westside Dental: Reminder — appointment tomorrow 4/18 10 AM. Reply C to confirm, R to reschedule. STOP to opt out."
- "Westside Dental: Your cleaning is confirmed for 4/18 10 AM with Sarah. STOP to opt out."
Opt-in flow: Patients provide phone + SMS consent on intake form. Stored in EHR.
Opt-out: Reply STOP → immediately removed. Confirmed via return SMS.
Volume: 5,000 messages/month estimated.
Approval path.
Common rejection reasons
- Missing opt-in details.
- Sample messages lack STOP language.
- Use case mismatch.
- Incomplete brand info.
- Restricted content.
Fix and resubmit. Don't treat rejection as final.
Related: toll-free verification
If using toll-free (800-series) numbers for SMS, it's a different (but parallel) verification path.
See setting up toll-free verification for AI calling.
Maintenance
- Annual campaign renewal — typically automatic, paid.
- Volume monitoring — stay under declared.
- Content compliance — stay within declared use case.
Lapsed campaigns = dropped deliverability.
Related reading
- How to Build a Compliant Outbound Voice Agent in 30 Days
- Caller ID and Trust: Why Numbers Get Marked as Spam
- TCPA Compliance for AI-Powered Outbound Calls
- Outbound AI Calling in 2026: A Practical Playbook
- Outbound for B2B: Pipeline, Renewals, and Win-Backs
FAQ
Do we need A2P 10DLC if we only send internally? Person-to-person is different. Person-to-many business messaging = A2P.
Can we use toll-free instead? Yes — different rules (toll-free verification). Often simpler for brands.
What about short codes? Expensive ($500–$1,500/month), slow approval, highest deliverability. For very high volume.
What if we're a nonprofit? Nonprofits register similarly. Content rules apply.
How do we monitor deliverability? Your provider's dashboard. Look for delivery rate, carrier rejections.

Tyler Weitzman is co-founder and Head of AI at Speechify. He has spent the past decade building the speech-synthesis stack that powers millions of users. Tyler writes about the engineering of real-time conversational systems — text-to-speech, speech recognition, latency budgets, model serving, and the architectural choices that separate prototypes from production-grade voice agents.
More from Tyler Weitzman
View all →Open-Source vs Proprietary Voice Agent Stacks
The open-source voice AI stack in 2026 is genuinely good. Whisper and its derivatives handle STT. Open-weight LLMs like Llama 3/4, Qwen, Mistral handle the reasoning. Open-source TTS (XTTS, StyleTTS, Orpheus-class) handles output.
Build vs Buy: When to Build Your Own Voice Agent
Build-vs-buy for voice agents in 2026 is a different conversation than it was two years ago. Then, the open-source stack was rough and most serious deployments ended up building.
Voice Agents for Developer Support
Developer support is a strange category. Developers don't generally want to call anyone. They want Stack Overflow, they want clear docs, they want an LLM that can read their code.
Related reading
How to Build a Compliant Outbound Voice Agent in 30 Days
Getting an outbound AI voice agent live in 30 days sounds ambitious — but it's achievable for focused deployments. The critical path is compliance setup (TCPA, A2P 10DLC, number verification), not technology. The voice AI itself can be configured in a week.
Caller ID and Trust: Why Numbers Get Marked as Spam
You deploy an outbound voice AI campaign. First week goes great. Second week, answer rates drop 40%. Third week, your phone numbers start showing up as "Scam Likely" on caller ID. What happened?
TCPA Compliance for AI-Powered Outbound Calls
TCPA — the Telephone Consumer Protection Act — is the federal law that governs automated and pre-recorded outbound calls in the United States. AI-generated voice calls fall squarely under TCPA's stricter rules for "artificial or prerecorded voice" messages.
Voice AI, twice a month.
Get the best of the SIMBA resources hub — new articles, trend notes, and operator guides. No spam.
