Skip to main content

10DLC campaign vetting and TN provisioning process

Updated over 2 weeks ago


Due to the manual nature of the 10DLC vetting process, we expect turnaround times of 3-5 business days for the initial review of a campaign, but it could be longer. Please note this review is done by the downstream Direct Connect Aggregator (DCA), not The Campaign Registry (TCR).

A note about billing:
Regardless of campaign vetting status, all campaigns (except for Political use cases) have a 3 month minimum commitment. This means that we bill monthly, for a minimum of 3 months. At the end of the initial 3 month period, campaigns renew on a month-to-month basis. Campaigns registered using the Political use case do not have any minimum commitment and also renew on a month-to-month basis.


As 10DLC continues to evolve, the wireless carriers identified a gap in the registration process - campaigns weren't being registered appropriately and didn't adhere to the carriers’ codes of conduct. As a result, there have been changes to the sole proprietor use case, and additional review (vetting) must be completed on newly registered campaigns. There are 3 major changes associated with the campaign vetting process:

  1. All newly created 10DLC campaigns will be subject to manual review and will be placed in a “pending” status until this review is completed.

  2. $15 fee per vetting event.

  3. The provisioning flow will change so that a telephone number (TN) won’t be able to be associated with a campaign until it's fully approved.

Pending status

The manual review process associated with campaign vetting increases the time it takes for campaigns to be ready for 10DLC traffic so please plan accordingly and register as early as possible. We expect delays of several days for the initial review of a campaign, but it could be longer. Please follow our 10DLC registration best practices to ensure the most expedient and successful campaign registration experience.

Campaigns in any state other than “approved” by the DCA are subject to blocking from the wireless carriers. If you'd like to check the status of your campaign, you can use the CSP portal (if you're registering directly with TCR). Once the campaign is fully approved by the secondary DCA, all carriers will show Yes in the Elected DCA column - this will allow you to receive the DCA_COMPLETE webhook from TCR. We've added this status to our GET API. In the example below, you would not receive the DCA_COMPLETE webhook until all carriers are flipped to Yes in the Elected DCA column.

2023-02-09_20-29-52.png

Vetting fee

Currently, Bandwidth charges a vetting fee once the campaign is approved or denied by our vetting partner (passing through their charges to you). Due to Bandwidth’s expertise at vetting, you can expect that we will catch non-compliant campaigns before they are sent to our vetting partner where a fee would be applied. To this end, we are changing our billing model to charge when Bandwidth rejects a campaign submission and when the campaign is fully approved by our downstream vetting partner (a diagram of this change can be found here). If you are submitting quality campaigns to Bandwidth, this could result in lower vetting charges overall. Some customers have already contracted for this billing change, but for any customer not contracted, this shift will begin on October 1, 2025.

Provisioning process

Once campaigns are put into Pending status by the secondary DCA, Bandwidth prevents TNs from being assigned to campaigns until the campaign is fully approved. We're making this change to protect deliverability as some mobile network operators will not support traffic from campaigns in a pending or unapproved status. Unregistered traffic is also being blocked with error code (4)476 or (4)773, so a campaign must complete vetting prior to numbers being assigned and traffic being sent.

Important: You must import your campaign into the Bandwidth App in order for it to be shared with our secondary DCA. The date you import is when it will be shared downstream.

When attempting to assign a TN to a campaign that isn’t fully approved by the DCA, you'll receive error 12219, "Campaign with id 'XYZ' has not been accepted by DCA2 yet." The provisioning and vetting flow can be seen below:

The happy path (straight line through the diagram at the top of the flow chart) can take 3-5 business days or more.

Any declines that cause you to have to update the campaign and flow it back through the vetting queue will prolong the process and timeline for it to be fully approved. Once declined, the campaign does not automatically deactivate, but you can edit or manually deactivate it (please note that you'll still be charged for the first 3 months of the campaign).

If you're editing your campaign after rejection and need to resubmit it to the secondary DCA, please re-import the campaign into the Bandwidth App (via UI or API), which will trigger us to share the campaign with the DCA again. Bandwidth is working to eventually support the "nudge" function from TCR, but in the meantime, re-importing into the Bandwidth App will achieve the same function on the back end.

Note: Any time a campaign is re-imported while in a rejected status, we'll share the campaign with the downstream DCA. It's best practice to only re-import the campaign once you're fully done making updates and are ready for it to be revetted. Please do not re-import the campaign multiple times, as it may result in unnecessary vetting events.

This new vetting process will add additional time to have your campaign ready, but there's one more component to registration before your traffic is considered fully 10DLC compliant with all carriers. After TNs are assigned to a campaign, the following steps are taken to ensure you're fully registered with each carrier:

    • Once a request is made to Bandwidth to associate a TN with a campaign, we utilize an API through the DCA that will add the TN(s) and campaign(s) to T-Mobile's platform (T-Mobile requires an additional step to add the numbers and campaigns directly to T-Mobile’s A2P provisioning platform).

    • If we receive a positive response from this API, we'll then send an API call to NetNumber to add the campaign ID to the TN (which covers AT&T and Verizon registration) and complete the T-Mobile portion of the provisioning. This signifies to T-Mobile that a TN is fully provisioned when you send traffic.

    • The T-Mobile portion of the provisioning can take anywhere from minutes to a few days, depending on how much traffic is being sent into their provisioning platform at the time. The NetNumber updates happen shortly after T-Mobile completes, typically taking less than a few minutes.

How to resubmit vetting - Registering through Bandwidth

With the introduction of the new provisioning process, you may find your campaign in a Pending, Declined, or Accepted state. You can find its status in the Vetting column on My Campaigns page.

2023-03-16_12-02-22.png

If your campaign was declined, you can click the campaign ID to learn more about the decline reason.

2023-03-16_12-03-59.png

The decline reason will tell you what needs to be adjusted on the campaign in order to get it approved by our aggregator. Once you've made all the necessary edits, click Resubmit Vetting.

Important: Please resubmit the campaign only once you're done making all of your edits.

Screen_Shot_2023-03-16_at_10.50.06_AM.png

If your campaign gets accepted after you resubmit it (or if it's accepted after the initial submission), the Campaign Vetting status will be Registered. The Resubmit Vetting button will be greyed out since you won't need to resubmit the campaign.

Screen_Shot_2023-03-16_at_10.50.26_AM.png
Did this answer your question?