Product changelog and announcements

We are committed to enhancing your integration experience and ensuring our customers can successfully send messages. However, we understand that sometimes errors occur, and we aim to provide you with the quickest guidance to resolve them. That is why we are updating the error code dictionary to improve clarity and usability. 

As of July 2024, the Reassigned Number package within the Lookup API is now Generally Available!

Reassigned Number allows you to Query the Lookup API with a phone number and the date you last verified consent to contact that user, and we will tell you whether the phone number has been reassigned to a new user since that date. Successfully querying this API prior to contacting a user grants you Safe Harbor from TCPA Violation Fees imposed by the FCC.

Additional Documentation on this feature can be found here

As of Friday July 25th, the SMS Pumping Risk Score package within the Lookup API is now Generally Available!

SMS Pumping Risk Score allows you to get real-time risk assessment on a phone number's involvement in SMS pumping fraud. It uses a proprietary risk assessment model that leverages data across our network including signals from Verify Fraud Guard as well as other signals associated with risky carriers, anomalous SMS traffic patterns, and low conversion rates.

Additional Documentation on this feature can be found here

Failed Brand Registrations can now be directly edited and retried through the Console. When a registration fails, the Console will display detailed error codes, allowing you to make necessary adjustments and resubmit seamlessly. Previously, editing Brand registrations was only possible through the API.

For a comprehensive list of Brand registration failures and guidance on addressing these issues, please visit our troubleshooting guide for 10DLC Brands.

Visit our Twilio Docs for more information on 10DLC Brand registration.

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.