A2P 10DLC registration is the carrier-required process that lets a small business send texts from software, such as appointment reminders, review requests or lead follow-up, from a regular 10-digit local number. You register your business as a “brand,” then register each texting program as a “campaign” describing who you text, why, and how they agreed to it. Skip it and U.S. carriers block the messages. Get it wrong and the campaign is rejected, usually because of a missing opt-in disclosure, a thin website or a privacy policy that does not say mobile numbers stay private. Below: what A2P 10DLC means in plain terms, what it costs, the reasons campaigns get rejected, and a checklist to get approved the first time.
What A2P 10DLC means in plain English
A2P stands for application-to-person: a text sent by software rather than typed by a person on a phone. 10DLC means 10-digit long code, the ordinary local phone number format. Twilio describes it as the standard U.S. carriers put in place to keep SMS traffic from long code numbers verified and consensual, and anyone sending SMS or MMS from an application over a 10DLC number to U.S. recipients has to register.
If your CRM sends a text when a web form comes in, when a job is booked, or when an invoice goes out, that is A2P traffic. It does not matter whether the platform is GoHighLevel, a scheduling tool, or a custom workflow in n8n or Zapier; the rule follows the number, not the software. HighLevel’s own help center says numbers must be linked to an approved campaign before SMS or MMS is sent.
This is not a new or optional rule. Twilio, one of the largest messaging providers behind many small business platforms, began fully blocking unregistered U.S. 10DLC traffic on September 1, 2023, and noted that it still charged messaging rates for the blocked messages. If your automations have been “sending” texts that customers say they never got, an unregistered or unlinked number is the first thing to check.
Brand vs campaign: the two parts of A2P 10DLC registration
Registration happens in two steps, and most confusion comes from mixing them up.
- The brand is your business. Legal name, EIN, address, website and a contact person. Carriers use it to confirm a real company is behind the messages.
- The campaign is one texting program. For example, “appointment reminders and job updates for existing customers” or “follow-up for people who request a quote on our website.” It includes a description, sample messages and proof of how people opt in.
Picking the right brand type matters. Twilio’s approval guide is blunt: applications from businesses that have a Tax ID looking for sole prop registration will be rejected. If your business has an EIN, register as a standard brand. Sole proprietor registration is for individuals without one, and it comes with tighter limits: Twilio lists one campaign per brand and roughly 3,000 message segments per day across U.S. carriers.
What A2P 10DLC registration costs
The fees are small compared with the cost of a follow-up system that silently fails. These are Twilio’s published figures; platforms built on top of a carrier provider, including HighLevel, may pass them through or bundle them differently.
| Fee | Amount | When it applies |
|---|---|---|
| Brand registration | $4.50 one-time | Every new brand |
| Standard brand vetting | $41.50 one-time | Standard brands (businesses with an EIN) |
| Campaign vetting | $15 per submission | Each campaign reviewed |
| Monthly campaign fee | $2 sole prop; $1.50 to $10 standard | Every month the campaign is active |
Sources: Twilio’s brand registration docs and campaign vetting FAQ, which says the $15 vetting fee is non-refundable if the campaign fails and that registration currently takes up to five business days for standard use cases. That last point is the real cost of a rejection: not the fee, but another week with your reminders and follow-ups switched off.
Why A2P 10DLC campaigns get rejected
Reviewers are checking that what you described matches what a customer will see. Most small business rejections trace back to one of these:
- The opt-in is missing required language. Twilio calls incomplete or missing opt-in requirements a common cause of rejection. The point where someone agrees to texts needs your business name, what kind of messages they will get, “Message and data rates may apply,” how to opt out, and links to your privacy policy and terms. Recurring programs also need a message frequency disclosure.
- The consent checkbox is pre-checked or bundled. On a web form, the SMS consent box has to be unchecked by default, so the customer actively chooses it.
- The privacy policy does not protect mobile numbers. Twilio says the absence of language confirming that opt-in mobile information will never be shared or sold to third parties is a major source of rejection. A generic template privacy policy usually fails here.
- The website cannot be verified. Sites that are under construction, password-protected, misspelled, or do not match the registered business name fail review. The website is part of your identity check, so an outdated one costs you here too.
- The campaign description is vague. “This campaign sends messages to customers” is rejected. Say who is sending, who receives it and why: “ABC Plumbing sends appointment confirmations, technician arrival updates and review requests to customers who booked service and opted in on our booking form.”
- Sample messages do not match the use case. If you registered for appointment reminders, a sample promoting a fall discount will raise a flag. Write samples that look like the texts your automation actually sends, with your business name and opt-out language.
A2P 10DLC approval checklist for small businesses
Work through this before you submit. Most of it lives on your website, which is why we treat 10DLC as a website and lead capture project rather than a phone project.
- Confirm the legal business name and EIN exactly match IRS records, including punctuation and “LLC.”
- Make sure the website is live, public and shows the same business name, address and contact details.
- Add an SMS section to the privacy policy stating that mobile numbers and opt-in data are never shared or sold to third parties or lead generators.
- Publish SMS terms: program name, message types, frequency, “Message and data rates may apply,” and that replying STOP opts out and HELP gets help.
- Add an unchecked SMS consent checkbox to every form that triggers texts, with the disclosure text right next to it. Our guide to website contact form best practices covers how to add it without cluttering the form.
- Screenshot the live form and opt-in language; reviewers ask for consent evidence.
- Write a campaign description naming the sender, the recipients and the reason.
- Write two to five sample messages copied from your real automations.
- Choose the use case that matches. Do not register marketing messages under a customer-care label.
- After approval, confirm every sending number is attached to the campaign before turning automations back on.
What changes in your automations after approval
Approval is not the end of compliance. Your workflows need to keep honoring the promises you made in the campaign.
Opt-outs have to stick, everywhere. Under the FCC’s consent revocation rules, which took effect April 11, 2025, consumers can revoke consent by any reasonable method, including replying “stop,” “quit,” “end,” “cancel” or “unsubscribe,” and requests must be honored within a reasonable time not to exceed ten business days. In practice, set your CRM to mark the contact as do-not-text the moment one of those words comes in, and make every workflow check that flag before sending.
New use cases need their own campaign. If you registered for service reminders and later want to send promotions or a reactivation offer, update or add a campaign first. The same goes for an AI chat or text agent that starts conversations on your behalf; it is still A2P traffic from your number.
Instant replies still need consent. Speed-to-lead texts that fire within a minute of a form submission are one of the highest-value automations a local business can run, as we cover in our guide to workflow automation for small business. They only work if the form collected consent first. The same applies to missed-call text back, which sends from a registered number and should be covered by your campaign description.
This post is general information, not legal advice. Texting rules also include the federal TCPA and state laws, and if you send marketing texts at volume it is worth a short conversation with an attorney.
A note for New Jersey service businesses
For service businesses in Somerset, Middlesex and Monmouth counties, a common gap is not a business that never registered. It is one that registered years ago under the owner’s name or an old website, then added new forms, a second number or a new booking tool, and never updated the campaign. If you changed websites, CRMs or phone numbers in the last year, check your registration status before you trust your follow-up.
Frequently asked questions
Do I need A2P 10DLC registration if I only text existing customers? Yes, if the texts are sent from software over a local 10-digit number. Registration is about how the message is sent, not whether the recipient is a new lead or a long-time customer. Texts you type by hand from a personal phone are a different category.
How long does A2P 10DLC approval take? Twilio currently says up to five business days for standard use cases, and HighLevel notes carriers can take several more business days to receive the updated registration after approval. Plan for one to two weeks before relying on new automations.
Can I use a sole proprietor registration for my LLC? No. If your business has an EIN, carriers expect a standard brand, and Twilio says sole proprietor applications from businesses with a Tax ID will be rejected.
What happens if I keep texting without registering? Carriers block messages from unregistered 10DLC numbers, and some providers still charge for the attempt. Your automations will look like they are working while customers receive nothing.
Get your texting set up and approved
Red Ridge AI builds lead capture and follow-up automation for small businesses across New Jersey from our office in Branchburg, and A2P 10DLC registration is part of every texting setup we do: privacy policy and SMS terms, compliant opt-in on your forms, campaign descriptions and opt-out handling in your CRM. Book a call and we will check whether your current texts are actually being delivered. Automatic review-request texts are part of The Never-Miss-a-Job System.