Twilio Changelog

Effective May 3rd, 2023, Twilio SendGrid customers will be able to configure multiple endpoints for our Event Webhook feature. This enhanced feature provides customers with greater flexibility and control with the ability to  deliver event data to multiple endpoints, each configured to receive whichever events make sense for your email program. For example, you could have one Event Webhook to monitor engagement data and another for delivery events, or one Webhook sending data to your marketing analytics pipeline and another feeding your application monitoring stack.

With this new feature roll-out we have updated the user interface (UI). All the webhook settings are in one place. In the SendGrid UI, click on Mail Settings in the left navigation, and you will see Event Webhooks below the  Webhook settings heading.. We have consolidated our security features: Signature Verification and OAuth 2.0 in one place, providing you with a streamlined user interface.

Additionally, we have added four new fields in the UI and API:
1. Friendly Name
2. Webhook ID
3. Created Date
4. Updated Date

Note:
* Existing webhooks will not be affected by this change, but customers can add additional endpoints as desired.
* The number of endpoints per user is dependent on the TSG plan you are on. See the SendGrid pricing page for details.

We hope this new feature will enhance our customers' experience with Twilio SendGrid and improve their ability to track and analyze their email engagement and delivery data.

 

As previously communicated, Twilio has changed how withheld caller ID is displayed on outbound <Dial> calls. This change has been made for inbound Programmable Voice calls as well. Any Programmable Voice calls where the caller ID has been withheld will now display anonymous in the From field. 

The Twilio Programmable Voice SDKs now offer the new Call Message Events: User-Defined Messages and User-Defined Message Subscription resources for application developers. This release, available now in Public Beta on the latest major versions of Voice JS and iOS SDKs, supports relaying custom events to and from your backend to a registered Voice SDK Client on any active call - all within the Twilio platform. This closes the loop on our December ‘22 release by extending support for established (“in-progress”) calls to also support for calls in a ringing state. By leveraging the existing signaling connection, you no longer need to set up your own communication channel between your client-side and server-side applications. This unlocks a host of advanced use cases, including:

• Relaying (and taking action on) call progress events
• In-line text transcriptions
• Upgrading 2-party call to multi-party via Voice Conference
• Presenting valuable context in your application at the right time, such as quick text reply buttons in a mobile app

In coming releases we’ll bring this functionality to our Android SDK as well as explore options to provide “out-of-the-box” event subscriptions for common use cases. Check out the docs for more information on how to use the new functionality in your application. We can’t wait to see what you build!

We previously announced that the Notify product would end of life (EOL) on October 23, 2023. We’re now extending the EOL deadline; the new EOL date for Twilio Notify is April 25, 2024. After this date, any requests made to the Notify API will fail.

We hope this extension will provide you with enough time to transition to alternative options. To assist you in this process, we have prepared a migration guide and recommend reaching out to our support team with any questions.

As previously communicated we have updated the status callback behavior for mobile Voice SDK calls. This change more accurately reflects the actual condition of the call; i.e. calls sent to powered off or otherwise unreachable devices will no longer return a ringing call progress event. If your application logic depends on the ringing status callback for its performance, you will need to update your application to handle this condition appropriately.

Effective May 3rd, 2023, Twilio SendGrid customers will be able to configure multiple endpoints for our Event Webhook feature. This enhanced feature provides customers with greater flexibility and control with the ability to  deliver event data to multiple endpoints, each configured to receive whichever events make sense for your email program. For example, you could have one Event Webhook to monitor engagement data and another for delivery events, or one Webhook sending data to your marketing analytics pipeline and another feeding your application monitoring stack.

We have updated the TaskRouter SDK V1 & Taskrouter SDK for Flex with the introduction of retries and the use of truncated exponential backoff in case of network call failures.

Twilio has updated its Text-To-Speech offering adding support for new Amazon Polly Neural Voices. This release includes the following new voices and languages: Ruth-Neural (en-US), Stephen-Neural (en-US), Sergio-Neural (es-ES), Andres-Neural (es-MX), Remi-Neural (fr-FR), Adriano-Neural (it-IT), Kazuha-Neural (ja-JP), Tomoko-Neural (ja-JP), and Thiago-Neural (pt-BR).

Starting 26 June 2023, “Alice” voices will no longer be supported for Text-To-Speech. Any request for “Alice” voices will be redirected to an alternative voice. No action is required from customers and no service disruption is expected.

Going forward, requests for “Alice” voices will be automatically mapped to the existing “Woman” voices when available for the selected language, and requests for non-available languages would be mapped to a paid alternative.

It is recommended to update configuration in Console, Studio flows and application to remove any references to “Alice”. Alternatively, Twilio encourages to review and re-test applications currently using “Alice” with the re-mapped voices to confirm that they work as intended.

For additional information, see this help center article.

Voice Intelligence is now in Public Beta. Create call transcriptions and apply Natural Language Understanding to get valuable data insights from your call recordings. It is available with a new API and in the Twilio Console.

With Voice Intelligence you can:

• Transcribe your calls from Twilio or 3rd party recordings.
• Apply Natural Language Understanding (Language Operators) to your call transcriptions to analyze calls, redact PII or identify keywords and phrases.
• Search and share data insights from your transcriptions in your software with an embeddable view.
• Integrate the Transcription Viewer with Flex using the Voice Intelligence plugin.

 

Learn more about Voice Intelligence in our docs.