Understanding Campaign Rejection Errors
When registering A2P 10DLC campaigns, submissions may be rejected for compliance reasons.
Below are the most common rejection codes, what they mean, and what you can do to correct them.
Rejection Code | Reason / What It Means | How to Resolve or Next Steps |
30885 – High Risk and Fraud Violations | The campaign was flagged as high risk because it appears to use deceptive marketing, misleading claims, "get-rich-quick" schemes, or business models that may exploit consumers. | This type of rejection is final - you cannot resubmit.
If you believe this was an error, contact support directly to contest the decision. |
30897 – Prohibited Content Categories | Content falls in a disallowed category such as: • Loan marketing • Debt collection • Gambling • Sweepstakes • Stock alerts • Cryptocurrency or high-risk investments • Credit repair, or federally illegal substances. | These too are final rejections. Review carrier/content policy lists first; do not attempt to resubmit if your business model or content falls under these categories. |
30883 – SHAFT Content Violations | “SHAFT” stands for Sex, Hate, Alcohol, Firearms, Tobacco/Vapes (and related content). Also includes Marijuana/CBD. Even indirect or related content will trigger this rejection. | This is non‑resubmittable. Alter your content or business category to remove SHAFT references if possible, or shift to compliant types of content. |
30908 – Privacy Policy Compliance Issues | Some possible problems: missing privacy policy, conflicting policies, or policies that allow sharing of mobile numbers with third parties. | Ensure: • There’s a privacy policy linked clearly on your site. • It explicitly states how phone numbers will (or will not) be used or shared. • Messaging flows or campaign descriptions include links to the policy. |
30891 – Website & URL Verification Problems | The URL you provided is invalid, the site is inaccessible, opt-in flow not identifiable, or there’s insufficient public content if the site isn’t live. | Before resubmitting: • Make sure the website works and is public. • Opt‑in flow should be visible. • If site is pre‑launch or behind restrictions, include screenshots. • Provide context if certain pages require special access. |
30896 – Opt‑in Process Violations | Consent or opt‑in methods aren’t compliant: for example, missing opt‑in documentation, unclear or unverifiable consent, opt‑in data being shared improperly, or inconsistent information on how users opt in. | To fix: • Document all opt‑in methods (web forms, keywords, paper or verbal, etc.). • Include clear links or screenshots of forms. • Make sure privacy policy and terms are present. • Don’t share opt‑in data with unauthorized third parties. |
30909 – Call‑to‑Action & Message Flow Issues | Rejected because the description of your message flow (how messages are sent/received, what users must do) is missing required elements; disclosures are insufficient (e.g. brand identity, message frequency, opt‑out instructions); or message flows don’t clearly show consent methods. | When you resubmit: • Describe every method of consent (keyword, web, verbal, etc.). • Include required disclosures: brand name, number of messages expected, “message and data rates may apply,” how to opt out. • If opt‑in flow isn’t publicly accessible, provide hosted screenshots. • For inbound conversational workflows, describe how the customer initiates contact. |
Which Rejections Are Final vs Fixable
Final / Non‑resubmittable codes:
Codes involving high‑risk/fraud, prohibited content, or SHAFT content are considered non‑resubmittable. If rejected under these, you must contact support only if you believe there’s a mistake. Otherwise, you can’t update the campaign for reapproval under these violation types.Fixable / Resubmittable codes:
Rejections for privacy policy, URL verification, opt‑in process, or message flow issues usually can be resolved. Make the required changes and resubmit.
Tips to Avoid Rejection
Before you register, double‑check the content policy and ensure your campaign and business model aren’t in disallowed categories.
Make your privacy policy easy to find, clear, and specific about mobile number usage.
Clearly document consent flows, including opt‑in methods and user‑initiated actions.
Be explicit in messaging flow: include brand, opt‑out instructions, disclosure of data/message rates, and expected frequency.
Provide screenshots or links where public access to content is restricted.
Frequently Asked Questions
What should I include in my campaign submission to reduce the risk of rejection?
Strong campaign submissions usually include:
A detailed explanation of the opt-in method (e.g. web form, in-store sign-up).
URLs or hosted screenshots that show the opt-in in action.
Direct links to your privacy policy and terms of service.
A sample message flow that aligns with your actual sending practices.
Why is having a privacy policy so important for 10DLC campaigns?
A valid privacy policy shows that you’re responsibly handling user data.
It should:
Clearly state how mobile numbers are collected and used.
Explain if data is shared with any third parties.
Be easy to find on your website—ideally linked in the footer or main menu.
Missing or unclear privacy policies are a common reason for rejections.
Need Help? ✋🏻
Contact us on live chat or send an email to us at [email protected].