A2P 10DLC - Registration for Government and Nonprofit Agencies

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.

• 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 Government.
• 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.

• 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.

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

• 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.

• 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.

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.

1
// Download the helper library from https://www.twilio.com/docs/node/install
2
const twilio = require("twilio"); // Or, for ESM: import twilio from "twilio";
3

4
// Find your Account SID and Auth Token at twilio.com/console
5
// and set the environment variables. See http://twil.io/secure
6
const accountSid = process.env.TWILIO_ACCOUNT_SID;
7
const authToken = process.env.TWILIO_AUTH_TOKEN;
8
const client = twilio(accountSid, authToken);
9

10
async function createBrandVetting() {
11
  const brandVetting = await client.messaging.v1
12
    .brandRegistrations("BNXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX")
13
    .brandVettings.create({
14
      vettingId:
15
        "cv|1.0|tcr|10dlc|9975c339-d46f-49b7-a399-2e6d5ebac66d|EXAMPLEjEd8xSlaAgRXAXXBUNBT2AgL-LdQuPveFhEyY",
16
      vettingProvider: "campaign-verify",
17
    });
18

19
  console.log(brandVetting.accountSid);
20
}
21

22
createBrandVetting();

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

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.

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.

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.

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