10DLC rejection reasons · Free lookup
What does your 10DLC rejection actually mean?
Carrier and TCR rejection notices are vague on purpose. Paste yours below and this free tool matches it to the exact reason it maps to, with the fix. No login, no waiting, nothing stored.
Nothing leaves your browser and nothing is stored. This matches your wording against the known 10DLC rejection reasons instantly. For a rebuilt, submit-ready package, use Fix →
Every 10DLC rejection reason
The complete list carriers and TCR bounce campaigns for. Critical reasons get a campaign rejected outright; warnings limit or throttle it. Each links to the full fix.
Critical — reject the campaign
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.
How to fix it →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).
How to fix it →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.
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.
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.
How to fix it →Sample messages missing opt-out language
At least one sample (typically the first/initial message) must show how recipients stop messages.
How to fix it →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.
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.
HELP response not provided or non-compliant
Carriers require a HELP keyword response that identifies the brand and gives a contact method.
How to fix it →STOP response not provided or non-compliant
A STOP keyword must confirm opt-out and state that no further messages will be sent.
How to fix it →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.
How to fix it →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.
How to fix it →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.
How to fix it →Legal business name / EIN mismatch
Brand registration is rejected when the legal name and EIN do not match IRS records exactly.
How to fix it →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.
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.
How to fix it →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.
Warnings — limit or throttle
Duplicate brand or campaign
Registering the same EIN as several brands, or submitting a campaign that copies an existing one (same description, website, flow, and samples under a new ID), gets flagged.
Sole proprietor treated as a standard brand
Sole proprietors without an EIN follow a different, throughput-limited path. Registering one as a standard brand fails.
How to fix it →Public URL shorteners in messages
Shared shorteners (bit.ly, tinyurl) are heavily filtered because they mask the destination.
How to fix it →Low brand trust score / vetting needed for throughput
Unvetted brands get low daily message limits. High-volume use cases need external vetting.
How to fix it →Haven't submitted yet?
If you're registering for the first time, don't guess your way into a rejection. The guided flow walks you through opt-in, samples, HELP / STOP and privacy copy, then audits the whole package against every reason in this list before you submit.
Common questions
Why was my 10DLC campaign rejected?
Almost always one of a short, fixed list of reasons: opt-in consent that wasn't clearly described or verifiable, sample messages that don't match your declared use case or read like placeholders, a missing HELP or STOP response, a privacy policy that doesn't mention SMS, a website that isn't live, or a legal-name / EIN mismatch at the brand level. Paste your rejection above and this tool points you at the exact one.
Is this rejection lookup free?
Yes. It runs entirely in your browser, needs no account, and stores nothing. It matches your rejection wording against the known 10DLC rejection reasons and shows you the fix. Rebuilding the corrected package is what Fix does.
What's the difference between this lookup and Fix?
The lookup identifies which reason your rejection maps to and how to fix it, instantly and for free. Fix reads your whole rejection and context, then rebuilds a corrected, submit-ready package — the consent language, samples, HELP/STOP and privacy copy — so your resubmission passes.
How long until I can resubmit after a 10DLC rejection?
Re-review usually takes another one to four weeks, and every rejected resubmission restarts that clock. That's why identifying every real reason before you resubmit matters more than resubmitting fast.