Product changelog and announcements

Sentiment Analysis, Summarization and Entity Recognition Language Operators are now available in Public Beta.

These three new Natural Language Understanding Operators are available in Voice Intelligence to get valuable insights from your call transcriptions.

Starting February 12th, 2024, we are improving visibility of inbound messages by including redacted One Time Passcode (OTP) messages. Twilio does not generally allow receiving inbound OTP messages on Twilio numbers. This prevents abuse of Twilio numbers. Previously, these inbound messages were filtered before being processed onto your Twilio account. In order to provide better visibility for all inbound traffic, Twilio will allow you to see these messages, but will be redacting the passcode itself and setting a failed status with error code 30038.

Starting February 13th, 2024, as part of out messaging error visibility improvements, we will be rolling out improvements to our console error logs. We are enhancing error coverage to include outbound messaging errors which previously weren't available in the console error logs. Previously, these errors were only accessible through the API, messaging logs and insights, and via message status callbacks. This visibility improvement empowers efficient troubleshooting and full operational transparency and doesn't indicate a decrease in message delivery success.

Learn more about upcoming messaging error visibility improvements.

RCS is an enhancement over SMS, delivering messages over Wi-Fi and cellular with higher encryption security and lower latency, to the default SMS messaging app on Android, Messages by Google. RCS only works on compatible devices and a limited set of countries.

In a gradual rollout starting February 16th, 2024, Twilio Verify will automatically upgrade delivery of Verify OTP messages via RCS instead of SMS whenever possible; and if it exhibits the same or better performance. See Verify RCS to learn more.

Effective 5 February, 2024, Twilio will deprecate HTTP voice media endpoint and redirect requests to fetch recordings media files to HTTPS. As a result, CNAME to serve media from custom hostname will no longer be supported.

With Generative Audiences, you can use generative AI to create Engage Audiences.

Using natural language prompts, you can describe your desired audience based on events performed, profile traits, or existing audiences in your workspace.

To learn more, visit Segment’s Generative Audiences documentation.

Effective January 31, 2024, messages sent from toll-free numbers pending verification will be blocked. Only fully verified toll-free phone numbers will be eligible to send messages. 

Blocked messages will return Error 30032 (any message sent from a restricted or pending TFPN) or Error 30007 (if spam/unwanted on a verified TFPN), and are subject to messaging fees.

These verification efforts, along with increased message filtering, help Twilio combat spam and create a trusted messaging ecosystem for you and your customers.

You may use our Twilio Console or API options to submit toll-free phone numbers for verification.

For more information, please check out our guide Toll-Free Message Verification for US/Canada.

The Google Display and Video 360 destination, rebuilt on Destination Actions, is now in public beta.

This destination lets you streamline activation of end-to-end ad campaigns under Google Marketing Platform.

Segment will deprecate the Personas DV360 destination. Moving forward, all users will work with the new Display and Video 360 (Actions) destination.

To learn more about the destination and migration steps, view the Display and Video 360 (Actions) documentation.

The United Kingdom (UK) regulators are enforcing new Know Your Customer (KYC) requirements and guidelines for UK long codes. Twilio will collect KYC information through Regulatory Compliance (RC) bundles either in Console or through our API.

As previously communicated, Twilio's public Voice IP migration has completed as of 8am UTC-8.