Key Dates - Past changes

Description

Aug 1st, 2023

Number linking & unlinking statuses

We are implementing asynchronous flows for linking and unlinking numbers, which will result in the following changes:

• The current "Pending" status will become "Linking"
• The current "Approved" status will become "Linked"
• Introduction of a new "Unlinking" status

Additionally, you can already start using the asynchronous unlinking flow by adding "?async" to the URL of the request.

Those changes are being introduced to reduce errors related to failed linking / unlinking requests when propagating the number configuration with our partners and carriers.

Apr 6th, 2023

Brands can now update their Entity type, EIN, EIN issuing country, and legal name

Breaking change

From April 6th, 2023, 10DLC brands can update the following attributes:

• Entity Type
• EIN
• EIN Issuing Country
• Legal Name

Note: If the brand has any of the following:

• Active campaigns
• Active external vet

The update will not be possible.

Note also that updating any of those attributes will set the brand identity status to "unverified", and you will be required to re-verify the brand ($4).

These changes will only apply to our public API. Customers using our dashboard will still need to register a new brand in some cases.

Apr 3rd, 2023

All recurring campaigns must provide an "Opt-in Message" during the registration

Breaking change

All 10DLC recurring campaigns must now provide an "opt-in message" during the registration.

Exemption: 2FA use case

Note: the opt-in keywords remain required only when the campaign has an SMS opt-in mechanism.

Apr 1st, 2023

Introducing 10DLC Brands "Pending" status

As a result of recent on-going issues with The Campaign Registry causing brand creation requests to fail, we have decided to decouple the brand creation and verification phases, allowing you greater visibility into the status of your request. The newly created brand will show as "pending" until it's confirmed to be "verified" or "unverified". Please note, registering a campaign requires successful verification or external vetting. Please refer to our Brand verification requirements article for additional details.

Mar 20th, 2023

The following attributes will default to 'true' for all new 10DLC campaigns registered:

• number pool
• subscriber opt-in
• subscriber opt-out
• subscriber help

Please note the following:

• In order to simplify the campaign registration process and to avoid mistakes, we are enabling by default the "number pool" attribute on all 10DLC campaigns. This attribute allows you to request a number pool for a campaign, but does not actually enable it. It is also a Boolean that cannot be updated once a campaign is registered in The Campaign Registry (TCR).
• Opt-in, Opt-out and Help Booleans are required for all campaigns. To simplify the registration process, we will always consider those values "true".
• The "subscriber opt-in" is about the existence of an opt-in mechanism (consent model). This must always be 'true', however, specifying an opt-in keyword and message is only required for Text-to-Join opt-in.
• Subscriber keywords and messages will still need to be provided when applicable.

The above changes are not breaking, and we will continue to accept requests specifying these attributes. However, we will ignore the value provided in the request at this time and no action will be applied. 

Mar 20th,

2023

All Sole Proprietor brands in "self-declared" status will be removed

The Campaign Registry (TCR) will delete every Sole Proprietor brand that did not complete the data validation check before march 20th, 2023 and still have a "self-declared" identity status.

Customers that have successfully completed the data validation check (by updating their brand and adding the "mobile phone" attribute) will have one month to complete the OTP verification step.

The OTP verification step is currently only available via our API. More information here.

Nov 21st, 2022

Implementation of a manual review process for all newly created 10DLC Campaigns

Breaking change taking immediate effect

Some carriers have imposed new requirements with very short notice and it means that from now on, our compliance team has to manually review every single 10DLC Campaign prior to submitting it to our connectivity partner. This means that our customers can expect some delays until the campaign is approved and they can start linking numbers & send traffic on a campaign.

We kindly ask our customers to take this into account when planning their US messaging flows and plan ahead to create campaigns a couple of weeks before they need to be sending traffic to avoid disruption.

We apologise for the short notice on this breaking change and understand your frustration. We will be making further changes into our systems to try and accommodate for as many of the changes as possible and ensure that most campaigns submitted provide all the required information.

Note that a further range of new requirements have equally been added to campaigns, we are working on a specific dedicated article to explain more on those and will link it on this page in the near future.

Nov 1st, 2022

Removal of un-registered traffic

Tier-1 US carriers required all customers to complete 10DLC registration effective March 1st, 2022 (notification). Customers must migrate to 10DLC as soon as possible to avoid higher carrier filtering, reduced deliverability, and blocked messages. 

Beginning Nov 1st, 2022, new customers who send from a +1 geographic number terminating to the U.S. without a linked campaign ID will receive error code 39. (Illegal Sender Address for U.S. destination) 

Dec 31st, 2022

Deprecating "Affiliate Marketing" and implementing "Terms and Conditions"

(breaking change)

TCR is deprecating the Affiliate Marketing attribute in 10DLC Campaigns as its meaning is confusing to customers and seldom used.

TCR is also implementing a new Terms and Conditions required attribute.

The "Terms and Conditions" in 10DLC campaigns is not about the customer having implemented or offering clear terms and conditions related to recipient receiving messages from that campaign, but it is about the customer agreeing with TCR's 10DLC terms and conditions.

Every 10DLC campaigns created after a date not yet determined by TCR, will be required to acknowledge their understanding of the terms and conditions of the 10DLC regulation and agree to those terms and conditions in order to submit a new campaign.

We will update this page when we have a clear date on when this change will apply.

Nov. 17,

2022

New required attribute to create 10DLC campaigns

(Breaking change)

TCR is introducing a set of new attributes for 10DLC campaigns, some of them will be required from November 17th. Please read this article for the details:

10DLC - New requirements for 10DLC Campaigns

Nov. 3,

