# About "Campaign Verify"

If your organization is a 527 (a political campaign, party committee, or PAC), you need to register with "[Campaign Verify](https://www.campaignverify.org/)" to ensure your text messages don't get filtered.

### **What's Campaign Verify?**

"Campaign Verify" is a third-party vetting provider for "[The Campaign Registry](https://www.campaignregistry.com/)", the organization that manages phone number registrations. These are both third-party organizations Daisychain works with to ensure your messages get delivered.

The verification process costs $95 and provides access to a token that authenticates your organization's identity and unlocks high-volume texting capacity on 10DLC.

**Who needs Campaign Verify?**

Campaign Verify is required for any 527 political organization that wants to use the Political special use case with higher messaging throughput. This includes:

* Federal candidate committees
* State and local candidate committees
* Party committees at any level
* PACs
* Ballot initiative committees organized as 527s

**Who does NOT need Campaign Verify?**

* 501(c)(3) nonprofits
* 501(c)(4) advocacy organizations not sending explicitly political messages
* Businesses and other non-political entities

**Why bother?**

Without Campaign Verify you're limited to sending 2,000 messages per day to T-Mobile and 75 messages/minute to AT\&T. With Campaign Verify and the Political use case, T-Mobile throughput is uncapped.

### **How do I register with Campaign Verify?**

To register with Campaign Verify, follow the steps below:<br>

1. **Submit Verification Request**\
   To obtain a Campaign Verify token, fill out [the form on the Campaign Verify website](https://www.campaignverify.org/get-started) and follow their instructions. Please note there is a $95 verification fee. Once submitted, Campaign Verify will approve or reject your request, on a timeline that varies from just a few minutes to two business days.\
   ​
2. **Receive a PIN**\
   Following approval, Campaign Verify will provide you with a six-digit PIN code. This code is vital to generate your token, which allows unlimited texting capacity on 10DLC. Your method of receiving the PIN depends on the information in your public filing record.\
   ​
3. **Generate a Token**\
   Upon receiving your PIN code, log into your Campaign Verify account at [**Campaign Verify**](https://app.campaignverify.org/). Click on the name of your verified campaign, input your PIN at the bottom of the page, select "The Campaign Registry" as the service, and generate your token.\
   ​
4. **Share the Token with Daisychain**\
   Lastly, email your token to Daisychain, and we'll let you know when you're good to go!

{% hint style="info" %}
**Already have a Campaign Verify account and need to generate a new token to use with Daisychain?** When you create a 10DLC brand with Daisychain, you will need to provide a new Campaign Verify token, distinct from any previous tokens you’ve used. The process for creating a new token for an election cycle you have already been vetted to send messages for is quick and free.

To create a new token, please login to Campaign Verify, and scroll to the bottom of the page. There you will find a button to Create an Authorization Token. Please click this button to create the new token. The new token will be displayed underneath your existing tokens.

*Some users may need to enroll in Multi Factor Authentication with Campaign Verify to complete this step.*
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://daisychain.gitbook.io/help/texting/phone-number-registration/about-campaign-verify.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.