10DLC registration: a plain-English guide

If you text customers from a regular local business number through any kind of software, you’ve probably been asked to “register for 10DLC.” For many small businesses that request arrives as a form full of unfamiliar fields, followed by a rejection email nobody understands.

This post explains what A2P 10DLC is, who runs it, what you register, what reviewers look for, and how to avoid the most common rejections. This is general information, not legal advice. Details vary by provider and change over time, so check your texting provider’s current documentation as you go.

What A2P 10DLC is

Break the name into parts:

• A2P is application-to-person: messages sent by software or a business system to a person, as opposed to one person texting another from their phone.
• 10DLC is a 10-digit long code: an ordinary US phone number, as opposed to a five- or six-digit short code or a toll-free number.

Twilio’s documentation describes A2P 10DLC as “the standard that United States telecom carriers have put in place” for this kind of traffic, and says “anyone sending SMS/MMS messages over a 10DLC number from an application to the US must register,” including individuals and hobbyists (Twilio). Toll-free numbers and short codes sit outside this system.

Why carriers want this: registration lets them see who is sending and what, before the messages arrive. Twilio says registering results in “lower message filtering and higher messaging throughput.”

Who’s involved

Four parties show up in most registrations:

Party	Role
Your business (the brand)	The sender customers see
Your texting provider (a campaign service provider, or CSP)	Submits your brand and campaigns and connects your numbers
The Campaign Registry (TCR)	The central registry for 10DLC brands and campaigns
Mobile carriers	Review, approve and filter traffic based on the registration

The Campaign Registry describes itself as “the backbone support for the 10DLC messaging ecosystem” and says brands and CSPs “are verified prior to being allowed to send messages.” Importantly for small businesses, TCR says direct registration with TCR is not available for brands: you register through a CSP, which records your brand and campaigns (The Campaign Registry).

In practice, that means you fill in your provider’s forms, and the provider handles the submission.

Step 1: register your brand

Your brand is your business identity. For a standard business, Twilio asks for details such as (Twilio):

• the exact legal business name as registered with your EIN,
• business type (corporation, LLC, partnership, non-profit and so on) and industry,
• your EIN in the standard format,
• a live website related to the business name,
• an authorized representative’s name, title, phone and email,
• your mailing address, and
• a business contact email used for verification.

Brand types

Twilio offers three brand types, with different limits (Twilio):

Brand type	Who it’s for	Limits Twilio lists
Sole Proprietor	No EIN or other tax ID	One campaign per brand; 1,000 SMS/MMS segments a day to T-Mobile (about 3,000 across US carriers)
Low-Volume Standard	Businesses with a tax ID and low volume	Up to five campaigns; up to 2,000 segments a day to T-Mobile (about 6,000 across carriers)
Standard	Businesses with a tax ID	Up to five campaigns unless there’s a valid business reason; 2,000 a day up to unlimited to T-Mobile, depending on Trust Score

Twilio also notes that sole proprietors who do have a tax ID should register as a Standard or Low-Volume Standard brand instead. A lawn care owner texting a few dozen customers a day would likely fit Low-Volume Standard; a roofing company running large reminder programs might need Standard. Other providers may name or structure these differently.

Step 2: register your campaign

A campaign describes what you’ll send and how people agree to receive it. Twilio’s campaign fields include (Twilio):

Field	What to write
Use case	The category that matches your messages, such as marketing, 2FA or mixed
Description	Who is sending, who receives the messages and why (40–4,096 characters)
Message flow	Every way people opt in, with links to the form and your privacy policy if it’s on a website
Sample messages	Two to five realistic examples that name your brand, with variable content in [brackets]
Embedded links and phone numbers	Whether your messages contain them
Opt-in, opt-out and help messages	What people receive when they join, reply STOP or ask for HELP

Twilio notes that special use cases need extra approval.

A good campaign description

Weak: “We send messages to customers.”

Better: “Ridgeline Roofing sends appointment confirmations, reminders, quote notifications and replies to customer questions to homeowners who request an estimate on ridgelineroofing.com and check the SMS consent box. Messages are sent by our office staff and scheduling system.”

