Decode a 10DLC rejection
What does your 10DLC rejection actually say?
Carrier and TCR rejection notices are worded loosely and rarely explain themselves. Find the wording closest to what you got below, or paste yours into the live lookup to match it instantly.
Critical — these reject the campaign
- “The opt-in workflow / call-to-action is not clearly described”Maps to: Opt-in / consent not described →
- “Sample messages do not match the campaign use case or description”Maps to: Opt-in language does not match the use case →
- “Sample messages are not realistic or appear to be placeholders”Maps to: Sample messages are placeholders or too generic →
- “Sample messages do not include opt-out (STOP) language”Maps to: Sample messages missing opt-out language →
- “HELP keyword response not provided or non-compliant”Maps to: HELP response not provided or non-compliant →
- “STOP keyword response not provided”Maps to: STOP response not provided or non-compliant →
- “Privacy policy does not mention SMS or is missing the required data-sharing language”Maps to: Privacy policy missing or does not mention SMS →
- “Website is not functional or the opt-in was not found on the website”Maps to: Website missing, dead, or under construction →
- “EIN and legal company name do not match”Maps to: Legal business name / EIN mismatch →
- “Campaign content is prohibited or restricted (SHAFT / high-risk)”Maps to: Prohibited or restricted content (SHAFT / high-risk) →
Warnings — these limit or throttle
- “Sole proprietor brand registered on the standard-brand path”Maps to: Sole proprietor treated as a standard brand →
- “Public URL shortener detected in message content”Maps to: Public URL shorteners in messages →
- “Brand trust score is insufficient for the requested throughput”Maps to: Low brand trust score / vetting needed for throughput →