Twilio Changelog

You can now delete WhatsApp message templates in the Twilio Console. To delete a message template, click on the template name on the WhatsApp Message Templates page and then click “Delete” at the bottom on the page. Per WhatsApp guidelines, you may not reuse the name of a deleted template for 30 days after deletion.

On October 26th 2021, the following Amazon Polly Neural voices will be set to Conversational speaking style by default. Amazon made Conversational speaking style default on June 28, 2021 for all new neural voices available at Twilio, deprecating the neutral speaking style. This change brings Conversational speaking style to the remaining set of Polly Neural voices used by Twilio.

Voices: Polly.Matthew-Neural (en-US), Polly.Joanna-Neural (en-US), Polly.Amy-Neural (en-GB) and Polly.Lupe-Neural (es-US).

Note there is no impact to any functionality or interface. As the neutral speaking style has been deprecated by Amazon, this change is permanent (no revert back option available). Compared to the legacy neutral style, the Conversational speaking style feature generally makes neural voices sound more friendly and expressive.

For more information about Twilio Text-to-Speech with Amazon Polly visit our docs.

Customers registering for U.S. A2P 10DLC should use the new name “Proxy” instead of the old name “Conversational” when registering for campaigns of this type. This change is applicable in the A2P wizard in the console as well as ISV APIs (Create Campaign Use Case step). ISV API customers need to update their API integration.

This name change is to better represent the campaign type, which is meant for proxy/pooled numbers supporting personalized services and non-exposure of personal numbers. Some customers had incorrectly registered campaigns as Proxy/Conversational which should’ve been registered as Customer Care.

You can read more about the Proxy campaign use case here.

We’re thrilled to announce that Video Insights is now available in Public Beta.

Video Insights brings self-service tooling to the Twilio console to help you observe application usage and quality, discover trends across all your rooms and participants, and troubleshoot issues with ease, leading to higher quality video experiences for your customers, reduced churn, and increased confidence in scaling rapidly.

Get started now by visiting the Video Insights Dashboard in the Twilio Console, or check out our blog post or the documentation to learn more.

Twilio Live is now Generally Available

With Twilio Live, developers have access to a low-latency, secure interactive live streaming platform that allows speakers to reach millions while providing an intuitive end-to-end developer experience, including flexible server-side API primitives, and player SDKs for iOS, Android, and JavaScript.

Twilio Live gives developers the tools to build immersive live experiences that can be directly embedded into their applications such as marketing conferences, next-generation social podcasts, shopping experiences, concerts, fitness classes, education sessions, and more.

For additional information on this release, check out our blog post and get started with our developer documentation.

Twilio allows customers to set caller ID as transferor or transferee for call forwarding use cases.

With this release you are now able to configure caller ID for call forwarding use cases in the console and API.

For details, check our documentation.

Customers can now view the reasons for their brand registration failures in the A2P wizard in the console or via the ISV APIs for US A2P 10DLC. In the A2P Wizard in the Twilio console, brand failures will result in an error screen with reasons for the failure and instructions to fix your brand registration before you can move forward. The GET Brand API call returns the failure reasons for ISVs registering their customers via API. You can review the failure reasons and API details here and reduce the likelihood of your brand registration failing by following the brand registration best practices here.

SendGrid has updated the system responsible for processing and logging spam report events. This change improves our system’s ability to process and count spam reports that come to us from mailbox providers when recipients mark a message as spam.

This change will result in elevated spam report metrics for some Twilio SendGrid users that will level off once our system catches up to all emails that have been marked as spam. The increase in spam reports is not the result of more recipients marking more mail as spam, rather it is the result of our system capturing spam report events more completely from this date onward.

Note that while this is a GA release, the updates are slowing being rolled out across all accounts.

Twilio SendGrid has launched the Apple Open Indicator in the Event Webhook. Open events now includes a new boolean field, sg_machine_open, to identify anonymous open events generated by Apple Mail Privacy Protection.

Super SIM now has one more location of our Distributed IoT Mobile Core in Singapore, to provide an Internet breakout for IoT customers in the APAC region. With this new location, Twilio has three Internet breakouts for Super SIM traffic: in Ashburn, Frankfurt, and Singapore, with more locations to follow.

Using distributed breakout to the Internet is important to achieve low latency, which opens up new use cases such as adding real time voice/video communications to an IoT device. In addition, it means less data crossing borders, and thus helps with data sovereignty.

To make use of the breakout location in Singapore, Super SIM customers must configure “sg1.super” as the APN on the devices (see Super SIM APN configuration). The existing default APN “super”, when used, results in traffic breaking out to the Internet via our mobile core in Ashburn, USA. When “de1.super” is used, the traffic breaks out to the Internet through our mobile core in Frankfurt.

If you are interested in using the Singapore Internet breakout location, please reach out to Twilio support.