Twilio Changelog

Twilio is releasing Deletable Regulatory Objects to make regulatory information management easier. This new functionality allows customers to delete unwanted Regulatory Bundles, Supporting Documents, and End-Users from the Twilio web Console and the Public API.

Workforce Management systems can now distinguish between inbound and outbound traffic when gathering agent adherence data. The Flex Real-Time Adherence feed automatically provides a direction attribute for voice interactions. Flex developers can also add a custom direction attribute to tasks for non-voice interactions

Deleting a Message log will now automatically remove any Media objects associated with that message whenever applicable. For media objects that are associated to multiple messages, Twilio will continue to store a copy until all messages refering to the media object are deleted. This allows a more intuitive experience when customers issue delete requests on messages containing media. The change will apply to all messaging channels supporting media including MMS, WhatsApp and Facebook Messenger.

More details of the changes to message records and media availability and deletion are published here.

Customers will be able to view message logs in Console--and retrieve the resources via GET to the /Messages endpoint--for thirteen months after the message is created. This represents a significant change as these logs were permanently stored by Twilio and retrievable via Console and API indefinitely before this change.

If you view logs in Console there is no follow up action, but just be aware that messages will now only display logs for 13 months.

All past message records older than thirteen months will still be backed up within Twilio and available to be retrieved using the Bulk Export utility (except for media older than 13 months).

This change will be reflected as a Data Access Policy Setting of "400 days" in the Messaging Console Settings page. If you perform log extraction via API on a rolling basis, it is important to verify that you are pulling the logs at a frequency that will remain unaffected by this change.

In case there is an urgent need to access older data via the API, customers may contact support for case-by-case extensions till Oct 31, 2020.

The Events and Metrics endpoints for the Voice Insights API are now GA and available for all Voice Insights Advanced Features customers.

These endpoints provide access to Voice SDK/call progress events and call quality metrics in near real time. Developers who consume these resources can discover emerging changes in call behavior reducing time to detection and improving time to resolution.

As part of this release, we have remapped the error codes from 15000 range to 17000 and made changes to pagination to support the encoded PageToken. We have also added an interval section of Metrics API response for Twilio Media Gateway edges.

For more information, see the docs.

Admins in Flex can now manage their plugins, view the history of plugin releases, and rollback to prior deployments. This provides visibility and control of your application's version outside of a developer's command line interface.

SMS Commands sent to Super SIMs will now be stored in the Mobile Core for up to 24 hours and retried until a positive delivery confirmation is received.

Twilio's support for the WhatsApp Business API is now Generailly Available! In addition to meeting Twilio’s SLA standards for GA products, this change represents an improvement in the product experience, support and resilience, as well as a commitment to offer WhatsApp as a first-class citizen across Twilio products.

To try WhatsApp, head over to Twilio Sandbox for WhatsApp. To get your own number, follow the onboarding instructions to connect your WhatsApp number. Once you are live, you can send and receive WhatsApp messages using the Programmable Messaging API or the Conversations API.

In TaskRouter, you can now evaluate a Worker’s Activity state by referencing worker.activity_sid and worker.activity_name in a Workflow’s target expressions. This allows you to target or exclude agents based on the Activity that they are in.

For example, with Activity-based routing you can:

• Route high-value Tasks to agents even when they are scheduled to not receive general Tasks.
  
• Transfer Tasks to agents who are in Activities that are excluded from routing.
• Designate an Activity that allows an agent to only accept a particular type of task.

To learn more about the new feature, please refer to our documentation on Activity-based routing.

Twilio and Elastic SIP Trunking sign outgoing calls under the SHAKEN/STIR call authentication framework to increase call answer rates. Direct customers can create a Business Profile and enable SHAKEN/STIR in the Twilio Trust Hub and assign their Twilio local and toll-free US phone numbers to receive full attestation so that a trust indicator, “Caller Verified”, can be displayed on devices on participating destination networks.

For more details, please visit here