Product changelog and announcements

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.

We have begun enabling accounts for improved message creation API error visibility in  SMS logs and Messaging Insights in the Twilio Console as well as when you list messages via the Programmable Messaging API. Full details are available here. When your account is enabled, the banners on those console pages 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.

HTTP callbacks (webhooks) for inbound WhatsApp messages that originate from a Meta Click-to-WhatsApp advertisement now include a new ReferralCtwaClid parameter. This parameter contains the unique identifier generated by Meta representing the WhatsApp message conversation initiated by a user’s ad click. Customers can now use this parameter to integrate their WhatsApp business messaging events with Meta’s Conversions API (see ctwa_clid) to optimize Meta’s ads targeting and performance measurement.

Learn more about how to create Click-to-WhatsApp advertisements with Twilio from our blog post.

Twilio Messaging MaxPrice API parameter will be deprecated starting June 3, 2024. 

We are excited to announce an enhancement in the A2P 10DLC Brand registration process. In our ongoing efforts to streamline and improve the user experience, we now have standardized error codes for any failures or issues encountered during Brand registration. These error codes will be directly available through the errors attribute on the Brand. 

With this release, it’s important to note that brand_feedback and failure_reason will be deprecated in an upcoming release.  If you have used these attributes in your integrations, we strongly advise transitioning to the new errors attribute due to its pending deprecation and limited information. 

Check out the updated Brand registration Twilio docs for more information. or a detailed list of all error codes please visit Twilio Error and Warning Dictionary.