10DLC Registration

The registration process for 10-digit long code (10DLC) ensures that your numbers are compliant with US messaging guidelines. 

10DLC registration process consists of the following steps:

1. Buy a number.
2. Create and register a brand.
3. (optional) Vet your brand.
4. Create and register a campaign, connected to a number.
5. Campaign review process.
6. Go live.

The following sections describe the registration process steps in more detail.

Buy a number

To send 10DLC traffic, you need to have a dedicated number. You can buy numbers easily via Infobip using:

• Numbers App
• Numbers API

You may already have an existing number that you wish to use in Infobip, and it is possible to use this rather than purchase a new number. 

You can request number import over Numbers App, selecting the Long Code and US option. Describe your current setup in the comment section.

For more information about buying or importing a number, see Numbers.

Create and register a Brand

The term brand refers to a company's business and legal information. Brand registration involves providing this information to The Campaign Registry (TCR), which works on behalf of certain mobile network operators to verify your company. For example, in the US, both T-Mobile and AT&T use TCR's verification process, which means that until TCR verifies your brand, you can't send messages from a 10DLC number to those operators.

You need to register a brand only once per company. Brand registration incurs a one-time registration fee. For pricing details, see North America Pass-Through Fees.

Use the Number Registration API to register a brand programmatically. This feature lets you enter the required information and submit it directly to TCR. The Brands screen lets you see the status of your brand. Once you submit your brand registration, TCR will verify if all the information checks out. If the correct information is provided, brand registration is immediate.

Vet your Brand

To ensure a high throughput, or to enable non-US brand's traffic to be terminated, you can vet your brand. Trigger the brand vetting over the Number Registration API.

For more information about brand registration and vetting, see Brands.

Create and register a Campaign

To send messages in the US, certain mobile network operators require that you submit a campaign. A campaign contains information about the messages you intend to send. Use the Number Registration API to create and submit campaigns, which are then propagated to The Campaign Registry (TCR).

For each campaign, you need to provide:

• Brand to which campaign would be associated
• Basic information about your campaign
  • campaign name, summary, use case
• Description of opt-in methods
• Examples of messages
• Support contact information and terms and conditions
• Numbers that would be used with the campaign (up to 49 numbers)

For more information about campaigns, see Campaigns. For details about pricing, see North America Pass-Through Fees.

Campaign review process

Once you've created the campaign creation and submitted it for registration, a two-level compliance review process will be triggered:

1. Review by Infobip Compliance Team - takes up to 5 working days
2. Review by underlying connectivity provider - can take up to 5 working days and is charged extra

Once fully approved, campaign is also registered with T-mobile and you can start sending traffic.

In case of rejection, the campaign will get deregistered, and you will be notified via email. You will need to submit a new campaign and will be able to use the same number.

You will get charged for TCR campaign and brand fees, regardless of the review outcome. If you've registered your campaign directly with TCR, you will be charged by TCR. For campaigns that pass internal Infobip review, clients will be charged an additional pass-through fee for the compliance review by the underlying connectivity provider.

Go live

Once your number has been procured, brand and campaign have been fully registered and approved, your campaign can go live!
For more information about throughput, see (link to throughput section).