Why your political texting registration was rejected — and how to fix it

You gathered your information, worked through the registration, submitted everything, and waited. Then came the rejection notice.

It's a frustrating experience — but it's also an extremely common one, especially for political organizations navigating this process for the first time. The important thing to understand is that most rejections aren't a judgment about your organization's eligibility. They're a signal that something specific is missing or inconsistent, and most of those things can be fixed in under an hour.

Work through the reasons below, match them against the feedback in your rejection notice, and fix what applies. Then resubmit. Most organizations that get rejected the first time get approved after addressing the flagged issues.

Reason 1: Missing or inaccessible privacy policy

This is the most common rejection trigger across every organization type. Reviewers are looking for a publicly accessible privacy policy that explains how your organization collects, uses, and protects personal data — specifically including phone numbers. If your site doesn't have one, or if it's buried somewhere that requires hunting to find, that's enough to stop approval.

A lot of organizations assume that because they're a small campaign or nonprofit, this doesn't apply to them. It does.

How to fix it: Create a privacy policy page if one doesn't exist — there are free generators online that cover the basics for small organizations. Make it publicly accessible, link to it in your site footer, and link to it directly from any form that collects phone numbers. Once it's live, update your registration with the URL and resubmit.

Reason 2: No SMS consent language on your forms

A phone number field on your signup form isn't the same as SMS consent. Reviewers need to see that visitors are explicitly informed they may receive text messages from your organization — before they submit the form. If that language isn't present and visible, the assumption is that people didn't know what they were signing up for.

How to fix it: Add a short disclosure directly below or near your phone number field. It doesn't need to be long — it needs to be clear. Something like: "By providing your phone number, you agree to receive text messages from [Org Name]. Reply STOP to opt out." Then link your privacy policy next to it.

Reason 3: No opt-in checkbox — or the checkbox was pre-checked

Consent to receive text messages needs to be active, not assumed. That means a checkbox — unchecked by default — that visitors can choose to check when they want to receive SMS communication. A pre-checked box doesn't count. Neither does a phone number field alone, even with consent language nearby. The checkbox is what makes consent explicit and optional.

How to fix it: Add an unchecked SMS opt-in checkbox to any form that collects phone numbers. Place it near the phone number field, label it clearly ("Yes, I'd like to receive text message updates"), and make sure submitting the form doesn't require checking it. Then verify the checkbox is actually optional by testing the form yourself.

Reason 4: Disclosure language is incomplete

Even when consent language exists, it's often missing specific required elements. Reviewers aren't just checking whether you mentioned texts — they're looking for a complete disclosure. Missing any one of these elements can trigger a rejection even if everything else looks fine.

Your disclosure needs to include: message frequency information, "message and data rates may apply," STOP opt-out instructions, HELP instructions, and a link to your privacy policy. All five. Not four.

How to fix it: Go through your existing disclosure word by word against that list. Add whatever's missing. The full disclosure can still fit in two sentences if written tightly — it doesn't need to be a paragraph. Once updated, make sure it's visible on every form that collects phone numbers, not just your main signup page.

Reason 5: Privacy policy isn't linked from the form

This one catches organizations who did the work but didn't connect the pieces. The privacy policy exists. It's public. But it's only in the footer — not linked from the form where someone is actually providing their phone number and consent. Reviewers want the policy accessible at the moment of consent, not three clicks away.

How to fix it: Add a direct link to your privacy policy within the consent language or immediately adjacent to the opt-in checkbox. The link text can be simple — "Privacy Policy" — but it needs to be there, on the form, at the point of consent.

Reason 6: Registration information doesn't match your website

Reviewers cross-reference what you submitted against what they find on your site. A different version of your organization name, a mismatched contact email, a description that doesn't line up with your about page — any of these can raise questions. They're not looking to catch you in something; they're trying to confirm your organization is who it says it is. Inconsistency makes that harder.

How to fix it: Open your registration submission and your website side by side. Check organization name, website URL, contact information, and any description of what your organization does. Fix the discrepancies — either update the registration or update the site — and make sure they match exactly before resubmitting.

Reason 7: Campaign Verify wasn't completed — or wasn't started

This is the rejection reason that blindsides political organizations most often. If your organization is running for office, supporting candidates, or engaged in electoral or political advocacy messaging, you almost certainly need Campaign Verify approval in addition to standard 10DLC registration. Many organizations submit their 10DLC registration without realizing Campaign Verify is a separate process with its own timeline — and then get rejected because that piece is missing.

Campaign Verify can take time. If you haven't started it, that's the first thing to do before you resubmit anything else.

How to fix it: Determine whether Campaign Verify applies to your organization — if you're doing any political messaging, assume it does. Start the Campaign Verify process, obtain your token once approved, and include that token in your registration before resubmitting. Don't resubmit your 10DLC registration until Campaign Verify is complete or actively in progress.

Reason 8: Message examples were too vague

Reviewers ask for message examples because they want to understand what you're actually going to send — and whether it matches the use case you described in your registration. Generic placeholder text doesn't give them that picture. Neither do examples that describe a completely different use case than what your organization actually does.

Too vague: "Hi, this is a message from our organization. Thanks for your support."

Specific and useful: "Hi [Name], polls close at 8pm tonight. Find your polling location at [link]. Reply STOP to opt out."

How to fix it: Write two or three examples that reflect what you'll actually send — GOTV reminders, volunteer asks, event notifications, member updates. Each example should include your org name, a clear call to action, and STOP opt-out language. Make them specific enough that a reviewer can picture your actual campaign.

If your rejection notice includes specific feedback, start there — don't just work through this list generically. Address the flagged items first, then do a full review of everything else before resubmitting. Fixing one thing and resubmitting with other issues still present just restarts the clock.

A rejection is part of the process for a lot of organizations — particularly political ones navigating Campaign Verify for the first time. The organizations that get stuck are the ones that resubmit without fully understanding what was flagged. The ones that move through it quickly treat the rejection notice as a specific to-do list, fix everything at once, and resubmit with confidence.

If you want to verify your setup before resubmitting, the Political SMS Compliance Checklist covers every item reviewers look for.

Next up: How long does 10DLC approval take?