A2P 10DLC registration: a practical guide for small businesses

If you send business text messages in the US from a normal 10-digit phone number, carriers require you to register. That's A2P 10DLC: Application-to-Person messaging over a 10-Digit Long Code.

Skip it and your messages don't bounce with a helpful error. They get filtered: delivered to nobody, often with a "sent" status on your end. This guide covers what to gather and what to expect.

Why this exists

Carriers were drowning in spam sent from cheap long codes. The fix was to make businesses identify themselves: register who you are (a brand) and what you send (a campaign), attach it to your numbers, and accept throughput limits and filtering based on that registration.

The practical effect: unregistered A2P traffic is unreliable, and increasingly just blocked.

What you'll need before you start

Gather this first. Half the delays come from hunting for it mid-application.

For the brand registration:

• Legal business name, exactly as registered.
• EIN (or equivalent tax ID). Sole proprietors have a different, more limited path.
• Business address, website, and a contact person with email and phone.
• Business type and industry vertical.

For the campaign registration:

• A description of what you'll send and why.
• Sample messages: actual message text, not placeholders. These get reviewed.
• Your opt-in method, described concretely, plus where it's documented.
• Links to your privacy policy and your SMS terms.

The opt-in requirement is the part that fails

Most rejections come down to consent evidence. You need to be able to say precisely how someone agreed to receive texts, and show it.

Acceptable patterns include a checkbox on a web form (unchecked by default, with disclosure text next to it), a customer texting you first, or a written agreement. The disclosure needs to say who's texting, what kind of messages, that message and data rates may apply, and how to stop.

What doesn't work: a purchased list, an assumption that having someone's number is consent, or a checkbox that's pre-checked.

You'll also need a public SMS terms page covering your program name, message frequency, "Msg & data rates may apply," STOP/HELP instructions, and a privacy policy link. Reviewers look for it.

Steps and rough timing

1. Register your brand. Usually fast, often same-day to a couple of days. Mismatches between your legal name and your EIN are the common failure.
2. Register your campaign. Slower, because a human reviews your use case and samples. Days to a couple of weeks depending on vertical and backlog.
3. Associate your numbers with the approved campaign.
4. Start sending, and watch delivery rates. Throughput is assigned based on your brand's trust score.

Budget a few weeks end to end. If you have a launch date, start this first, not last.

Ongoing obligations

Registration isn't a one-time gate you pass and forget:

• Honor STOP immediately and permanently until the person opts back in.
• Answer HELP with your identity and contact info.
• Send what you registered. Approved for appointment reminders and then blasting promotions is how brands lose trust scores.
• Keep consent records. If challenged, "we think they agreed" isn't a defense.

How this interacts with your software

Your messaging platform should enforce the parts that are enforceable in code: opt-out state checked on every send, quiet hours respected, marketing consent tracked separately from service messages, and an audit trail of what went out.

In Frontiva, opt-out enforcement lives in the send path itself: a conversation marked opted-out refuses outbound sends rather than relying on a policy someone remembers. Your registration is tracked too, since 2026-09-26: the brand and use cases you registered live on a screen under Settings, Compliance, each number you text from is joined to one, and the carriers' answer is recorded against it, so a number they would filter reads as unregistered instead of looking fine. You still register in your own Twilio account, and Frontiva does not yet provision numbers for you.

This is a practical summary, not legal advice. TCPA and state-level rules carry real penalties, and the details depend on your industry and how you collect consent. Have counsel review your opt-in language and templates.