In order to register your US long code messaging traffic for A2P 10DLC, Twilio offers registration through Twilio’s Trust Hub. Twilio has integrated directly with The Campaign Registry (TCR) to facilitate registration for all our customers. This offers you other benefits of Twilio’s Trust Hub.
However, if you are an Independent Software Vendor (ISV), you can apply to Twilio for an exception to allow you to go directly to TCR for your Brand and Campaign registrations, and use those registrations for your message traffic on Twilio. If you aren't sure whether you are an ISV, see our A2P 10DLC registration article for a description of ISV vs. a direct customer.
The process to request an exception to go directly to TCR is described below. However, before considering this option, please review the below information about requirements and limitations when registering your A2P 10DLC Brands and Campaigns directly with TCR.
I am a direct customer of Twilio (not an ISV). Can direct customers register their Brands and Campaigns with TCR?
No, at this time only ISVs are able to complete registration directly through TCR, according to TCR and carrier rules.
Direct customers must use Twilio’s Trust Hub and A2P registration system to submit their information to TCR.
What additional work is required of ISVs if they go directly to TCR?
Going directly to TCR for registration requires working through and understanding telecom complexities such as Direct Connect Aggregators (DCAs), rate limits, and daily messaging caps. Twilio’s Trust Hub takes care of this complexity for you, so you only have to register your Brands and Campaigns (Use Cases).
What other advantages does Twilio's Trust Hub offer, compared to going direct to TCR?
In addition to managing the telecom complexities, Twilio’s Trust Hub also offers a streamlined registration process that allows you to register a Business Profile once, and use that same registered information across multiple channels (Messaging, Voice, etc.). For example, Twilio’s Voice product offers SHAKEN/STIR for trusted calling, which also utilizes Trust Hub registration.
Twilio is also continually discussing price advantages that we can provide to our customers, now and in the future. By utilizing the Twilio Trust Hub and APIs, you have a centralized, single-vendor experience that guarantees quality, support, and cost-effectiveness.
What limitations/complexities are introduced by going directly to TCR?
Campaigns can’t be shared across vendors.
A2P Campaigns registered through TCR can’t be shared across vendors, so you will still need to work with a vendor like Twilio to attach your registered Campaigns to phone numbers. It is not possible to use a single Campaign across multiple vendors.
Migration between vendors requires new Campaign registrations, which could result in downtime.
Migration between vendors requires you to create new Campaigns in TCR, which could result in downtime. TCR requires you to select a vendor when registering a Campaign, and does not allow an already-registered Campaign to be changed to utilize a different vendor.
If you wish to use the same phone numbers via a different vendor, you would also be required to move phone numbers between providers. It is likely there would be downtime in the process of moving your numbers.
Twilio offers an assurance of quality.
The Campaign Registry is a new registration solution. We are still unsure of the full impact or implications of multi-vendor registrations. Bugs or nuances with multi-vendor registration, some of which might not be discovered yet, could negatively impact your traffic.
I understand the limitations and I’d like to apply to use direct-to-TCR registrations with Twilio.
If you meet the requirements and would like to apply for an exception to register direct to TCR, please contact your Account Executive to initiate the process.
If you do not have an Account Executive, please contact Twilio Support.