Cleared to Send

10DLC / A2P registration

Your 10DLC campaign got rejected. Here's how to fix it.

Carriers reject A2P 10DLC campaigns for a short, predictable list of reasons. Below is that list, with the exact fix for each. Then let Cleared to Send generate a submit-ready package and audit it against every reason before you resubmit — so you don't lose another two to four weeks.

Fix my registration → See the rejection reasons

The most common 10DLC rejection reasons

These are the criticals — the ones that get a campaign bounced outright.

  1. Opt-in / consent not described

    The #1 rejection cause. The campaign must describe exactly how end users consent to receive messages, and the consent must be verifiable.

    Fix: Describe the opt-in method in detail (web form, keyword, point of sale, paper form) and capture a screenshot of the exact CTA. Consent must be explicit and not bundled with other terms.

  2. Opt-in language does not match the use case

    Sample messages or call-to-action describe a message type the campaign did not register for (e.g. marketing content on a 'customer care' campaign).

    Fix: Make the CTA, the declared use case, and the sample messages describe the same thing. If you send marketing, register a marketing campaign and say so at opt-in.

  3. Sample messages are placeholders or too generic

    Samples like 'Hello, this is a test' or vague templates get rejected. Samples must reflect real traffic and match the use case.

    Fix: Provide 2-3 realistic messages that match the declared use case, include the brand name, and show any {variables} you actually use.

  4. Sample messages missing opt-out language

    At least one sample (typically the first/initial message) must show how recipients stop messages.

    Fix: Include 'Reply STOP to opt out' (or 'Text STOP to unsubscribe') in at least one sample message.

  5. HELP response not provided or non-compliant

    Carriers require a HELP keyword response that identifies the brand and gives a contact method.

    Fix: Provide HELP copy that names the brand and includes a support contact (phone, email or URL). Keep it under 320 characters.

  6. STOP response not provided or non-compliant

    A STOP keyword must confirm opt-out and state that no further messages will be sent.

    Fix: Provide STOP copy confirming the user is unsubscribed and will receive no further messages from the brand.

  7. Privacy policy missing or does not mention SMS

    The brand website must host a privacy policy stating that mobile information is not sold or shared with third parties for marketing.

    Fix: Publish a privacy policy on the website that explicitly states SMS opt-in data is not shared/sold, and link it from the opt-in flow.

  8. Website missing, dead, or under construction

    Reviewers visit the brand website to verify the business is real and the opt-in exists. A dead or parked domain fails.

    Fix: Ensure the website is live, describes the business, and (for web opt-in) hosts the consent form and privacy policy.

  9. Legal business name / EIN mismatch

    Brand registration is rejected when the legal name and EIN do not match IRS records exactly.

    Fix: Use the exact legal entity name tied to the EIN (as on the IRS CP-575 / tax records), not a DBA or marketing name.

  10. Prohibited or restricted content (SHAFT / high-risk)

    Sex, Hate, Alcohol, Firearms, Tobacco, cannabis, gambling, loans/debt, and other restricted categories are barred or heavily gated.

    Fix: Remove restricted content, or pursue the specific carrier-approved special-use-case path if the business is in a gated vertical.

Don't guess whether the fix worked

Cleared to Send's Clear module walks you through each of these, generates your consent language, sample messages and policy copy, then runs the whole package against this exact kill-list and returns a pass / fail verdict with specific fixes. Catch the rejection before the carrier does.

Start Clear · it's guided →
  • Opt-in & consent language generated for you
  • Sample messages pre-scored and matched to your use case
  • HELP / STOP / privacy copy, correctly formatted
  • Pre-submission audit against every reason above
  • Submit-ready package to paste into your provider

Common questions

Why was my 10DLC campaign rejected?

The most common cause is opt-in: the campaign didn't clearly describe how customers consent, or the consent couldn't be verified. Sample messages that don't match the declared use case, a missing HELP or STOP response, and a privacy policy that doesn't mention SMS are the next most frequent reasons.

How long does it take to re-register after a rejection?

Re-review typically takes another one to four weeks. That's why fixing every issue before you resubmit matters — each rejected resubmission restarts the clock.

Do I need an EIN to register for 10DLC?

Not always. Without an EIN you can register on the sole proprietor path, which has lower daily throughput and stricter content limits. Registering a sole proprietor as a standard brand is itself a rejection cause.

What is a submit-ready 10DLC package?

Your brand details, campaign use case, opt-in/consent language, two to three compliant sample messages, and your HELP, STOP and SMS privacy copy — all formatted the way carriers expect, with the known rejection reasons already checked.