Twilio Changelog

TaskRouter now offers dedicated properties in the Workflow filter target to improve support for use cases where the agent is already known, e.g., because the customer previously spoke to that agent (‘last agent routing’) or has an existing relationship with that agent / advisor (‘preferred agent routing’).

Developers can utilize properties for either the agent’s Worker SID or Worker friendly name in a Workflow filter target and specify the respective value on the Task.

Utilizing this feature will yield significant performance improvements over the general evaluation logic and prevent latencies during routing and assignment of such Tasks.

To learn more about the TaskRouter Known Agent Routing feature, please refer to our documentation on Known Agent Routing.

As previously communicated, Twilio is adding functionality to the Programmable Voice <Dial> verb. Although the new features are specific to SIP Connectivity via <Dial><Sip>, the new functionality may affect your existing applications using <Dial>, <Dial><Client>, and <Dial><Number>. <Dial><Conference> and <Dial><Queue> are not impacted.The deadline to account for these changes in your application code is 16 November 2021.

In most cases, your existing code will continue to function; however, there are some functional improvements and behavioral changes which could possibly impact your application. We recommend testing your existing application code in dev or staging environments before 16 November 2021 to identify any potential impacts.

The new features can be enabled on the Programmable Voice Settings page by clicking the Enable Advanced Programmable SIP Features setting. This will activate the new features on an account-wide level.

Twilio initially communicated that these features will be applied to all accounts after 31 July 2021, but following customer feedback we extended the testing period to 16 November 2021.

We are keeping your runtime up to date in accordance with industry standards. Based on the Node.js support schedule, Node.js v12 will no longer be in Maintenance long-term support (LTS) status after April 30, 2022. Production applications should only use releases of Node.js that are Active LTS or Maintenance LTS.

Your currently deployed functions will continue to execute on the existing Node.js v12 runtime if no changes are made.

Follow these instructions to upgrade, test, and deploy your code and ensure a safe transition to Node.js v14.

ISV customers using the APIs to register brands for US A2P 10DLC will see two new values for brand registration status (‘status’ field):

1. IN_REVIEW
2. DELETED

Customers will also see new behavior for this field. You can check the github changelog here for the new enums available November 1. Starting December 1, using GET API to check brand registration Status will return ‘status’ as IN_REVIEW when your brand is under manual third-party review. The manual review can take 7+ days. Status ‘DELETED’ will be returned when a brand is deleted. Since a new status type can be a breaking change for you, please update your code before Dec 1.

Additionally, behavior of the ‘status’ field now represents a more accurate status of the brand as it is APPROVED only when your brand registration is complete and you can move to campaign creation. This eliminates the need for you to check multiple fields to know the action required from you on a brand. You can see the new behavior of status in the A2P wizard within Twilio Console, and in the API. Before December 6th, IN_REVIEW status will be visible on Console but not be returned in API to give adequate time for your API integration to be updated.

New U.S. A2P 10DLC registration flows are now available for 527 Political Organizations and K-12 Education customers. These new registration flows are available in both the A2P wizard in the Console as well as ISV APIs.

• 527 Political Organizations can now complete registration by providing their Campaign Verify token during A2P brand registration. This will qualify the brand for the Political special use case and unlock increased message limits
  • Onboarding Guide for ISVs
  • Onboarding Guide for Direct Brands
• K-12 Education customers can now register their campaigns using the new K-12 Education special use case. The K-12 Education use case offers both increased message limits and reduced carrier fees. Carrier post-approval required.
  • Onboarding Guide for ISVs
  • Onboarding Guide for Direct Brands

For more information on eligibility, messaging limits, pricing, and FAQs for these registration flows, please see our article on Special Use Cases for A2P 10DLC.

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.