10DLC Vetting ProcessFollow
As 10DLC continues to evolve, the wireless carriers have identified a gap in the registration process - campaigns are not being registered appropriately and do not adhere to the carriers’ codes of conduct. As a result, there have been changes to the sole proprietor use case and now there will be additional review (vetting) completed on newly registered campaigns. There are 3 major changes associated with the campaign vetting process:
- All newly created 10DLC campaigns will be subject to manual review and will be placed in a “pending” status until this review is completed.
- $15 fee per vetting event.
- The provisioning flow will change so that a telephone number won’t be able to be associated with a campaign until it is fully approved.
On January 26, 2023, The Campaign Registry (TCR) is releasing a feature that eliminates the auto “accept” option for secondary Direct Connect Aggregators (DCA). This means all new campaigns will be defaulted to a pending status and will require manual review by the wireless industry’s main 10DLC Direct Connect Aggregator (DCA) in order to approve or reject the campaigns. Beginning January 10, 2023, newly registered campaigns that utilize Bandwidth as the Connectivity Partner will begin to go through the manual review process so you will start to see campaigns that appear to be approved in TCR but are still pending with the secondary DCA.
The manual review process will increase 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 initial review of a campaign, but it could be longer. Please follow the guidelines in our 10DLC Best Practices to ensure the most expedient and successful experience with campaign registration.
Campaigns in any state other than “approved” by the DCA will be subject to blocking from the wireless carriers. Unfortunately, at this time we don’t have a way to display the current DCA status of the campaign, but we are working with TCR to ensure this status is able to be surfaced to our customers in some fashion.
In addition to this review process, beginning January 31, 2023, the DCA mentioned above will begin implementing a $15.00 (USD) vetting fee on 10DLC campaigns. As currently understood, this is an additional new fee that will be charged per “vetting event.” While precise implications are still not entirely known, this may mean that if the DCA rejects a campaign two times before it is finally approved, Service Providers would be charged three vetting fees for a total of $45.00 USD for a single campaign’s vetting and approval process.
These fees will be passed through a month in arrears so you will see campaigns vetted in February charged on your April invoice.
We will begin preventing telephone numbers from being assigned to campaigns that have yet to be fully approved by the DCA once campaigns are put into Pending status by the secondary DCA. We are making this change to protect deliverability as some mobile network operators will not support traffic from campaigns in a pending or unapproved status.
When attempting to assign a telephone number to a campaign that isn’t fully approved by the DCA, you will receive error 12219, "Campaign with id 'XYZ' has not been accepted by DCA2 yet.". The new provisioning flow can be seen below:
Based on what we currently know, the happy path (straight line through the diagram at the top of the flow chart) can take five business days or more. If there are any rejections that cause a campaign to have to be updated by the customer and flow back through the vetting queue, that will prolong the process and timeline for a campaign to be fully approved.
This new vetting process will add additional time to have your campaign ready, but there is 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 are fully registered with each carrier:
- AT&T and Verizon - once TNs are assigned to a campaign, Bandwidth sends an API call to NetNumber to associate the TN with the campaign in the Override Service Registry (OSR).
- This process typically takes less than 30 minutes unless there is queueing at NetNumber.
- Completion of this step means AT&T and Verizon are fully registered and compliant.
- T-Mobile - there is an additional step to add the numbers and campaigns to T-Mobile’s A2P provisioning platform
- Once a TN is associated with an approved campaign, we utilize an API through the DCA that will add the TN(s) and campaign(s) to this platform.
- If we receive a positive response from this API, we will then send one final API call to NetNumber. This signifies to T-Mobile that a telephone number is fully provisioned when you send traffic.
- The T-Mobile portion of the provisioning can take anywhere from minutes to a few additional days depending on how much traffic is being sent into their provisioning platform at the time.
Below is the flow for the carrier registration steps once TNs are assigned to the campaign in Bandwidth’s dashboard:
Was this article helpful?
2 out of 7 found this helpful