Product changelog and announcements

Several countries and networks require registration for Alphanumeric Sender ID, Phone Numbers, or Short Codes. When you have registered a Sender with Twilio, we automatically override the value provided in the "From" parameter with your registered Sender on any messages sent to that destination.

It’s now easier for large organizations to manage their Toll-Free records efficiently.

Customers registering for Toll-Free numbers can now retrieve all Subaccount verification records under a main account by using the new ‘IncludeSubAccounts’ parameter. This update simplifies the process, eliminating the need for separate authentication and retrieval for each Subaccount. 

Visit our Twilio Docs for more details.

Use twilio/catalog to send items and services directly to your customers on WhatsApp and guide them through a transaction

Twilio now supports a messaging throughput of 80 MPS (messages per second) by default per WhatsApp sender for all outbound traffic. This throughput applies to both messages containing text-only and messages containing media files. The text-only throughput for a WhatsApp sender can be increased up to a maximum of 400 MPS by request for businesses requiring it to send high and sustained messaging volumes.

A WhatsApp sender’s throughput in messages per second (MPS) can now be viewed in the Twilio Console on the WhatsApp Senders page.

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.