10DLC Registration Requirements for High-Volume Senders

If you send text messages to US customers at volume, 10DLC registration requirements decide whether your messages arrive. 10DLC (10-digit long code) is the system US carriers use to manage business texting from standard local phone numbers. Businesses register who they are and what they send, and carriers use that information to decide how much traffic to let through.

Vendors report that since February 1, 2025, US carriers have blocked texts sent from unregistered 10DLC numbers, with no grace period or reduced-rate tier (opens in a new tab). That report comes from industry sources, so confirm the current rules with your messaging provider. Either way, the practical point is the same: registration is now a precondition for a reliable program.

Key takeaways

• 10DLC registration has two steps: register your brand, then register each campaign.
• Your brand's vetting score is reported to set how much you can send, and adding more phone numbers does not raise it.
• Most rejections trace back to mismatches: between your EIN and legal name, your stated use case and your sample messages, or your consent claims and your website.
• Some use cases, including certain lending and debt-related messaging, are reportedly restricted. Check before you build a program around them.
• Gather your documents and fix your website before you submit. Resubmissions cost time.

How 10DLC registration works

Registration runs through The Campaign Registry (TCR), the industry database that carriers rely on. Most businesses register through a messaging provider, which submits the information on their behalf.

Step 1: Brand registration

According to TCR's user guide (opens in a new tab), a brand must be registered before any campaign can be created for it. Brand registration includes your legal company name, country of registration and EIN (Employer Identification Number, the US federal tax ID). Each registered brand receives a unique 7-character Brand ID that starts with "B".

TCR's guide also states that unverified brands cannot register 10DLC campaigns. A brand needs "Verified" or "Vetted_Verified" status first.

Step 2: Campaign registration

A campaign describes one messaging program: its use case, sample messages and proof of how recipients opt in. Vendors report that the use case category you choose matters. SignalWire (opens in a new tab) calls choosing the wrong category, or being vague, one of the most common causes of rejection or delay.

If you run several programs, such as appointment reminders and promotional offers, expect to describe each one accurately. One vendor reports that a marketing use case inside a mixed campaign must be listed and approved separately (opens in a new tab).

Why your brand's trust score matters for throughput

Vendors report that your throughput, meaning how many messages you can send per day or per minute, comes from your brand's vetting score and your campaign's use case. SignalWire (opens in a new tab) reports that adding more phone numbers to a campaign does not raise it.

Reported carrier behavior differs:

• T-Mobile reportedly applies a daily cap at the brand (EIN) level. According to JustCall (opens in a new tab), the cap counts all outbound SMS segments and MMS to T-Mobile subscribers (including Sprint and MetroPCS) for that EIN, even if the brand is registered through another provider. Sole proprietor brands are reportedly capped at about 1,000 messages per day to T-Mobile.
• AT&T reportedly applies a per-minute limit per campaign.

The exact tiers and score bands vary from source to source, and Verizon's model is unclear, so this post does not give a tier table. Ask your provider for the limits that apply to your brand today.

One more point: trust scores are reported to reflect (opens in a new tab) identity, business age and size, public records and compliance history, not message content. A high score does not protect you if your messages drift from what you registered. Carriers can still filter or block them.

Common reasons 10DLC campaigns get rejected

Rejection is mostly a documentation problem, not a content problem. The causes reported by vendors fall into a few groups.

Brand-level mismatches

• EIN and legal name don't match. Signal House reports (opens in a new tab) that an EIN that doesn't match your legal name or IRS records is a common brand mistake.
• Generic support email. Using a Gmail-style address instead of one on your website's domain is another reported mistake.
• Brand name differs from the sending entity. The name you register should match the business that actually sends the messages.

Use case and sample message problems

• Samples don't fit the stated use case. A CSP source reports that a mismatch is a common rejection reason (opens in a new tab), for example a marketing campaign submitted with one-time-passcode samples.
• No brand name in samples. Reported as a rejection cause by A2P.guide (opens in a new tab).
• Link shorteners or HTTP URLs. Also reported as rejection causes.
• Missing disclosures. Reported gaps include message frequency, "Msg & data rates may apply," and STOP/HELP instructions.

Weak or unverifiable consent

Reviewers reportedly check (opens in a new tab) your consent claims against your public website. Commonly reported problems:

• A missing or pre-ticked opt-in checkbox
• Bundled consent, where agreeing to texts is folded into another agreement
• A privacy policy with no statement that mobile numbers are not shared
• A site that doesn't name the business or its messaging program
• Opt-in language that doesn't match your sample messages

Prohibited or restricted content

A2P.guide reports that prohibited categories include SHAFT content (sex, hate, alcohol, firearms, tobacco), cannabis, high-risk loans, debt, gambling and crypto. If your program involves lending or collections, this matters. Official carrier rules for these categories were not verified for this post, so check the current carrier policies, or ask your provider, before you build a program around one.

What this means for high-volume SMS senders

Registration is not a one-time form. It affects how fast you can scale, and it can change what happens to a program that is already running.

Plan for review time. Sources disagree on timelines. One vendor says brand registration takes minutes to two business days and another says two to five, while campaign approval ranges from a few business days to several weeks. Fees also vary across providers, and some include markups. Build slack into launch dates.

Treat your registration as a contract. Reviewers compare what you submit to your website, your samples and, later, your live traffic. If your messages change, such as new offers, new links or a different sender name, update the registration to match.

Watch delivery after approval. Approval is not the end. Carrier filtering shows up as delivery failures and error codes, and you want to catch it early.

What to do now

1. Match your brand data. Confirm that your legal name, EIN and address agree with your IRS records and your website.
2. Use a domain email. Set up a support contact on your website's domain.
3. Pick the narrowest accurate use case. Don't use a broad category to cover several programs. Register each program separately.
4. Write samples that mirror reality. Include your brand name, use the same tone and content as live messages, and avoid link shorteners and HTTP URLs.
5. Fix your opt-in flow. Use an unchecked, standalone consent checkbox with clear disclosures: who is texting, how often, "Msg & data rates may apply," and STOP/HELP.
6. Publish matching policies. Your website and privacy policy should name your business and messaging program and say that mobile numbers are not shared.
7. Check restricted categories. If you send lending, collections or similar messages, confirm current carrier rules before you submit.
8. Ask for your current limits. Get your brand's throughput tier from your provider and plan volume around it.
9. Monitor deliveries. Review failure patterns by carrier error code after launch and after any change.

Frequently asked questions

What are the main 10DLC registration requirements?

You register your brand first, with your legal company name, country of registration and EIN. Then you register each campaign with its use case, sample messages and proof of opt-in. A brand must have "Verified" or "Vetted_Verified" status before it can register campaigns.

Why was my 10DLC registration rejected?

Reported causes include an EIN that doesn't match your legal name, sample messages that don't fit your stated use case, opt-in language that doesn't match your samples, missing disclosures, and prohibited content. Reviewers also check your website, so missing consent language or a site that doesn't name your business can lead to rejection.

Does adding more phone numbers increase my 10DLC throughput?

According to SignalWire, no. Throughput is reported to come from your brand's vetting score and your campaign's use case, not the number of numbers you attach. If you need higher limits, ask your messaging provider about vetting options and your current tier.

Get registered before you scale

A clean registration is the foundation of a reliable SMS program, and it is far cheaper to get right before launch than to fix after messages start failing. Flowtext is 10DLC registered and TCPA compliant, with 24/7 number-health monitoring and carrier error-code failure analysis that help surface filtering early.

This post is general information, not legal advice. Consult counsel about your own messaging programs.

Tags

• 10DLC
• SMS compliance
• A2P messaging
• deliverability
• campaign registration