Product changelog and announcements

Twilio now supports sending one tap and zero tap authentication templates on WhatsApp.

One tap autofill lets your customers authenticate by clicking a button in WhatsApp that triggers an activity that opens your app and delivers the password or code to it.

Zero tap authentication templates allow your users to receive one-time passwords or codes through WhatsApp without having to leave your app. If the zero-tap process fails, the code is still delivered in the WhatsApp chat.

More information on how to configure your existing authentication or new templates to support this functionality can be found in our documentation. 

Twilio now supports sending webviews on RCS through twilio/card. 

Webviews are new way for your customers to open links that keep them on the messaging thread. With webviews through Twilio, you can designate the height of the in-app browser that opens the webview. 

Additionally, webviews opens the door for more even richer interactions through RCS with integrations such as boarding passes and in-messaging payments. 

Between Monday, November 24, 2025 and Monday, January 5, 2026, Twilio will enter a Heightened Awareness Period (HAP) to help ensure reliable message delivery during peak traffic times, such as Black Friday and Cyber Monday. 

During this period, message sending rates to U.S. destinations will be monitored and may be limited at the account level for toll-free, short code, and 10DLC numbers.

Accounts that send high volumes of messages from short codes or toll-free numbers may be temporarily migrated to Market Throughput during the HAP; customers will be notified via email if their account is affected. Market Throughput does not affect 10DLC numbers, which will continue to live on Account Based Throughput.

We're excited to announce that we will be gradually rolling out a new version of the Messaging Insights UI starting today. New UI is designed for improved performance. 

Important action required after the roll out is complete for your users: Any previously saved filters and bookmarks will not carry over to the new interface. Please reapply your filters and update your bookmarks. To prevent confusion, consider deleting any old Insights bookmarks that no longer function with the updated UI.

Compliance Toolkit is now available in Public Beta, allowing you to use Artificial Intelligence and machine learning to help manage compliance obligations with respect to certain local regulatory or compliance requirements.

To start using Compliance Toolkit, Opt in through the Twilio Console and review the detailed setup instructions in our developer documentation.

We’ve made an important update to A2P 10DLC Phone Number Registration events in Twilio Event Streams — now including the Messaging Service SID in all related events.

With this enhancement, you can directly identify which A2P Campaign a phone number is associated with by referencing the messaging_service_sid field in the 2.0 schema version. This improves traceability and helps streamline debugging, monitoring, and automation workflows tied to number registration.

The following Event Streams now include the messaging_service_sid field:
- com.twilio.messaging.compliance.number-deregistration.pending
- com.twilio.messaging.compliance.number-deregistration.successful
- com.twilio.messaging.compliance.number-registration.pending
- com.twilio.messaging.compliance.number-registration.successful

To learn more about A2P Notifications through Event Streams , check out our guide docs.

We’ve made a key improvement to Authentication+ to support programmatically triggering a new 2FA verification email for A2P 10DLC Brand registrations that have failed. 

Alongside the endpoint, we’re introducing a set of dedicated 2FA error codes that surface precise failure reasons and point you to the fastest remedy, so your users can complete brand verification with fewer support tickets and less manual work.

To learn more about Authentication+, check out our Support Article and Twilio API Docs.
 

Studio now supports the ability to shorten links within your message body when using the Send Message and Send & Wait For Reply widgets. You can also shorten links to track customer engagement with click events.

All ID fields specified in the Twilio Content Content APIs such as in Twilio cards will be returned in Button Payload in a uniform way.

We will return the exact payload specified without 64 bit encoding to align button behavior.  

To specify a Button Payload, pass in an ID field into the button actions array within a button object. Examples can be found in the Twilio docs. Button Payloads will be returned in the inbound webhook. Billing may apply. To learn more see our docs here.