On this page

A2P 10DLC - Registration for Government and Nonprofit Agencies

Government and nonprofit agencies are eligible for A2P 10DLC Special Use Cases, which allow for increased messaging throughput and/or discounted pricing on the T-Mobile network.

This document lists the specific steps required to register your A2P 10DLC Brand and Campaigns if you are a government or nonprofit organization.

Read this guide before beginning A2P 10DLC registration to ensure that your organization can use the appropriate A2P 10DLC Use Case.

If you are registering your own agency/organization for A2P 10DLC, you are considered a Direct Customer , and you need to follow the steps in the Direct Standard Brand Onboarding Guide along with the Direct Customer directions on this page .
If you are an Independent Software Vendor (ISV) registering your customer for A2P 10DLC, you need to follow the steps in the ISV Standard Brand Onboarding Guide , along with the ISV directions on this page .

(warning)

Warning

If you are registering a 527 political organization, there are additional required steps. Read the 527 political organization section at the bottom of this page before starting the A2P 10DLC registration process.

Direct Customer

This section is for Direct Customers who are registering their own government or nonprofit organization for A2P 10DLC. This section covers the values you need to provide at specific points in the A2P 10DLC registration process.

Direct Customer - Government organizations

When creating your TrustHub profile:
- For Business Type , enter Non-profit corporation .
- For Business Industry , enter Government .
When creating your A2P Brand:
- For Company Type , enter US Non Profit .
Once your Brand is APPROVED, you can create your A2P 10DLC Campaign.
- Government agencies can register with all Standard Campaign Use Cases, and are also eligible for the Emergency Special Use Case. Read the Help Center article on Special Use Cases for more information .

Direct Customer - Nonprofit agencies

When creating your TrustHub profile:
- For Business Type , enter Non-profit corporation .
- For Business Industry , enter Not for profit .
When creating your A2P Brand:
- For Company Type , enter US Non Profit .
- For 527 political organizations , you must also provide your Campaign Verify token during this registration step.
Once your Brand is APPROVED, you can create your A2P 10DLC Campaign.
- Nonprofit organizations have access to additional Special Use Cases, such as Charity/501(c)(3). 527 political organizations can use the Political Special Use Case. Read the Help Center article on Special Use Cases for more information .

ISV

This section covers the values that must be provided by an ISV when registering their customer's government or nonprofit organization for A2P 10DLC.

ISV - Registering a government organization

When creating the EndUser resource of type customer_profile_business_information for your customer's business:
- The business_type value must be Non-profit Corporation .
- The business_industry value must be GOVERNMENT .
When creating the EndUser resource of type us_a2p_messaging_profile_information:
- The company_type value must be government .

ISV - Registering a nonprofit organization

When creating the EndUser resource of type customer_profile_business_information for your customer's business:
- The business_type value must be Non-profit Corporation .
- The business_industry value must be NOT_FOR_PROFIT .
When creating the EndUser resource of type us_a2p_messaging_profile_information:
- The company_type value must be non_profit .

Additional steps for ISVs registering a 527 political organization

This section covers the two additional steps required for 527 political organizations to have access to the Political Special Use Case.

When creating the BrandRegistration resource for a 527 political organization, skip_automatic_sec_vet must be true as shown in the code sample in the onboarding guide .
After the BrandRegistration's status is APPROVED, you need to create a BrandVetting resource.
- This API request associates the Campaign Verify token with the BrandRegistration resource. A sample request is shown below.
- The vetting_provider is campaign-verify .
- The vetting_id is the Campaign Verify token.

Create a BrandVetting resource for a 527 political organization

Node.js

Python

Java

PHP

Ruby

twilio-cli

curl


_14// Download the helper library from https://www.twilio.com/docs/node/install
_14// Find your Account SID and Auth Token at twilio.com/console
_14// and set the environment variables. See http://twil.io/secure
_14const accountSid = process.env.TWILIO_ACCOUNT_SID;
_14const authToken = process.env.TWILIO_AUTH_TOKEN;
_14const client = require('twilio')(accountSid, authToken);
_14
_14client.messaging.v1.brandRegistrations('BNXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX')
_14  .brandVettings
_14  .create({
_14     vettingId: 'cv|1.0|tcr|10dlc|9975c339-d46f-49b7-a399-2e6d5ebac66d|EXAMPLEjEd8xSlaAgRXAXXBUNBT2AgL-LdQuPveFhEyY',
_14     vettingProvider: 'campaign-verify'
_14   })
_14  .then(brand_vetting => console.log(brand_vetting.brandSid));

Output


_12{
_12  "account_sid": "AC78e8e67fc0246521490fb9907fd0c165",
_12  "brand_sid": "BNXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX",
_12  "brand_vetting_sid": "VT12445353",
_12  "vetting_provider": "campaign-verify",
_12  "vetting_id": "cv|1.0|tcr|10dlc|9975c339-d46f-49b7-a399-2e6d5ebac66d|EXAMPLEjEd8xSlaAgRXAXXBUNBT2AgL-LdQuPveFhEyY",
_12  "vetting_class": "POLITICAL",
_12  "vetting_status": "IN_PROGRESS",
_12  "date_created": "2021-01-27T14:18:35Z",
_12  "date_updated": "2021-01-27T14:18:35Z",
_12  "url": "https://messaging.twilio.com/v1/a2p/BrandRegistrations/BN0044409f7e067e279523808d267e2d85/Vettings/VT12445353"
_12}

527 political organizations

(information)

Info

This section only applies to 527 political organizations that need to register for A2P 10DLC.

Campaign Verify is a secure, non-partisan verification solution for US political organizations who wish to engage with voters via A2P 10DLC messaging.

All 527 political organizations sending political communications on behalf of a federal, state, or local political campaign must be verified by Campaign Verify to unlock the Political Special Campaign Use Case with increased messaging limits.

(warning)

Warning

You should read the Campaign Verify FAQ before continuing with this guide, as this process involves fees.

Verification involves submitting information about your political organization to Campaign Verify, as well as verifying your identity as an authorized person associated with the political organization. After completing verification with Campaign Verify, you receive a Campaign Verify (CV) token. You need to provide this token during A2P 10DLC registration with Twilio.

Campaign Verify tokens

A full CV token is composed of 6 pipe (|) delimited fields, for example:

cv|1.0|tcr|10dlc|9957c339-d46f-49b7-a399-2e6d5ebac66d|GQ3NMEjED8xSlaAgRXAXXBUNBT2AgL-LdQuPveFhEyy

CV tokens expire after a period of time and need to be periodically updated. This can be done via API using the BrandVetting resource .
You can only use a CV token with one Brand.
If the 527 organization is a customer of multiple text messaging providers that will each create an A2P 10DLC Brand on the organization's behalf, a unique CV token must be generated and provided to each vendor.

(warning)

Warning

A 527 organization that does not register with Campaign Verify and provide a token during A2P 10DLC registration is allowed to register with Standard Use Cases, but receives the lowest tier of A2P 10DLC messaging limits and does not qualify for the Political Special Use Case.

In addition, the organization may be subject to penalties from carriers if political messaging traffic is incorrectly registered with Standard Use Cases.

(information)

Info

If you have already created a US A2P Brand for a 527 political organization and would like to add a CV token after Brand registration, you must use the REST API.

Once you have a CV token, you can proceed with registration. You provide the CV token during the Brand registration step.