Twilio Changelog

Twilio Frontline, a programmable application for salespeople and relationship managers, is now in Public Beta. This launch includes publicly available mobile apps for both iOS and Android, advanced inbound routing, native SSO integration, functionality to transfer and close conversations, and support for production-scale rollouts of a secure customer communication platform over SMS and WhatsApp.

You can read more about this launch on our blog, and if you’re ready to start building, dive in to our docs.

We are excited to announce that the support for using version 16.13.1 of React and ReactDOM on Flex is now generally available.

This allows you to use more of React’s APIs, including React Hooks, when developing your Flex plugins. You can set the React version of your Flex application on the Developer Setup Page. You are no longer required to set the UNBUNDLED_REACT argument for all your Flex Plugins CLI commands.

Review our React documentation for more details and upgrade to the latest version of the Flex Plugins CLI to get started.

Error Log events are published when an error or warning takes place on your Twilio account. These are the same events surfaced through the Twilio Console Debugger. Developers can now have these events delivered to destinations like Amazon Kinesis and webhook through Event Streams. For more information about Error Log events, read the docs here.

Following our earlier announcement, we have applied a Content Security Policy to all Flex applications on flex.twilio.com. This restricts Flex from being rendered in an iframe on unregistered external domains. To continue using Flex within an iframe, including through Salesforce and Zendesk integrations, admins must register their external domains on the Flex Settings page. We have updated our Content Security Policy to prevent potential phishing attacks or abuse by malicious third parties.

Refer to our documentation for more details.

Emergency calls will always be delivered for Twilio phone numbers in the US and Canada using Elastic SIP Trunking.

If your Twilio phone number used to call 911 does not have an emergency dispatchable address, the call will be routed to a national emergency call center where a trained agent will ask for the caller’s name, phone number and location.

To associate an emergency address with your Twilio phone number, check out our docs and API.

Twilio Programmable Voice signs outgoing calls under the SHAKEN/STIR call authentication framework to increase call answer rates. Customers can create a Business Profile and enable SHAKEN/STIR in the Twilio Trust Hub or with the Twilio Trust API and assign their Twilio local and toll-free US phone numbers to receive full attestation on their outbound calls. This can lead to a trust indicator, “Caller Verified”, being displayed on devices on participating destination networks.

For more details, please visit here.

Twilio Elastic SIP Trunking signs outgoing calls under the SHAKEN/STIR call authentication framework to increase call answer rates. Customers can create a Business Profile and enable SHAKEN/STIR in the Twilio Trust Hub or with the Twilio Trust API and assign their Twilio local and toll-free US phone numbers to receive full attestation on their outbound calls. This can lead to a trust indicator, “Caller Verified”, being displayed on devices on participating destination networks.

For more details, please visit here.

Twilio Programmable Voice now allows customers to use CNAM to brand their outgoing calls from United States Twilio Phone Numbers. CNAM stands for Caller ID Name. CNAM is a feature in the United States public telephone network that identifies an incoming caller by an individual or business name associated with the originating phone number. CNAM is registered by the end user assigned to the phone number through their Telephony Service Provider (Twilio).

Customers can take advantage of CNAM by onboarding to the Twilio TrustHub via Console or the API. For more information please visit here.

Twilio Elastic SIP Trunking now allows customers to use CNAM to brand their outgoing calls from United States Twilio Phone Numbers. CNAM stands for Caller ID Name. CNAM is a feature in the United States public telephone network that identifies an incoming caller by an individual or business name associated with the originating phone number. CNAM is registered by the end user assigned to the phone number through their Telephony Service Provider (Twilio).

Customers can take advantage of CNAM by onboarding to the Twilio TrustHub via Console or the API. For more information please visit here.

Conference and Participant Summaries provide multiple views into conference metadata which allow users to see conference parameters, investigate participant event timelines, and understand detected quality issues.

Every conference on Twilio is now being analyzed and aggregated by Conference Insights to provide visibility into participant behavior and offer prescriptive recommendations for resolving common quality and configuration issues.

Conference and Participant Summaries are included with all conferences at no additional cost. For more information see our docs.