Product changelog and announcements

As announced on May 28, 2024, Google will end of life (EOL) Google Business Partners (GBM) in July 2024. You won’t be able to start new conversations after July 15, and the Twilio GBM API and Google Business Profiles chat will no longer work after July 31, 2024.

You should replace any brand-managed entry points (like URLs or web widgets) with an alternative messaging option by July 15, 2024, to avoid message disruption. You don’t need to take action if you use Google entry points for business messages.

For more information, review Update on Google Business Messages.

Customers registering 10DLC Brands and Campaigns for A2P Messaging can now create subscriptions to receive detailed error codes through Event Streams when a Brand or Campaign registration fails.

This enhancement uses Twilio's Event Streams product to push error codes directly to customers, eliminating the need to query the Brand and Campaign endpoints or check the A2P Console Pages.

Existing users must update to Schema version 2 for the following events to start receiving error codes:

• Campaign Registration Failure 
• Brand Registration Failure.

Check out the Event Streams product or documentation on how to get started!

We're enhancing our trust hub customer profile rejection process by introducing error codes, which will include the description, possible causes, and possible solutions. The current rejection reasons will be part of the error description. This change aims to provide clearer information to our customers when a profile is rejected.

We have begun enabling accounts for error log tracking of message creation API errors. Full details are available here. When your account is enabled, the banners on the messaging error log console page will update to reflect that your account is enabled. Note that accounts will be enabled on a per-account-sid basis over the coming weeks; thus certain sub-accounts may gain access before others.

We are excited to announce an enhancement in the Toll-Free Verification process. In our ongoing efforts to streamline and improve the user experience, we now support multiple rejection reasons, new rejection error codes have been added and existing rejection error code descriptions have been improved. These changes are supported in the Toll-Free Verification API, Console, Event Streams - webhooks and email notifications-about a rejected toll-free verification.

With this release, it’s important to note that the Toll-Free Verification API’s LIST, GET and webhook still supports a single rejection reason, but we strongly advise transitioning to the new “rejection_reasons” attribute, so that you pick up all the rejection reasons. 

Previous releases have included this metadata, which you may also find useful when processing a rejection: 

  "rejected_on": "2024-04-05T22:01:58.076Z",

  "edit_expiration": "2024-04-05T22:01:58.076Z",

  "edit_allowed": true,

Additionally, the Twilio-Rejected event webhook now includes the phone number DID: 

  "phonenumber": "+18002225555",

For a detailed list of all toll-free verification error codes please visit Twilio Error and Warning Dictionary.  

As of 1st April, 2024,  SMS Pumping Protection for Twilio Programmable Messaging is generally available to prevent fraudulent SMS traffic and lower its significant costs. This feature automatically detects messaging traffic driven by SMS pumping and blocks it from being sent.

SMS Pumping Protection requires no configuration. Enable it in the Twilio Console and Twilio will do the rest. 

The performance of the feature can be monitored via existing Messaging Insights & the newly launched SMS Pumping Insights.

To further customize your SMS pumping protection experience, we have also launched RiskCheck and the Global Safelist.

Starting May 9, 2024, Twillio will remove any phone range blocks on your account that have been active for longer than 30 days.

In the past, some accounts received a notification that fraud was detected on those accounts and that Twilio enacted blocking for certain prefixes. These blocks were internally set using the messaging opt out functionality which is why outbound messages destined for these blocks fail with Twilio error code 21610. As there is no way for customers to control this functionality and since fraud activity tends to dissipate after blocking, we will be removing these blocks from those accounts.

What do you need to do? We recommend regularly reviewing your SMS geo permissions and only enabling countries where you intend to send messages and incur messaging costs. This is a more efficient method to prevent unwanted messages without the risk of blocking legitimate traffic. To enable or disable Geo Permissions, go to your Console’s Geo Permission settings.

As of 1st April, 2024, the Global Safelist API is now generally available for Twilio Programmable Messaging. Twilio's Global Safelist API empowers you to manage trusted phone numbers that they are not blocked by Twilio’s algorithms for SMS Pumping Protection on Twilio Programmable Messaging.