Does every US business text need A2P 10DLC registration?

A2P 10DLC applies when an application sends messages to US recipients from a 10-digit long-code number. Twilio states that all traffic it sends from a 10DLC number to US recipients must be registered, including traffic from individuals and hobbyists. Toll-free numbers and short codes follow separate registration or verification paths, so sender type should be checked first.

Is A2P 10DLC the same as legal consent?

No. Registration identifies the sender and campaign to the messaging ecosystem; it does not create consumer consent. A program still needs an appropriate opt-in, accurate disclosure, working opt-out handling, and records that match the messages sent. Carrier acceptance and legal compliance overlap, but they are different checks. Ask qualified counsel to review interpretations of the TCPA and state law.

What information does a campaign application need?

Expect to provide the legal business identity, tax or registration details, campaign purpose, sample messages, opt-in flow, help behavior, and opt-out behavior. The evidence must agree across the form, website, screenshots, and sample copy. Twilio also requires publicly accessible privacy-policy and terms URLs for new API campaign submissions from June 30, 2026, so those pages belong in the launch checklist.

A2P 10DLC Guide for Marketers

What does A2P 10DLC register?

The process covers two connected records. A brand record identifies the business. A campaign record describes why messages are sent, how people opt in, how they get help, how they opt out, and what sample messages look like. Approved numbers are then associated with that campaign through a messaging service.

Which sender types sit outside 10DLC?

Sender	Typical use	Registration path
10-digit long code	Local-looking business messaging	A2P 10DLC for application traffic to US recipients
Toll-free	National two-way or service messaging	Separate toll-free verification
Short code	High-volume branded programs	Separate carrier provisioning
Alphanumeric ID	Branded sender in supported markets	Country-specific; unavailable for US traffic

What evidence should you collect first?

Legal business name, registration ID, address, entity type, and authorized representative.
Website, public privacy policy, public terms, and consistent brand contact details.
Campaign purpose, expected content, two representative messages, and sender identity.
Opt-in location, disclosure copy, screenshots, confirmation behavior, HELP response, and STOP handling.
Messaging service, phone number, provider account owner, and internal launch approver.

How long does review take?

Twilio's current quickstart warns that campaign reviews can take 10 to 15 days. That estimate can change and is not an approval promise. Build the review queue into the launch schedule, answer requests for more information carefully, and avoid sending application traffic from the number before the required approvals are in place.

Why do privacy and terms pages matter in 2026?

Twilio requires public privacy-policy and terms-and-conditions URLs for new A2P campaign registrations submitted through its API from June 30, 2026. Both pages need to load publicly. They should identify the business and describe relevant data and messaging practices consistently with the application.

What does registration not do?

Registration does not grant consent, approve every future message, settle TCPA interpretation, or guarantee delivery. It is one control in a larger program. Maintain consent evidence, honor opt-outs, use the approved campaign purpose, monitor provider status, and ask qualified counsel to review the laws that apply to your business and audience.

Primary references checked July 26, 2026

For hands-on preparation, see A2P registration support. Connect the sender work to SMS compliance operations and the opt-in checklist.

A2P 10DLC, without the carrier fog.