Using Twilio’s Externally Registered Campaigns API, Twilio supports A2P registration directly with TCR and allows you to connect your TCR registered Brands and Campaigns to Twilio’s services.

Effective January 26, 2023, new A2P Campaign registrations were subject to a manual vetting process and were charged a $15 campaign verification fee at the time of external vetting. 

Effective March 15, 2023 Twilio introduced changes to the ERC API requiring Campaign Vetting before connecting your Campaigns to Twilio as well as introducing our own vetting into the process. While previously customers could register Twilio as the DCA via the TCR API and immediately connect those Campaigns via the ERC API, Campaigns that don’t complete vetting will now fail. Customers will need to make sure they wait for the CAMPAIGN_SHARE_ACCEPT webhook from the TCR API before calling the ERC API. 

Please see below for full details on the changes to the submissions steps:

ERC Registration (Previous Guidance: Prior to January 26th)

1. Create a Twilio Messaging Service via API/Console.
2. Assign phone numbers to the Messaging Service's Sender Pool via API/Console.
3. Via TCR APIs, share the campaign with Twilio as the Direct Connect Aggregator (DCA).
4. Twilio, as the DCA, accepts the campaign and obtains campaign metadata regarding rate limits and daily messaging caps.
5. Assign a CampaignID to the Messaging Service that you created using the Externally Registered Campaigns API.
6. Twilio ensures every phone number in the Messaging Service's Sender Pool is associated with the CampaignID attached to the Messaging Service.
7. Twilio will bill messages and rate limit them according to the Campaign Class.

ERC Registration (Previous Guidance: Jan 26, 2023 - March 15, 2023)

1. Create a Twilio Messaging Service via API/Console.
2. Assign phone numbers to the Messaging Service's Sender Pool via API/Console.
3. Via TCR APIs, share the campaign with Twilio as the Direct Connect Aggregator (DCA).
4. Assign a CampaignID to the Messaging Service that you created using the Externally Registered Campaigns API.
5. Twilio will perform any carrier-specific campaign configuration and elect any required secondary DCAs for this campaign. Secondary DCAs will conduct campaign reviews before the campaign becomes fully operational. If the secondary DCAs reject the campaign, Twilio support will reach out with their feedback. Twilio will bill the $15 vetting fee for each review conducted by the secondary DCA. 
6. Twilio ensures every phone number in the Messaging Service's Sender Pool is associated with the CampaignID attached to the Messaging Service.
7. Twilio will bill messages and rate limit them according to the Campaign Class.

ERC Registration (Current Guidance)

1. 1. Create a Twilio Messaging Service via API/Console.
   2. Assign phone numbers to the Messaging Service's Sender Pool via API/Console. Phone numbers can be added to a Messaging Service before or after Campaign association.
   3. Via TCR APIs, share the campaign with Twilio as the Direct Connect Aggregator (DCA).
   4. Twilio, as the DCA, reviews the campaign for compliance. 
      • If the campaign data fails the review criterion, Twilio will reject the campaign sharing request. You will receive a CAMPAIGN_SHARE_DELETE webhook from TCR. You can update the information on the campaign based on the feedback in that webhook and re-share the campaign for re-review. 
   5. Once a campaign is accepted, you will receive a CAMPAIGN_SHARE_ACCEPT webhook from TCR. You will not be able to move past this step until the campaign is accepted.
   6. You assign a CampaignID to the Messaging Service that you created using the Externally Registered Campaigns API. Twilio obtains campaign metadata regarding rate limits and daily messaging caps.
   7. Twilio will perform any carrier-specific campaign configuration and elect any required secondary DCAs for this campaign. Secondary DCAs will conduct campaign reviews before the campaign becomes fully operational. Twilio will bill the $15 vetting fee for each review conducted by the secondary DCA.
      • If the secondary DCAs reject the campaign, you will receive a CAMPAIGN_SHARE_DELETE specifying that the DCA2 has rejected the campaign with a reason. You will need to update the campaign based on the feedback and contact Twilio support to resubmit the campaign with the secondary DCA that rejected the campaign.
   8. Once the campaign is approved by all parties in the chain, Twilio ensures every phone number in the Messaging Service's Sender Pool is associated with the CampaignID attached to the Messaging Service. All future numbers added to the Messaging Service will also be associated with the campaign. (Note: Sole Proprietor campaigns are limited to 1 number)
   9. Twilio will bill messages and rate limit them according to the Campaign Class.