2022

Sole Proprietor v2

(Breaking change)

TCR and the US carriers are implementing a new version of the Sole Proprietor brand & campaign. Please read this article for more:

10DLC - Sole Proprietor v2

The changes include price changes for Sole Proprietor and Low Volume Mixed campaigns

Sept. 1,

2022

New Filtering capabilities

The GET endpoints for 10DLC now offer the option to filter the set of results. Please check this page for more information:

https://developer.vonage.com/messages/10-dlc/filter

Note that the filtering of brands is also now available on our customer dashboard

Beginning Sept. 15, 2022

10DLC Platform Upgrade:
SMS Queuing*

(Potential Breaking Change)

*MMS queuing will be available in early 2023. If you are sending a MMS campaign, you will still receive rate limit errors for any MMS message that exceeds 10DLC carrier limits.

Messages sent from a 10DLC number to +1 US destinations that exceed 10DLC throughput rates will no longer be rejected as part of the API request. Instead, messages will be queued in our system and sent to the supplier at the provisioned mobile network rate associated with your brand and campaign. (Minus T-mobile/Sprint networks)

These queues can also hold up to 72 hours' worth of message segments, based on the sending rate allocated to the applicable brand/campaign associated with the ‘from’ number.

Account limit throughputs will remain unchanged and you will still receive a throttling error if you exceed your limit.

You may have to review your existing logic or build new logic to account for these changes.

Sept. 29,

2022

Campaign "resubmit" endpoint (Public API)

For the Customer Dashboard

Customers can now resubmit an existing campaign to request specific MNO (Mobile Network Operators) to re-evaluate the throughput they allow for a specific 10DLC campaign. 

When a 10DLC brand's vetting score is updated, each of the campaigns already existing under that brand are not automatically resubmitted to the MNOs. This decision from TCR is to prevent campaigns from potentially being updated with less throughput than before. Therefore, TCR has implemented this feature to allow customers to manually trigger this action.

Please be mindful of the risk of seeing the throughput of your campaign being reduced. 

Note: Customers having imported campaigns created directly on TCR's portal need to trigger this action using TCR's API / portal.

10 DLC Platform Upgrade - SMS Queuing*

(Potential Breaking Change)

*MMS queuing will be available in early 2023. If you are sending a MMS campaign, you will still receive rate limit errors for any MMS message that exceeds 10DLC carrier limits.

Messages sent from a 10DLC number to +1 US destinations that exceed 10DLC throughput rates will no longer be rejected as part of the API request. Instead, messages will be queued in our system and sent to the supplier at the provisioned mobile network rate associated with your brand and campaign.

These queues can also hold up to 72 hours' worth of message segments, based on the sending rate allocated to the applicable brand/campaign associated with the ‘from’ number.

Account limit throughputs will remain unchanged and you will still receive a throttling error if you exceed your limit.

You may have to review your existing logic or build new logic to account for these changes.

MNO status name change

(Breaking change)

TCR is changing the way Mobile Network Operators designate a campaign as "APPROVED", the new status will be "REGISTERED".
This may impact customers if they implemented logic before starting to link numbers to a campaign or start sending messages via specific campaigns / numbers.

Vonage will implement this change in the coming weeks. We will first run the new status to all the new campaigns, then will gradually but quickly replace existing campaigns' statuses to "REGISTERED" to remain aligned with TCR.

If you have implemented logic based on the status MNO return, you will need to accept both "APPROVED" and "REGISTERED" status from September 1st, 2022
You do not need to make any changes to the API endpoints called.
You do not need to make any changes if you are not implementing logic based on this status.

New API endpoint to allow importing TCR campaigns into Vonage

We have released a new API endpoint to allow approved customers to import campaign they created directly on the TCR portal into Vonage.

If you would like to use this endpoint, please note the following:

• You need to have a contract with TCR and have created both your brands and campaigns directly via TCR
• You need to reach out to your Vonage Account Manager so they can enable the feature for your account(s)

Once the feature is enabled, you can make the following call from your parent account (main api_key):

POST /partnercampaigns/import

{

  "account_id": "abcdef01",

  "campaign_id": "string",

  "label": "string"

}

where "account_id" is the api_key of the account where the campaign needs to be imported; and label is an optional "friendly" name the customer can define to recognise that campaign.

The API description will be updated to reflect the changes soon here.

Update to 10DLC campaigns creation rules

(Breaking change)

For Standard Brands:

- Low Volume Mixed campaigns require no vetting

- Political campaigns may require a Political vetting

- All other campaigns require a standard vetting

For Sole Proprietor brands:

- Sole Proprietor campaigns require no vetting

- Political campaign require a political vetting (Federal level political vetting forbidden)

Update to Campaign creation endpoint:

POST /brands/{brand_id}/campaigns

(Breaking change)

TCR is removing the "vertical" attribute from this endpoint.

No changes to existing campaigns

Update to the vetting importing endpoint

PUT /brands/{brand_id}/vetting/requests/{vetting_request_id}

(breaking change)

- Removing vetting_class from the payload as it is not required by TCR anymore

- Renaming "vetting_request_id" by "vetting_id" for consistency

- Moving the "vetting_id" attribute from the URL to the body

PUT /brands/{brand_id}/vetting/requests/{vetting_request_id}
{
"evp_id": "858FC02",
"vetting_class": "abcd123",
"vetting_token": "abcd123"
}

Will become

PUT /brands/{brand_id}/vetting/requests/
{
"evp_id": "858FC02",
"vetting_id": "abcd123",
"vetting_token": "abcd123"
}

Note: the vertical attribute will not be returned for existing campaigns anymore either.