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. 

View updates for Connections, Protocols, Unify, and Engage on Segment Community.

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. 

As of September 16, 2025 the Twilio Console experience has been revamped to enable access to the latest packages available in Lookup!

The Twilio  Console now allows you to try out the various Lookup packages without needing to implement the APIs. You can now  try all packages like Caller Name, Line Type Intelligence, Identity Match, SIM Swap, Line Status, Reassigned Number, and SMS Pumping Risk Score (some of these packages require onboarding prior to testing via console). You will no longer have access to the V1 version on the lookup API via the console.

Voice Conference Recordings are now recorded and stored in dual-channel by default in all regions!

ConversationRelay now officially supports Deepgram’s latest speech-to-text model, nova-3. Deepgram nova-3-general will be the default model (e.g. transcriptionProvider and speechModel combination) for all new customers; current customers will not be impacted. In addition to nova-3-general, the nova-3-medical version is also available. Lastly, we’ve updated ConversationRelay’s “hints” parameter to include support for Deepgram’s newer “keyterms” feature for nova-3.

Support for nova-3’s multilingual language option will come in a subsequent planned release.

To learn more about ConversationRelay please check out the docs here. We can’t wait to see what you build!

As of September 11, 2025, Twilio Voice, Video, and Conversations will no longer support TLS v1.0 and v1.1 for the following endpoint:

sdk.twilio.com (used to host assets and SDK documentation related to Voice, Video, and Conversations)

Any connection attempts made after this date will fail. Due to TLS security vulnerabilities, we will stop offering TLS 1.0 or 1.1 protocols on this date; only the TLS 1.2 protocol will be supported.

When we first introduced the CardConnect Pay Connector, our goal was simple: make it easier for customers to securely collect payments over the phone without adding extra costs. 

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.

As of September 10, 2025, Twilio Flex no longer supports TLS v1.0 or v1.1 for the assets.flex.twilio.com endpoint, which hosts assets and SDK documentation related to Flex UI. If you try to connect to this endpoint using TLS v1.0 or v1.1, your request will fail. To make sure your request uses a supported protocol, use TLS v1.2 or later.