A2P 10DLC registration: What Businesses Need to Know

A2P 10DLC registration, explained

A2P 10DLC registration identifies a US business and its application-to-person SMS program before it sends from local 10-digit long-code numbers. You register a Brand, register Campaigns that explain the messages and consent path, then associate approved senders through a messaging provider. The Campaign Registry describes 10DLC as an A2P channel in which Brands and Campaign Service Providers are verified before messaging is allowed. [1]

10DLC registration is a carrier-ecosystem and messaging-provider requirement, not a legal safe harbor. Federal and state rules may govern consent, content, timing, privacy, and opt-outs. For covered robotexts, FCC rules protect a recipient’s ability to revoke consent. [4] Treat registration as one control inside a broader business SMS compliance program—not permission to text any number you possess.

What you register: the Brand, the Campaign, and the sending numbers

A Brand is the business identity behind the program, typically including its legal name, address, tax identifier where applicable, website, and authorized contact. A Campaign defines the use case, description, samples, and opt-in, help, and opt-out methods. Your provider links local 10DLC numbers or a messaging service to that campaign. Twilio likewise separates Brand creation from Campaign creation. [2]

Do not register a parent company and then send under an unrelated storefront name, or call a campaign “customer care” when it promotes sales. Brand identity, opt-in language, website, campaign description, and the messages themselves should point to the same recognizable business. This consistency is central to SMS campaign vetting and later filtering decisions.

Choose a use case that matches the message people will receive

The use case is not a label to optimize for cost or throughput. It is a reviewer’s shorthand for program purpose. Common patterns include promotional marketing, customer care, account or delivery notifications, and one-time passcodes. If a service thread can include discounts, disclose that reality and make sure consent and templates support it. Providers offer standard, low-volume, and special use cases with different fee and throughput treatment. [2]

For example, an ecommerce brand might describe a marketing campaign as: “Subscribers who check the optional SMS box at checkout receive product launches, sale alerts, and cart-related offers from Northstar Outfitters.” Its samples should look like that program: “Northstar Outfitters: Early access to 25% off select outerwear through Sunday. Reply STOP to opt out.” A shipping-notification campaign should not use the same campaign to send seasonal sale blasts. Keep campaigns narrow enough that the evidence and message stream remain credible.

Before adding a message category, acquisition path, brand name, or audience, decide whether the registration still accurately describes the program. A conservative best practice is to involve the registration owner before a new automated flow launches.

Build website proof and disclosures before submitting

The fastest way to create rework is to submit a campaign before its public enrollment experience exists. Reviewers need to verify the opt-in method; a live public website with an opt-in process is one accepted form of proof. Twilio’s registration guidance also identifies a public video or a public screenshot of a configuration that tracks opted-in users as possible evidence where a site is not live. [3] Your submission should identify the exact page and explain the steps a person takes—not merely say “customers opt in online.”

At collection, make the SMS choice distinct and the disclosure visible before submission. A practical disclosure identifies the brand and program, explains recurring or automated SMS where applicable, gives an expected frequency description, notes message and data rates may apply, and explains help and opt-out options. Link directly to terms and a privacy policy. These are carrier and platform expectations informed by voluntary industry guidance, not a replacement for fact-specific legal review. [5]

Your privacy policy must describe actual data practices. One current provider checklist calls for a public policy stating that mobile information will not be shared with third parties or affiliates for marketing or promotional purposes. [3] Do not use language your business cannot honor. Build enrollment around our SMS opt-in requirements, then test the linked SMS terms and conditions and SMS privacy policy pages on mobile.

• Capture the exact disclosure version, webpage URL, date and time, mobile number, and affirmative action associated with enrollment.
• Use the same brand name in the checkbox disclosure, confirmation message, campaign samples, and actual sender identity.
• If text-to-join is offered, configure the keyword response and preserve proof of the keyword, number, and resulting consent event.
• Make HELP and STOP paths work in the production messaging environment, not only in a staging demo.

A practical A2P 10DLC registration workflow

