A2P 10DLC Registration
US carriers only deliver business text messages from local numbers that are registered for A2P 10DLC. This article explains what that means. To register, use Compliance Setup.
This is not legal advice. Carrier rules change; the summary below is background, not a promise of approval or delivery.
What 10DLC means
- 10DLC (10-digit long code) is a regular local phone number used for business texting, as opposed to a short code like 12345.
- A2P (application-to-person) means texts sent by a business system, such as Taalk, to consumers.
US carriers (AT&T, T-Mobile, Verizon and others) require businesses to register who they are and what they text before they send A2P messages from local numbers.
Why it matters
Carriers filter, throttle or block texts from unregistered senders. Messages can look "sent" in your system and never arrive. Registration tells carriers your business is legitimate and what your messages are for.
In Taalk, you'll see a reminder when you set up texting on an AI agent or a campaign until texting is registered.
What gets registered
Registration has two parts:
| Part | What carriers review |
|---|---|
| Brand | Your business identity: legal name (as registered with your EIN), business type, EIN, address, website and an authorized contact. |
| Campaign | What you text and how people opt in: use case, estimated monthly volume, opt-in method and proof, Privacy Policy and Terms of Service links. |
Compliance Setup collects both in one guided flow, along with your caller name (CNAM) if you want one.
How to register in Taalk
- Go to Platform › Compliance › Registration (or the Get started checklist step "Register for texting and caller ID").
- Follow the steps in Compliance Setup.
- Track each part's status: Draft, Submitted, In review, Approved or Needs changes.
Taalk's compliance team usually reviews a submission within one business day and emails you when a status changes. Carrier approval can take longer after that. You can also see your registration status under Profile › Business registration.
Common reasons for rejection
| Issue | How to avoid it |
|---|---|
| Legal name mismatch | Enter the name exactly as it appears on your EIN records. |
| Website problems | Your site must be live, match your business, and link a Privacy Policy. |
| Weak opt-in proof | Show a separate, unchecked SMS consent checkbox with your company name, message purpose, frequency, "Msg & data rates may apply" and STOP/HELP. |
| Privacy Policy wording | State that mobile information and SMS consent are not sold or shared with third parties for marketing. |
| Use case mismatch | Describe what you'll actually send. Registering for notifications and sending marketing gets flagged. |
Carrier fees
Carriers and The Campaign Registry charge registration and per-message fees for 10DLC traffic. These are set by the carriers, not by Taalk, and they change over time. Ask Taalk support how they appear on your account.
Tips
- Register before you plan to text. Don't wait for launch day.
- Keep your website, legal name and opt-in form consistent.
- Include STOP instructions in your messages.
- Start with modest volume and grow it.
Related
- Compliance Setup: the step-by-step how-to
- CNAM and Caller ID
- SMS Messaging
- Consent Management