Twilio Changelog

We have updated all Flex projects that use Automatic Updates to Flex UI 1.27.

This release of Flex UI includes a public beta for Real-Time Queue Monitoring. This feature displays real-time metrics that are useful for managing queues during the day. We have added new default metrics - number of handled customers, number of abandoned customers, and SLA. The SLA shows the percentage of waiting customers that were connected to an agent within a desired target time. Developers can programmatically add additional metrics to extend this dashboard.

Real-Time Queue Monitoring can be enabled from the Flex Features page.

For more information check our documentation. Check how to enhance and customize queues monitoring programmatically.

For more details on this release, please visit the release notes for Flex UI.

Reminder: You can pin to individual versions of the Flex UI or manage your Automatic Updates within the Flex Admin UI.

It is now possible to do a single participant lookup in the Conversations API. With this feature, you can now easily list all Conversations for a specific participant. The lookup is performed using the participant identifier: identity for a chat participant and address for SMS and WhatsApp participants.

Explore the lookup documentation and give it a try!

Starting 31 August 2021 Twilio will begin to escape & and = in query parameters provided in RecordingStatusCallback values for the creation of Calls and Conference Participants.

Today, a bug in RecordingStatusCallback encoding/decoding results in Twilio dropping everything after & in query parameter strings for the provided URL.

Some customers have identified this bug and implemented a workaround where they escape the & before sending it to Twilio. Other customers have developed a workaround that escapes everything except for =. The bug fix will break both of these workarounds, but will result in proper and expected encoding/decoding of HTTP query parameters.

If your application escapes these characters when constructing a RecordingStatusCallback URL you will want to update its behavior to be resilient to this change by August 31st.

Twilio has now extended the maximum Voice call duration on Programmable Voice calls from 4 hours to 24 hours. We’ve also added the ability to set the maximum duration for individual calls generated via the Programmable Voice API and TwiML, using the timeLimit parameter. You can also use the same API parameter to update the maximum duration on active calls.

You can enable the 24-hour Maximum Call Duration in your Programmable Voice Settings console, and the timeLimit parameter is available for you to use in your applications using the Programmable Voice API and TwiML.

For more details on this feature, see our blog post here.

Twilio continues to streamline registration with US Carriers for Long Code Messaging (A2P 10DLC). All A2P brand registrations are now subject to an additional $40 one-time vetting fee. Twilio will automate the vetting process and cover the vetting fee for primary Brands until October 1, 2021 and Secondary Brands created for ISVs until August 21, 2021.

With automated secondary vetting, you will benefit from:

1. Increased daily messaging limits to T-Mobile. See the article ‘T-Mobile daily message limits for long code messaging with A2P 10DLC’ for details.
2. Increased throughput on your campaigns since secondary vetting will ensure accuracy of information and maximizing the TCR Score. See more details in our support article ‘Message throughput (MPS) and Trust Scores for A2P 10DLC in the U.S.’

There is no special action needed from customers to benefit from secondary vetting after this change, it will automatically be triggered for all brands registering for US A2P compliance.

Government agencies are now able to register for US A2P 10DLC.

Government agencies have access to all Standard Campaign use cases today, and will also be eligible for the use case for Emergency Services, once the ecosystem has launched full support for Special Use Cases. See our support article for more info.

Twilio SendGrid now supports the “Multiple Reply-To” feature. This allows senders to include more than one recipient email address to receive replies and/or bounce messages from the recipient of the email.

This feature is available in the SMTP and V3 email APIs. For more information about this feature, please visit the documentation.

Developers can now retrieve the Service SID and Environment SID more easily within their Function code. These SIDs are automatically included in the context object of the invocation and can be accessed with the keys context.SERVICE_SID or context.ENVIRONMENT_SID. This change does not apply to Functions(Classic). For a small number of customers already using a large number of environment variables within their code this functionality may be disabled, and these variables will return undefined. For more information, visit the documentation for this feature.

To go along with this change, Runtime Handler version 1.1.2 is now available, and logs an error to your console if you access context.SERVICE_SID or context.ENVIRONMENT_SID during local development. This version is backward compatible and is available on the Serverless API and the New UI Editor. This handler version is not compatible with Functions(Classic).

To use the new handler version, go to the Dependencies tab, update @twilio/runtime-handler to 1.1.2, and create a new deployment. This handler version requires the Twilio SDK version 3.50.0 or later.

You can find documentation for Runtime Handler and detailed instructions on how to use the Runtime Handler with the Serverless Toolkit in our docs.

Twilio Event Streams can now be used to develop compliant healthcare applications that contain protected health information (PHI) for organizations that are subject to the Health Insurance Portability and Accountability Act (HIPAA). Twilio will sign Business Associate Addendums (BAA) with covered entities and business associates for HIPAA Eligible Products and Services.

Learn more about how to build on Twilio for HIPAA compliance.

All eligible Twilio customers can now start registration for US A2P 10DLC, in the Twilio console or via API. Registering protects and can improve SMS and MMS traffic deliverability and throughput.

To see who should currently register for A2P 10DLC, please refer to this article. In general, customers who send more than 3,000 SMS to the US using Long Code numbers can immediately begin taking action. To start registration, click here or go to Twilio Trust Hub, and select "Go to A2P Messaging".