Political SMS compliance checklist: 10 things to verify before you submit

If you haven't read What is 10DLC and why does your organization need it?, start there. This checklist picks up where that article leaves off — it's for organizations that understand what the registration process is and are ready to make sure everything is in order before they hit submit.

The items here reflect the most common reasons political and advocacy organizations get delayed or rejected. None of them are complicated. All of them are fixable. The goal is to catch them before a reviewer does.

1. Your website is live, public, and clearly identifies your organization

Reviewers will visit your website. It needs to be publicly accessible — not password protected, not "coming soon" — and it needs to make clear who your organization is, what it does, and how to contact you. A single-page site is fine. A broken or placeholder site is not.

• Website is live and publicly accessible
• Organization name is clearly displayed
• Contact information is present
• Description of the organization's purpose is easy to find

2. You have a privacy policy — and it's easy to find

This is the single most common reason applications get delayed. If your organization collects personal information — phone numbers, email addresses, names — you need a privacy policy that explains how that data is collected, used, and protected. It needs to be publicly accessible, not just referenced in your registration.

• A privacy policy exists and is publicly accessible
• The privacy policy explains how personal data is collected and used
• The privacy policy mentions SMS communication specifically

3. Your privacy policy is linked directly from your signup forms

Having a privacy policy page isn't always enough on its own. Reviewers expect it to be accessible from the exact location where you're collecting consent — meaning the form where someone enters their phone number should have a direct link to your privacy policy nearby. Don't make someone hunt for it.

• Privacy policy link appears on every form that collects phone numbers
• The link works and goes to the correct page

4. Your forms include clear SMS consent language

People who give you their phone number need to understand that they may receive text messages from your organization. That understanding needs to be communicated clearly — not assumed, not buried, not implied by a generic "sign up" button. The consent language should appear close to where the phone number is collected.

Example consent language:

By providing your phone number, you agree to receive text messages from [Organization Name]. Message frequency varies. Message and data rates may apply. Reply STOP to opt out or HELP for assistance.

• SMS consent language is visible near the phone number field
• Language clearly states that text messages may be sent
• Language is plain English — not buried in legal fine print

5. You have an optional SMS opt-in checkbox

Consent to receive text messages should be explicit and separate from submitting a form. An unchecked-by-default checkbox that specifically asks for SMS consent is the standard expectation. Pre-checked boxes or automatic enrollment based on a phone number field alone are common rejection triggers.

• An SMS opt-in checkbox exists on your form
• The checkbox is unchecked by default
• The checkbox is optional — the form can be submitted without checking it

6. Your disclosure includes all required SMS language

Beyond general consent, your SMS disclosure needs to include several specific elements that carriers and reviewers look for. Missing even one of these is enough to trigger a delay. The language doesn't need to be elaborate — it just needs to be present and accurate.

• Message frequency disclosure (e.g. "Message frequency varies" or "You'll receive up to X messages per month")
• "Message and data rates may apply" language
• STOP opt-out instructions
• HELP instructions (reply HELP for assistance or a support contact)
• Link to your privacy policy within or near the disclosure

Note: Carrier requirements do change. The items above reflect current standard expectations, but verify against the latest guidance before you submit — especially if this article has been sitting in your bookmarks for a few months.

7. Your organization information is consistent everywhere

Reviewers cross-reference what you submit in your registration against what they find on your website. Inconsistencies — different versions of your organization name, a phone number that doesn't match, a description that doesn't align with your site — are common delay triggers. Do a quick audit before submitting.

• Organization name matches exactly across registration and website
• Website URL in registration matches the actual URL
• Contact information is consistent
• Description of your organization's purpose is consistent

8. Political organizations: Campaign Verify is started early

If your organization is running for office, supporting candidates, or engaged in political advocacy or electoral messaging, you will likely need Campaign Verify approval in addition to standard 10DLC registration. Campaign Verify is a separate process with its own timeline, and it's one of the most common sources of unexpected delays for political organizations who didn't know it applied to them.

If there's any chance you fall into this category, look into Campaign Verify requirements before you submit anything else. Starting it late is one of the most avoidable delays in the whole process.

• Confirmed whether Campaign Verify applies to your organization
• Campaign Verify process started (if required)
• Token obtained and ready to include in registration (if required)

9. You have realistic message examples ready

Reviewers want to understand what you're actually going to send. Prepare a few concrete examples that accurately reflect your intended use — not generic placeholders. If you're sending GOTV texts, show a GOTV text. If you're sending event reminders, show an event reminder. Vague or implausible examples slow things down.

Example message:

Hi [First Name], it's [Org Name]. Early voting starts Monday. Find your polling location at [link]. Reply STOP to opt out.

• Two to three realistic message examples prepared
• Examples reflect your actual intended use case
• Examples include STOP opt-out language

10. A second set of eyes has reviewed everything

Before you submit, have someone else look at your website, your forms, your disclosure language, and your registration details. Not because you're careless — but because broken links, missing checkboxes, and inconsistent information are easy to miss when you've been staring at the same pages for hours. A five-minute review from a fresh perspective has saved more than a few organizations a week of waiting.

• Second person has reviewed the signup form and consent language
• All links tested and working
• Registration details reviewed for consistency with website

The organizations that move through SMS registration most smoothly aren't the most technical. They're the ones that prepare before submitting. Work through this list, fix what needs fixing, and you'll be in better shape than most.

If you've already submitted and hit a problem, the next article covers the most common rejection reasons and exactly how to address them.

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