Twilio Changelog

Marketing Campaigns supports sending a test email to up to 10 email addresses at a time. Now, when users send a test email, Marketing Campaigns automatically adds “Test -” to the beginning of the subject line. This ensures test recipients know the email is a test and was not yet actually sent to the targeted list or segment.

Updating some Voice settings including PCI Compliance, Call Recording Encryption, and Logging of TwiML, now require the user to have the Owner or Administrator role. A user with a Developer role can only view these settings. This change helps with your implementation of access controls and compliance processes.

To learn more about the roles available and their respective permissions, please click here.

Twilio Studio now supports programmatically ending an active Execution via the REST API and the Twilio helper libraries. This method is useful in cases where a new REST API-triggered Execution needs to override an existing Execution that is already active for the same Contact. Previously active Executions could only be ended via the Console.

To learn more, visit the API documentation for End an Active Execution.

A common request is to download large volumes of messaging data. Although this is possible using Twilio’s REST APIs, it can be slow. BulkExport allows you to download all of a day’s messages in a single file, rather than iterating on the list.

Now Enterprise Plan customers can request a date range, or enable automatic daily generation of files. Each file holds a day’s worth of messages exported in JSON. This enables customers who want to manage compliance or load into a warehouse to get a single file to feed to their processes. After Public Beta, this will be available to all Twilio accounts.

For more information on how to set this up, look at the BulkExport API Overview. Then you can start by requesting a day in the past, and getting all those messages in a single file.

Twilio’s Programmable Voice Mobile SDK 1.x for iOS and Android will officially shut down on July 31st, 2020. After this date, all iOS and Android Apps that use Voice Mobile SDK 1.x for VoIP calls, will no longer be able to connect to Twilio to make or receive VoIP calls.

For continuity of service, upgrade to the latest SDKs and release your app in the App/Play Store, and have your users update before July 31st, 2020.

See this advisory for more information.

Twilio Speech Recognition with <Gather> TwiML now supports enhanced phone_call model that improves accuracy of speech recognition compared to the existing standard phone_call model. The premium phone_call model was built using thousands of hours of training data and ensures 54 percent less errors when transcribing phone conversations than the basic phone_call model. To get started, simply add enhanced=”true” attribute to <Gather> when using speechModel=”phone_call”. Click here to learn more about pricing for the premium enhanced phone_call model as well as how to use it.

An issue has been identified where Voice Insights was tagging calls as having packet loss due to Twilio-internal removal of DTMF or Comfort Noise packets.

For calls with both in-band and out-of-band DTMF key press data Twilio removes the in-band packets which results in RTP packet sequence number jumps that are interpreted as packet loss by the Voice Insights platform.

Additionally, calls where Twilio received Comfort Noise packets the CN packets are not propagated internally which results in the RTP sequence number jumps being reported packet loss.

In both of these cases the calls have been tagged as having high packet loss, but the packet loss percentage reported by Voice Insights in the call summary was 0%.

We have updated the packet loss call tagging logic to account for these conditions and these calls will no longer be tagged by Voice Insights unless the percentage loss for packets outside of these two conditions is greater than 5%.

Depending on your call flow you may see a significant decrease in the number of calls marked as having been impacted by packet loss going forward.

Following the release of Amazon Polly Neural Text-to-Speech voices for the Voice <Say> verb, Studio now supports the same new voices in the Say/Play and Gather Input widgets.

In Marketing Campaigns, you can now segment contacts from a particular list directly from the Contacts page. This reduces the steps to create list-specific segments.

You can now view WhatsApp template rejection reasons in console. When WhatsApp rejects a submitted template, they provide a reason:

• PROMOTIONAL: WhatsApp has deemed this to contain promotional or marketing content.
• TAG_CONTENT_MISMATCH: The language and/or template category selected don't match the template content.
• INVALID_FORMAT: Placeholders or other elementse formatted incorrectly.

Previously, this information was only available by opening a support ticket. For additional details on template rejection reasons from WhatsApp, please refer to our Guidance on Templates.

Happy building!