When registering campaigns for A2P 10DLC messaging, your submission may be rejected for various compliance reasons. Below are the most common rejection errors and how to address them:

Your campaign has been flagged as high risk due to content that appears fraudulent or uses deceptive marketing practices. This type of rejection means the campaign cannot be approved and is ineligible for resubmission. Common triggers include misleading claims, get-rich-quick schemes, or business models that appear to exploit consumers. If you believe this rejection was made in error, you'll need to contact support directly as these campaigns cannot be resubmitted through the normal process.

Campaign rejections for disallowed content occur when your business falls into restricted categories such as loan marketing, debt collection, gambling, sweepstakes, stock alerts, cryptocurrency, risk investments, debt reduction, credit repair, lead generation, or federally illegal substances. These content restrictions are in place to comply with carrier policies and federal regulations. Like high-risk rejections, campaigns rejected for disallowed content cannot be resubmitted. Review your business model carefully against carrier content policies before registering.

SHAFT categories (Sex, Hate, Alcohol, Firearms, Tobacco/Vape) and Marijuana/CBD are completely prohibited from A2P messaging. Even tangential content related to these categories can trigger a rejection. This includes dating apps with adult content, firearm accessories, CBD products marketed for wellness, or alcohol delivery services. These rejections are final and cannot be appealed through resubmission.

Privacy policy rejections occur for several reasons: missing privacy policy, policy inconsistencies such as multiple conflicting policies, or policies that indicate mobile information sharing with third parties. To resolve this, ensure your privacy policy is easily accessible from your website's main pages and explicitly states that mobile phone numbers collected for messaging will not be shared with third parties for marketing purposes. The policy must be directly linked in your message flow description and clearly address SMS data collection and usage.

Website-related rejections happen when the provided URL is invalid, the website is inaccessible, the opt-in flow cannot be found, or there's insufficient indication that a website is pre-launch. Before resubmitting, verify all URLs are working correctly and publicly accessible. If your website is geographic-specific or requires special access, include this information in your campaign description with links to screenshots. For pre-launch websites, provide publicly accessible screenshots of your planned SMS opt-in flow rather than a non-functional URL.

Opt-in rejections occur when the consent workflow doesn't meet requirements, consent isn't adequately provided or maintained, or opt-in information is being shared with unauthorized third parties. To fix opt-in issues, document all methods customers can use to opt-in (website forms, keywords, paper forms, verbal consent), provide direct links or hosted screenshots of opt-in forms, ensure your website includes both privacy policy and terms of service, and verify that opt-in data isn't shared with third parties. Every opt-in method must be clearly verifiable by human reviewers.

This is often the most complex rejection to resolve. The rejection occurs when the Call to Action (Message Flow) doesn't clearly explain how users opt-in, lacks sufficient detail for off-website consent verification, omits required disclosure elements, doesn't list all opt-in methods used, or when opt-in evidence isn't publicly accessible.

To address message flow rejections, rewrite your Message Flow section to include every consent collection method (web forms, keywords, verbal scripts, paper forms, QR codes), ensure all required disclosures are present (brand identification, message frequency for recurring programs, links to terms and privacy policy, "message and data rates may apply" notice, and opt-out instructions), and provide public URLs with hosted screenshots if your opt-in process isn't publicly accessible.

For conversational messaging that primarily responds to inbound messages, clearly document how customers initiate contact and provide consent, such as "customers text our support number to start a conversation." When using keyword opt-ins, include the specific keywords and provide the required help and opt-out responses.

Most campaign rejections (except for high-risk, disallowed content, and SHAFT violations) can be resolved by addressing the specific issues mentioned in the rejection notice and resubmitting your campaign. Take time to carefully review each rejection reason and ensure your updated submission fully addresses all compliance requirements before resubmitting. For rejections that cannot be resubmitted, contact customer support if you believe the rejection was made in error.