If your AI chatbot texts customers from a regular US 10-digit number, it needs A2P 10DLC registration. You register your business as a brand and your use case as a campaign with The Campaign Registry (TCR), usually through your messaging provider, and carriers then let that traffic through at a set throughput. Skip it and messages get filtered, blocked or surcharged.

What is 10DLC and why does it apply to AI bots?

10DLC means "10-digit long code", an ordinary local number used for application-to-person (A2P) messaging. US carriers require every business sending A2P texts on these numbers to register. An AI chatbot is A2P traffic even when it is only replying to customers who texted first, because software is sending the messages on behalf of a business.

The alternatives have their own processes: toll-free numbers need toll-free verification, and short codes are leased and approved separately. Our SMS AI agents for business overview compares them.

What are the brand types?

Twilio's A2P 10DLC documentation lists three brand types:

Brand type Tax ID needed Campaigns per brand Daily volume to T-Mobile Best for
Sole Proprietor No 1 1,000 segments (about 3,000 across carriers) Hobby projects, testing
Low-Volume Standard Yes Up to 5 Up to 2,000 Small businesses
Standard Yes Up to 5 (more with reason) 2,000 to unlimited, by Trust Score Production agents

Twilio also warns that campaigns may be rejected in manual vetting when one Tax ID is used for more than five Standard or Low-Volume Standard brands, which matters for agencies registering clients.

How do you register, step by step?

  1. Create a business profileLegal name, EIN, address, website and authorised contact in your provider's console.
  2. Register the brandChoose Sole Proprietor, Low-Volume Standard or Standard; Standard brands get secondary vetting and a Trust Score.
  3. Create the campaignPick a use case, write the description, add sample messages and describe the opt-in flow.
  4. Configure keywordsProvide opt-in, opt-out and HELP keywords and the exact replies.
  5. Link numbersAttach your numbers (or Messaging Service) to the approved campaign.
  6. Test and monitorSend real test messages and watch delivery errors after approval.

Review times vary and Twilio's overview page does not commit to one; plan for days to a few weeks, and longer if a campaign is rejected and resubmitted.

How should you describe an AI chatbot in the campaign?

There is no AI-specific campaign type. Twilio's A2P 10DLC docs list Standard, Low-Volume Mixed and Special categories; an AI agent registers under an ordinary use case and describes the AI in the campaign description. Reviewers want to know what messages people will receive and why they agreed to them. For an AI agent, that means:

  • Use case: pick the one that matches the bot's job, such as customer care, account notifications or appointment reminders. If it does several things, a mixed use case may fit better than forcing one label.
  • Description: say plainly who sends the messages, who receives them and that replies are generated by an AI assistant. Example: "Acme Dental sends appointment confirmations and answers patient scheduling questions by text. Replies are generated by an AI assistant with staff handoff on request. Patients opt in when booking online."
  • Sample messages: two to five realistic examples, including the brand name and opt-out language. Write them as the bot would actually write them, not as marketing copy.
  • Opt-in flow: describe exactly where consent is collected (web form, checkout checkbox, keyword) and provide a screenshot or public URL showing the consent wording.

What opt-in, STOP and HELP details do reviewers check?

The CTIA Messaging Principles underpin most carrier vetting. Key points for an AI bot:

  • Opt-in confirmation. For recurring messages, send a confirmation that includes the program name, customer care contact or HELP instructions, how to opt out, message frequency, and fee language such as "Msg & data rates may apply".
  • Opt-out. Use standard STOP wording, but also act on plain-language requests like "please opt me out". Send one final confirmation, then nothing more.
  • Privacy policy. Keep a clear, public privacy policy and do not share opt-in data with third parties.
  • Record keeping. CTIA suggests storing the consent timestamp, method, the wording shown, the campaign, IP address and phone number.

Handle these keywords in code before the LLM sees the message. Our opt-in and opt-out rules guide covers the FCC's 2026 changes in detail, and TCPA rules for AI texting covers consent law.

What does 10DLC cost?

Fees below come from Twilio's help centre, as of 2026 (Twilio raised them after TCR increased its fees on August 1, 2025). We could not re-check them in November 2026 because the help article only loads in a browser, so confirm them in your console. Other providers pass through similar TCR and carrier charges.

Sole Prop or Low-Volume Standard brand (one-time)
$4.50
Standard brand incl. secondary vetting (one-time)
$46
Campaign vetting (one-time)
$15
Campaign fee ($2 for Sole Prop)
$1.50–$10/mo

Messages are billed on top: about $0.0083 per segment on Twilio plus carrier fees of roughly $0.0025 to $0.007 per message, as of November 2026. Our SMS AI agent costs guide puts these together. For the full fee list with first-year examples, see 10DLC fees for an AI texting agent, and if you are weighing a toll-free number instead, see toll-free vs 10DLC for an AI agent.

Why do AI chatbot campaigns get rejected?

The common reasons we found in Twilio's vetting guidance and CTIA rules are not AI-specific:

  • A description too vague to tell what messages people will receive.
  • Sample messages missing the brand name or opt-out language.
  • An opt-in flow reviewers cannot see (for example, behind a login with no screenshot).
  • A website that does not match the brand, or no privacy policy.
  • Content in restricted categories, or a use case that does not match the samples.

For AI bots specifically, be explicit that the bot answers inbound questions or sends specific notifications, and that it does not send unsolicited messages.

Bottom line

Register before you build anything customer-facing. Describe the bot honestly, show reviewers exactly where consent happens, put STOP and HELP in deterministic code, and keep the model's output inside the use case you registered. Then follow our Twilio build tutorial to wire up the agent itself.