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.
- Haven't submitted yet? Start your registration, the guided pre-submission flow →
The most common 10DLC rejection reasons
These are the criticals. They get a campaign bounced outright.
- How to fix this rejection →
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.
- How to fix this rejection →
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.
Opt-in CTA missing a required disclosure
The call to action, where the customer actually agrees, has to carry every disclosure itself: brand name, that the messages are texts, what you will send, message frequency, 'Msg & data rates may apply', HELP and STOP instructions, and links to your Terms and Privacy Policy. Putting them only in your Terms does not count. Reviewers now flag each missing piece with its own code.
Fix: Rewrite the CTA next to the phone field or keyword so it reads like: 'By checking this box, you agree to receive appointment reminder texts from {Brand}. Message frequency varies. Msg & data rates may apply. Reply HELP for help, STOP to cancel. Terms: {url} Privacy: {url}'. Your opt-in confirmation text needs the same brand, frequency, rates, HELP and STOP pieces.
SMS consent is forced, pre-checked, or bundled
Consent to texts has to be its own optional choice. A pre-checked box, a box required to submit the form, consent folded into accepting your Terms, one box covering texts plus email and calls, or one box covering both marketing and informational texts all fail. So does consent a staff member records on the customer's behalf.
Fix: Give texts their own unchecked checkbox (or keyword) that the customer has to select, and let them finish the form, purchase, or sign-up without it. If you send marketing and informational texts, use a separate opt-in for marketing. Offer a non-SMS option for verification codes.
- How to fix this rejection →
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.
- How to fix this rejection →
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.
Campaign description vague or generic
The description has to say who sends the messages, who receives them, what they contain, and why. A one-liner like 'customer notifications', the same text pasted into several fields, or a description that doesn't match the brand, website, and samples gets rejected. It must be in English.
Fix: Write 2-4 plain sentences: '{Brand}, a dental office in {city}, texts appointment reminders and rescheduling links to patients who opted in on our online booking form. Patients get 1-3 messages per appointment.' Keep it different from the opt-in description and consistent with the samples and website.
Content attributes don't match the messages
The campaign's content attributes (embedded links, embedded phone numbers, age-gated content, direct lending, affiliate marketing) have to match what you actually send. A sample with a link while 'embedded link' is off, a lender with direct lending off, or age-restricted content with no age gate all fail.
Fix: Set each attribute to match your real traffic, and make the samples show it: if you send links or phone numbers, include them in the samples. If you lend money, say so in the description and turn on direct lending. If your content is age-restricted, put an age gate on the site and before opt-in.
- How to fix this rejection →
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.
- How to fix this rejection →
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.
- How to fix this rejection →
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.
- How to fix this rejection →
Terms and conditions missing or not compliant
Reviewers check for public terms and conditions that cover the SMS program. Terms that allow sharing opt-in data or phone numbers with third parties, or that signal affiliate or lead-generation marketing, fail review.
Fix: Publish a terms page on your website with an SMS section: business and program name, what you send and how often, 'Msg & data rates may apply', HELP and STOP instructions, a support contact, a line that carriers are not liable for delayed or undelivered messages, and a link to your privacy policy. Link it from the opt-in form, add the URL to your campaign, and remove any language about sharing consent or phone numbers with third parties.
- How to fix this rejection →
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.
- How to fix this rejection →
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.
Brand support email or contact can't be verified
The support email and contact person on the brand have to clearly belong to the business. A disposable address, a personal free-mail address with no public tie to the business, or a contact who isn't an employee or owner gets flagged.
Fix: Use an address on your business domain (support@yourbusiness.com) and list an owner or employee as the contact. If you have to use a free-mail address, publish it on your website as the business contact. No spaces in the email or phone fields.
- How to fix this rejection →
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.
Lead generation, affiliate, or shared consent
Consent has to go to the one brand that sends the texts. Bought or rented lists, numbers collected for partners, affiliate marketing, one campaign shared by several companies, or opt-in proof showing a different company's name all get rejected, often with no resubmission path.
Fix: Collect consent only for your own brand, with your name on the form. Remove any Terms or privacy language that allows sharing numbers or consent with partners or affiliates. If you send for several businesses, register a separate brand and campaign for each.
Don't guess whether the fix worked
Cleared to Send 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 your registration · 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
What does "your A2P campaign registration with TCR failed" mean?
TCR is The Campaign Registry, the system every 10DLC campaign goes through. A failed registration means the campaign was not approved in review. Your provider's notice usually includes a reason, like unclear opt-in or sample messages that don't match the use case. Paste it into the free rejection lookup to match it to the cause.
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.