Registration process

To register your Sole Proprietor Brand, go to the Trust & Compliance page in your Console and begin the process listed under the A2P Brands tab. Click the Create A2P Brand button to get started on creating your brand.

Again, a Tax ID would be a U.S. EIN or a Canadian Business Number, which you would use to file Federal U.S. or Canadian income tax as a corporate entity. If you DO have such a number, you are not eligible for a Sole Proprietor Brand but must instead register as a Standard or Low-Volume Standard Brand. A Sole Proprietor is either an individual businessperson who uses their own Social Security number (or Canadian Social Insurance Number) when filing income taxes. 

As part of the registration process, Twilio sends the One Time Password (OTP) verification request to this mobile number from which you must respond.

• This mobile number must belong to a valid U.S. or Canadian mobile device.
• You can't acquire this mobile number from a CPaaS provider such as Twilio.
• You can use this mobile number no more than three times for exclusive A2P 10DLC Sole Proprietor Brand registrations with TCR.
• If you registered an A2P 10DLC with another vendor using this mobile number, that registration counts towards this limit.
• You may use the same number for both the Phone Number field during Profile creation and the Mobile Number field on this screen, provided that this number satisfies all of these requirements.

You are also asked to agree to the one-time Brand registration fee before submitting your Brand, and consent to an OTP verification request using the mobile number you've provided. When you have completed these details, click Register to submit your Brand for approval.

Once you click Register, Twilio submits your application for approval. Approval typically occurs within a few minutes of submitting. You will receive an email and see a message on screen when your registration is complete.

Before your Brand can be fully approved, you will receive an SMS OTP to the mobile number you provided. You must respond to this OTP within 24 hours for your Brand to be approved. If you've failed to respond to this OTP within 24 hours, you can come back to this screen to re-trigger the OTP request.

 

Approval process

A Brand can have one of the following statuses:

• IN_REVIEW: Brand registration is in progress and your Brand information is under manual third-party review. Manual reviews take seven business days or more. There is no action required from your side.
• APPROVED (Registered): Brand registration is complete and the Brand is verified. You can now register your Campaigns.
• FAILED: Brand information couldn't be verified and registration has failed. You can find reasons for failure in the Trust & Compliance page in Console then click on the rejected brand to review the brand.
• SUSPENDED: The Brand potentially violates one or more rules for Brand registration.

If your Brand registration is FAILED or SUSPENDED, see our Troubleshooting Guide for detailed information on how to correct and resubmit the registration.

Once your Brand is APPROVED, it will be listed in the Brands tab under the Trust & Compliance page in Console to display a final screen that lists the brand name and its TCR Trust Score.

 

Step 3: Register a Campaign and associate a Messaging Service

Now that your Customer Profile and Brand are successfully registered, you can register a Campaign for your Brand to send A2P 10DLC messages.

Set up a Messaging Service and Twilio Phone Number

Campaigns require an associated Messaging Service with at least one Twilio 10DLC Phone Number in its Sender Pool. You can use an existing Messaging Service or create one before or during Campaign registration. A Messaging Service can only be linked with one Campaign at a time.

The Messaging Service must have at least one Twilio Phone Number in its Sender Pool. During the Campaign registration process, you can associate an existing Twilio Phone Number with the Messaging Service or purchase a new one. You can also purchase Phone Numbers through the Console, REST API, or Twilio CLI.

A Sole Proprietor campaign is only allowed one phone number to be approved for A2P under the Messaging Service. Add the Phone Number that you plan on using for A2P 10DLC messaging to the Messaging Service before submitting your Campaign registration. When your Campaign is vetted and approved, the 10DLC phone numbers within the Campaign's Messaging Service are registered for A2P 10DLC capabilities.

 

Select a use case

A Campaign represents a single messaging use case which describes the type of messages you send to recipients, such as marketing promotions or order confirmations. A Sole Proprietor Brand only have a single use case, which is called the Sole Proprietor use case.

 

Registration process

To register your Campaign, go to the Trust Hub page in your Console and begin the process listed under the A2P Campaigns tab. Click on the Create A2P Campaign button to get started on the campaign creation.

During Campaign registration, you can either select an existing Messaging Service or have a new one created for you.

 

Approval process

Once submitted, your Campaign undergoes a manual vetting process and has a pending status. This process can take between 5-10 days to complete. Twilio will contact you if any additional information is required. Once approved, you are able to start sending A2P 10DLC messages and register additional Campaign use cases.

 

 

Additional Information 

Trust Score & Throughput (MPS) for Sole Proprietor Brands

A Trust Score is a score assigned during Standard Brand registration with The Campaign Registry (TCR - the 3rd party that administers the US wireless carriers' new registration system). When an A2P Customer Profile registration for US 10DLC messaging is submitted to Twilio, we send this information to TCR for review. Twilio also submits the Brand for "secondary vetting," which assigns a score from 0 to 100 and gives access to higher default throughput and message limits toward US mobile carriers.

Sole Proprietor Brands do not go through "secondary vetting", are not assigned a Trust Score. Throughput is fixed based on their corresponding use case.