A good message-flow description

Explain exactly how consent happens: “Customers opt in by checking an optional, unchecked SMS consent checkbox on our estimate request form at [URL]. The disclosure next to the checkbox names Ridgeline Roofing, describes the messages, states that message frequency varies and that message and data rates may apply, and explains how to reply STOP and HELP. Privacy policy: [URL].”

That lines up with what the CTIA Messaging Principles and Best Practices say a call-to-action should include: the program description, the number messages come from, who is sending, clear opt-in language and fees, and terms such as how to opt out and the privacy policy (CTIA). For collecting and storing consent, see SMS consent management.

What reviewers check

Reviewers are trying to answer three questions: is this a real business, does the campaign match what it says, and can people opt in and out properly? Concretely, they look at whether:

• the legal name and tax ID match official records,
• the website is live, belongs to the business and has a public privacy policy,
• the description, use case and sample messages agree with each other,
• the opt-in method is clear and verifiable, and
• the content is allowed.

Common rejection reasons (and fixes)

Twilio’s documentation lists common rejection reasons (Twilio):

Problem	Fix
Website unreachable, parked, for sale, behind a login or redirecting elsewhere	Publish a real, public site on your business domain
Privacy policy behind a login or missing a statement that mobile numbers aren’t shared	Make it public and say mobile numbers aren’t shared; include message frequency and “Message and data rates may apply”
Terms hosted off your domain or not public	Host them publicly on your business domain
Personal, free or distribution-list brand contact email	Use a business address
Business name or tax ID mismatch	Use the name exactly as it appears on your EIN letter; newly issued EINs can take 30–90 days to be recognized
Description doesn’t match the use case	Rewrite so the description, use case and samples tell the same story

Twilio’s campaign troubleshooting page adds three more fixable rejections: an invalid or vague campaign description, sample messages that are missing or don’t match the use case, and a public URL shortener in sample messages. For the last one, Twilio recommends a dedicated, branded short domain. It also recommends editing and resubmitting a rejected campaign rather than deleting it, which avoids a second vetting fee. Some rejections, such as prohibited content or high spam or fraud risk, can’t be fixed by rewording (Twilio).

CTIA’s guidelines take the same line on links: where a URL shortener is used, it should be one dedicated to the sender’s exclusive use (CTIA).

What happens if you don’t register

Unregistered business texting from 10DLC numbers doesn’t quietly work forever. Twilio says customers sending unregistered traffic from a Twilio 10DLC number “will receive additional carrier fees” (Twilio), and its error documentation says Twilio blocks messages to US numbers sent from a 10DLC number “that is not associated with an approved A2P 10DLC Campaign” (Twilio).

If you need to text before registration is approved, Twilio suggests a sender type outside A2P 10DLC, such as a toll-free number or a short code, or Twilio Verify for verification codes.

A pre-submission checklist

• Legal name and EIN exactly match your IRS paperwork
• Website is live, on your own domain, with a public privacy policy and terms
• Privacy policy says you don’t share mobile numbers
• SMS consent checkbox is optional, unchecked and has a full disclosure
• Description, use case and sample messages all describe the same program
• Sample messages name your business and use [brackets] for variables
• No public link shorteners in samples or real messages
• Opt-out and help messages written and tested

Where Exa fits

Exa sends SMS through Twilio. Inside Exa, consent is stored per channel with its source and evidence, STOP, START and HELP replies update consent automatically, and opted-out numbers are blocked server-side, which supports the opt-in and opt-out story your campaign describes. Exa’s lead capture forms include per-channel consent checkboxes that store evidence on each submission. For how two-way texting fits into a sales process, see business texting.

Final thoughts

10DLC registration feels like paperwork, but it’s mostly a consistency check: does your business match its records, and does your texting program match what you say it is? Get the legal name right, publish a real privacy policy, write a specific description and realistic samples, and describe your opt-in honestly.

Then remember that registration is the start, not the finish. Carriers still expect consent, easy opt-outs and honest content every day after approval. The basics are in TCPA-friendly texting.