Full disclosure — I run ReadySMS. The 47 submissions referenced below are real submissions our team has shepherded through TCR (The Campaign Registry) and the carriers in the last 12 months. The rejection patterns are anonymized but accurate.

If you've tried to register a 10DLC campaign in 2025 or 2026, you've probably hit a rejection that read something like:

"Sample messages do not appear to align with the use case. Please update and resubmit."

That sentence is the bane of every SMS team's existence. It's the carrier's way of saying "no" without explaining why. After running 47 submissions through the registration process — 33 approved, 14 rejected, 9 of those eventually approved on resubmission — here's the actual pattern of what gets through and what doesn't.

The four-stage gauntlet

Before getting into rejection patterns, here's what "10DLC registration" actually involves. Most documentation glosses over this:

  1. Brand registration — TCR vets your business identity. EIN, legal name, vertical. Approval: usually instant if your EIN is clean. Rare rejections are typically EIN/legal-name mismatches.
  2. Campaign registration — TCR vets what you'll send. Use case, sample messages, opt-in flow. Approval: 1-3 business days. This is where most rejections happen.
  3. Carrier review — T-Mobile, AT&T, and Verizon each separately review the campaign. Approval: 5-10 business days, but T-Mobile is the gatekeeper that catches 90% of issues.
  4. Provisioning — Numbers get assigned to the campaign. Throughput tier set. Now you can send.

Most "10DLC is hard" complaints conflate stages 2 and 3. The TCR submission itself is straightforward; the carrier review is where vague rejection reasons appear.

What we saw across 47 submissions

OutcomeCount%
Approved on first submission3370%
Rejected, approved on resubmission919%
Rejected, no successful resubmit yet511%

The 70% first-pass rate is higher than the industry average (industry quote is around 50% first-pass), and we've spent enough hours debugging rejections to have a strong sense of why.

The 5 rejection patterns we see most

1. Sample messages don't include opt-out language

This is the #1 rejection. Carriers want to see "Reply STOP to unsubscribe" or equivalent in at least one of your sample messages — usually the first transactional/welcome message.

Gets rejected:

"Hi! Thanks for signing up. Reply YES to confirm your appointment."

Gets approved:

"Hi! Thanks for signing up. Reply YES to confirm your appointment. Reply STOP to unsubscribe."

You don't need it on every single sample message, but at least one needs to demonstrate that opt-out is honored. Many teams skip this because their production messaging includes it dynamically — but the registration form takes static samples.

2. Use case doesn't match sample content

Carriers cross-reference your declared use case against your sample messages. If you pick "Customer Care" as your use case, but your samples include promotional content, you get rejected.

Common trap: picking "Marketing" or "Promotional" because it sounds broad. These categories have stricter content review and lower throughput tiers. Pick the narrowest category that actually describes your use — "Account Notifications," "2FA," "Polling/Voting," "Customer Care" — and your approval odds go up.

3. Opt-in description is vague

The opt-in description field is a free-text box where you describe how customers consent to receive SMS. Vague answers like "Customer signs up on website" get rejected.

Gets rejected:

"Customer opts in via our website signup form."

Gets approved:

"Customer enters phone number and email on https://example.com/signup, ticks the box reading 'I agree to receive transactional SMS notifications about my account, including order updates and shipping confirmations. Message and data rates may apply. Reply STOP to unsubscribe.' Phone number is verified via OTP before any SMS is sent."

The pattern: name the URL, quote the consent language verbatim, mention frequency expectations and STOP handling. The more specific, the faster the approval.

4. Brand doesn't match the visible business

If your TCR brand is "Acme Holdings LLC" but the website you cite uses the brand "Acme Marketing," carriers flag this as a misalignment. Either rename the brand to match the public-facing brand or update the website to display the legal entity.

The sub-trap here is DBA (doing business as) names. TCR allows DBA fields, but carriers verify against the visible website. If your website doesn't display the DBA, the DBA field doesn't help you.

5. Throughput request out of band for use case

The throughput tier you request needs to make sense for your use case and brand vetting score. New brands with no operating history that request 200+ msgs/sec typically get bumped to tier 1 (1 msg/sec) automatically. Apply for the tier that makes sense for your current volume; you can request an upgrade after demonstrating consistent traffic.

The pre-submission checklist that improved our approval rate

After analyzing the rejections, we built a 7-item checklist run before any submission. First-pass approval went from 58% to 81% after we adopted this:

  • [ ] EIN matches legal name on website footer / TOS / privacy policy
  • [ ] Use case is the narrowest accurate option (not "Marketing" by default)
  • [ ] At least one sample message includes "Reply STOP to unsubscribe"
  • [ ] At least one sample message identifies the brand by name (e.g., "[Acme]" prefix)
  • [ ] Opt-in description quotes the consent language verbatim and names the opt-in URL
  • [ ] Privacy policy on the website mentions SMS communications explicitly
  • [ ] Throughput tier requested matches realistic month-1 volume

Run this check first. The 22-minute audit saves you 5-10 days of back-and-forth.

What to do when you get rejected

The rejection email is usually a single sentence with no specific reason. Don't bounce a resubmission immediately — that's a common mistake that lengthens the cycle.

Instead:

  1. Read your submission against the 7-item checklist above. 80% of the time the failure is one of these.
  2. If nothing obvious is wrong, change ONE THING and resubmit. Common safe changes: tighten the opt-in description, add STOP language to all sample messages (not just one), narrow the use case category.
  3. If still rejected, contact the carrier directly. Most providers have an escalation channel to T-Mobile or AT&T's compliance team. Use it.

We've had cases that took 3 resubmissions and a carrier escalation to clear. The longest one took 21 days from first submission to approval — for a legitimate political volunteer organization that the system kept flagging because their use case was unfamiliar.

How long does this actually take?

Realistic timeline for a brand with no carrier history:

  • Brand vet: instant to 24 hours
  • Campaign submit → TCR approval: 1-3 business days
  • TCR approval → carrier review (T-Mobile, AT&T, Verizon): 5-10 business days
  • Carrier approval → number provisioning: 1-2 business days
  • Total realistic timeline: 10-15 business days for first send

If a vendor tells you "2 minutes to start sending" they're either talking about installing their app (true) or counting on you migrating an already-registered campaign (also possible, but you can't if it's a brand new business).

What changed in 2026

A few updates worth knowing if you've been off the 10DLC beat for a year:

  • T-Mobile's review queue moved faster in Q1 2026. Average TCR-to-carrier-approval is down from ~14 days in 2025 to ~8 days now.
  • Stricter content review on financial services use cases. If you're sending mortgage, debt, or loan-related messages, expect 2-3x more scrutiny on samples.
  • AT&T started flagging URL-shorteners more aggressively. Bit.ly and TinyURL in sample messages can trigger rejection. Use a custom domain redirect.
  • Brand vetting score now visible. TCR exposes the score that influences throughput tier — if you're below 75, you're at tier 1 by default. Improving the brand profile (full address, website with TLS, social links) raises the score.

The 10DLC process is annoying, but it's not random. Most rejections fall into a small set of patterns. If you've been rejected and want a second pair of eyes on the submission, that's the kind of thing my support team helps with — even if you're not on ReadySMS yet, it's useful free practice for us. Email support@readysms.io.