Twilio Changelog

<Connect><ConversationRelay> is a TwiML noun and Service Provider Interface (SPI) for building genAI-powered virtual agents. ConversationRelay makes voice AI integrations straightforward, so you can focus on delivering the self-service experiences customers expect without diving into the complexities of voice technology. It combines low-latency speech-to-text and text-to-speech capabilities with human-like conversational pacing, orchestration, and seamless interruption handling through a websocket API. Bring your own large language model (LLM) and let Twilio take care of the rest. 

New features included with this release:

• ElevenLabs is now the default TTS provider. A new TwiML param “elevenlabsTextNormalization” specifies whether or not to apply text normalization while using the ElevenLabs TTS provider.

• New TwiML param “reportInputDuringAgentSpeech” specifies whether your application receives prompts and DTMF events while the agent is speaking

• New TwiML param “debug“. Options are debugging, speaker-events, and tokens-played. The debugging option provides general debugging information. speaker-events will notify your application about agentSpeaking and clientSpeaking events. tokens-played will provide messages about what's just been played over TTS.

Check out the blog post to learn more. If you’re ready to dive right into code you can find the docs here. We can’t wait to see what you build!

Voice Intelligence has been renamed to Conversational Intelligence – reflecting our expansion into analyzing conversations across all customer touchpoints. Businesses can now unlock unified AI understanding across Voice, Messaging & Virtual Agents. 

Building on the foundation of Voice Intelligence's AI-powered transcription and language analysis capabilities, Conversational Intelligence introduces powerful new features designed for today’s cross-channel engagement landscape:

🤖 AI Agent Observability with ConversationRelay (Generally Available)

A native integration with ConversationRelay empowers you to monitor and refine interactions between customers and Twilio-powered AI agents to ensure quality and fine-tune performance over time.

✨ Generative Custom Operators (Public Beta)

LLM-powered custom operators let you easily define use cases like quality assurance checks, compliance flagging, or competitive insights — tailored to your business — all with just a few simple instructions. 

💬 Conversational Intelligence for Messaging (Private Beta)

Gain full visibility into customer interactions across SMS, WhatsApp, and web chat. Analyze messaging conversations alongside voice data to uncover trends, preferences, and patterns throughout the entire customer lifecycle.

Want to learn more?

• 👉 Explore the Conversational Intelligence docs
• 👉 Get building using Conversational Intelligence with ConversationRelay
• 👉 Create your first Generative Custom Operators
• 👉 Request access to the Conversational Intelligence for Messaging Private Beta

––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––

Important Note: Voice Intelligence customers do not need to take any action as a result of these changes, and Transcription & Language Operators will continue to function normally. 

Twilio, by default, handles standard English-language reply messages such as STOP, UNSUBSCRIBE, END, QUIT, STOPALL or CANCEL for US and non US Long Code numbers, in accordance with industry standards. As of May 13, 2025, Twilio added REVOKE, and OPTOUT as additional opt-out keywords.

Learn More: Update to FCC's SMS Opt Out Keywords

Beginning today, agents can now leave and pause a task for any Flex Conversations channel, such as SMS or webchat. We’re expanding this functionality from only email tasks to all Flex Conversations tasks. 

Agents can also enter wrap-up after they leave or pause a task, so they can perform final wrap-up activities before completing a task. This ensures that agents have time to document their actions and also provides a more accurate report of their status.   

In addition, administrators and developers can now configure a webhook URL and subscribe to notifications about Interactions API events that occur during conversations. 

Event notifications can provide information about customer interactions or enable developers to trigger additional workflows after certain events. For example, when used with leave and pause functionality, Interactions event notifications enable you to trigger custom logic when a customer responds to a conversation the agent has left.

With SAML-based SSO, users can now automatically join a primary team when they sign in to Flex. In addition, when supervisors sign in to Flex, they can automatically gain oversight of multiple teams as the assigned owner. By using attributes from your identity provider (like Okta), this update simplifies team assignments right from the start. 

To learn more about Flex Teams and how to set up SSO, see Teams in Flex and Configuring SSO and IdP in Flex.

We’re excited to announce that Flex UI 2.12.0 is now available. This release includes:

• A new Flex UI action for Conversations messages that lets you send rich text using a content template and associated variables.

• You can now localize dynamic strings, such as agent status, in custom Flex plugins.

Throughout Flex UI, you'll find feature and UI enhancements, bug fixes, and more. 

For complete details, see the Flex UI release notes for 2.12.0.

Accept PIX Payments on WhatsApp with Twilio/pay
Move from conversation to conversion with native in-chat payments

We’re excited to announce support for PIX payments on WhatsApp using Twilio/pay templates. You can now guide customers through completing a financial transaction directly in WhatsApp.

Use Content Templates with Twilio/pay to:

• Send Order Details messages with a PIX copy code button that opens the user’s banking app

• Send Order Status updates as payment progresses through stages like pending, shipped, or completed

• Display itemized order summaries, expiration details, and total amounts—all within a single message

To enable this, your business must:

• Have a valid WhatsApp sender in Brazil

These templates support variables for payment ID, merchant name, itemized details, and expiration. Rich metadata can be passed to payment processors, with updates automatically sent to users through Order Status messages.

Ready to embed seamless checkout into your messaging flows?
Explore the docs to get started:
twilio/pay

We’re making it easier to troubleshoot Toll-Free Verification (TFV) errors!

Starting May 15, 2025, we’ll begin rolling out more specific and detailed error codes for TFV requests. These new codes are designed to give you clearer, more actionable feedback when a submission doesn’t go through— so you can fix issues faster and keep things moving. 

Don’t worry, the old codes will still be supported— but we think you’ll find these new ones to be more helpful.

What’s changing?

Right now, TFV error messages can be a bit vague. With this update, you’ll start seeing granular error codes that explain why a verification was rejected. These new codes will appear in: 

• API responses

• Webhooks

• Email notifications

• Twilio Console

What this means for you

If you’re a customer that has set up custom logic to handle TFV errors—like mapping them in dashboards or internal tools—be sure to review and update your error mapping to reflect the new codes.

For more details, check out the Twilio API Docs and the Twilio Error Code Dictionary.

We hope this update makes your TFV experience smoother and more efficient. 

Thank you for building with Twilio!