1. Inventory every US local number, messaging provider, business unit, message stream, and live or planned opt-in source.
2. Name a business owner for each program and verify the legal entity, website, and customer-facing brand are accurate and consistent.
3. Separate message streams into defensible use cases; write a short campaign description that states audience, purpose, cadence, and consent route.
4. Collect representative samples that show the brand and an opt-out instruction and that genuinely match the registered description.
5. Publish and test the enrollment page, terms, privacy policy, confirmation logic, HELP handling, STOP suppression, and consent-record capture.
6. Submit the Brand and Campaign through your Campaign Service Provider, respond promptly and truthfully to vetting questions, then associate only approved senders with the approved campaign.
7. After approval, run a controlled production test, verify delivery and keyword behavior, and document the campaign ID, sender inventory, owner, and approval evidence.

Businesses generally work through a registered Campaign Service Provider rather than directly with The Campaign Registry. [1] Use your provider’s current instructions rather than copying an application from another platform. Vetting queues and clarification requests vary, so do not promise a launch date based on an assumed approval time.

Why A2P 10DLC campaigns are rejected—and how to correct them

Most denials are evidence or consistency problems. Twilio identifies campaign registration as the step where most application failures occur and calls for thorough descriptions, relevant samples, sender identification, verifiable opt-in proof, and functional linked websites. [3] Fix the root mismatch before resubmitting.

Throughput: approval improves routing clarity, not a delivery guarantee

Throughput is the rate at which a program may submit messages, often measured in segments. It is not a fixed benefit of approval. Provider documentation says campaign type, brand type, expected volume, and sometimes trust score affect capacity. [2] Carrier controls, routing, engagement, number health, and content can also affect delivery. Registration can reduce risk tied to unregistered traffic, but it does not guarantee delivery or prevent filtering.

Plan peak sends before choosing a sender setup. Calculate recipients, segments, acceptable delivery window, trigger concurrency, and retries. Use queues and rate limits that respect the provider configuration. Keep promotional bursts separate from time-sensitive order or security messages where the platform permits. Validate current capacity in writing before promising rapid delivery at scale.

A well-vetted list is a commercial control as well as a compliance control. Suppress unsubscribes immediately, validate numbers at capture where appropriate, and watch delivery failures and complaints by source, campaign, and sender. Our SMS deliverability guide and guide to reducing SMS spam complaints explain the operating signals that merit action.

Post-approval obligations: keep the registered program true

Approval begins the operating phase. Continue sending only traffic the campaign describes, maintain the opt-in experience, and review material changes before deployment. Keep an owner who can pause a sender, answer provider inquiries, and retrieve consent proof. A strong SMS consent audit trail links each subscriber to source, disclosure version, affirmative action, timestamps, program, and opt-out events.

Legal obligations and carrier expectations overlap but are not identical. For robotexts covered by the FCC rule, a recipient may revoke consent by any reasonable method that clearly communicates the request. STOP, QUIT, END, REVOKE, OPT OUT, CANCEL, and UNSUBSCRIBE replies are reasonable means per se; covered senders must honor reasonable revocations within no more than 10 business days and cannot require one exclusive path. [4] Have counsel assess application to your program. HVSMS provides strategy and implementation, not legal advice.

• Synchronize opt-outs across the CRM, messaging provider, support desk, and any agency or ecommerce integration; test that suppression before every major launch.
• Monitor delivery errors, carrier or provider notices, opt-out rates, complaint signals, and unusual changes in engagement; investigate by campaign and acquisition source.
• Re-review templates, sender associations, public disclosures, and consent capture whenever a new brand, funnel, audience, or message category is introduced.
• Keep consent and suppression evidence available for the period appropriate to your legal and contractual obligations, using a documented retention decision rather than an arbitrary default.

The registration readiness test

You are ready when an independent reviewer can move from the campaign description to the live opt-in page and representative messages without finding contradictions. The brand is recognizable, purpose specific, consent path visible, policies live, and STOP and HELP working. Your CRM must prove opt-in and prevent future sends after revocation. Resolve any uncertainty before vetting.