Twilio Changelog

The Conference Insights Dashboard provides an account-level view of conference and participant behavior. Conference Insights Dashboard data is generated by analyzing and aggregating Conference Summary and Participant Summary records, and can be used to detect changes in application behavior and surface opportunities for optimization. For more information see our docs.

If you face errors in submission or brand verification when you submit your brand details for A2P registration, you will now see a simplified step in the A2P wizard in TrustHub. The multiple steps to edit your brand earlier have been simplified into a single step in the console. This will help you save time in registering your A2P brand and allow you to focus on the most important fields to review. The new design also provides transparency on the number of retries remaining.

You can read more about brand editing here.

If your concerns are not addressed through the instructions shown in the wizard or if you are an ISV API user, you can refer to the new comprehensive guide for troubleshooting your A2P brand here.

Verify Geographic(Geo) Permissions are now available in the Console to block/unblock desired destinations for SMS and Voice, helping you to prevent unexpected high messaging or voice costs caused by malicious actors creating unwanted verification requests.

Check them out on the Verify Geo permissions page:

https://www.twilio.com/docs/verify/preventing-toll-fraud/verify-geo-permissions

We have launched a new SSO management experience in public beta. This new SSO UI will be available in the admin center for customers who have purchased Administrative or Enterprise editions.

Customers can configure and manage their SSO for Twilio Console by themselves using this UI. Earlier, they were required to create support tickets and exchange the SSO configuration data over emails which would take a few days to configure correctly. Now SSO configuration can be setup and enabled for managed users in a few minutes.

Customers also don’t need to enable SSO for every user manually. With the new Domain based enforcement feature, all existing as well as new users will get SSO enforced automatically. So customers won’t have to track whether SSO is enabled for every new user invited to their Twilio Organization.

Learn more about this feature in Twilio Console SSO documentation.

We are excited to announce the JavaScript SDK release of Adaptive Simulcast, a new feature that improves client performance by dynamically switching off unused simulcast spatial layers.

When using adaptive simulcast, a publisher will only encode video layers up to the highest spatial layer being used by subscribers.

For example, a common presentation layout in video chat will have the active speaker’s video in a large format and the remaining participants as thumbnails. In this situation, adaptive simulcast will encode all spatial layers for the active speaker and only the smallest spatial layer for the thumbnail participants. As speakers change, the respective publishing participants will automatically have their spatial layers turned on / off based on what is being used by subscribers in the room.

Compared to standard simulcast, adaptive simulcast will provide significant CPU and bandwidth improvements for your publishing clients, and we recommend all users switch from standard simulcast to adaptive simulcast.

This feature is currently only available in the JavaScript SDK. Please read our simulcast documentation to learn how to use this new feature.

Usage Insights provides a convenient way to view your Super SIM usage over time as graphs and tables. This lets you monitor upward/downward trends in usage as well as anomalous spikes or dips in your Super SIM activity. You can specify different ways to slice-and-dice your data, You can filter by:

• a customizable date range
• SIM
• Fleet
• Network
• Country

Drill into an hour-by-hour view by clicking on the date hyperlinks in the bar chart.

Access Usage Insights in Console via Monitor > Insights > Super SIM.

The Flex Plugins CLI now automatically deletes the package of a plugin when it is being archived. When a plugin is archived, it deletes the built packages of all the versions of the plugins stored in Twilio Assets and when a particular plugin version is archived, it will only remove the plugin package of that particular version. This feature is automatically available with the archive command of the Flex Plugins CLI. This feature also enables you to cleanup your plugins when you hit the plugin limits on your Flex application.

Upgrade your plugins to the latest version of the Flex Plugins CLI to leverage this feature.

We are excited to announce that Message Scheduling is in public beta!

You can now schedule a message over SMS, MMS and Whatsapp using the Programmable Messaging API. Today, when you make an API request to Twilio’s Programmable Messaging API, a message is sent out instantaneously. With this new feature, you can intentionally delay or schedule the time a message is sent out up to 7 days in the future. This means you no longer have to rely on internal cron jobs or scheduling services.

Check out our documentation and blog post to learn more and try scheduling a message.

When you submit brand details for A2P registration, you will be shown feedback if the information could not be verified by the registration vendor, TCR. Based on this feedback, you can now edit the brand information, as explained here with an example of TrustHub UI in the Twilio console. If you are using the ISV APIs, you also have the capability to edit such a brand using APIs as explained here.

For the majority of brands facing verification failures, Twilio will allow you to update your brand up to three times via self-service, after which you would be redirected to customer support for further help. For a minority of brands facing failures, you will be redirected to customer support right away, since the problem can not be resolved via self-service.

Twilio will bear the costs of updating your brand. You can read more about updating your brand details and brand registration best practices here.

You can now manipulate the To and From numbers within SIP INVITE messages through creating Manipulation Policies in the Console.

The expected format of phone numbers in SIP INVITE requests can sometimes differ between on-premise equipment providers and carriers. For example, some PBXs might send numbers in a format other than E.164, the format that Twilio requires. Using Manipulation Policies, you can edit the contents of To and From numbers within SIP INVITEs to comply with formatting requirements, change the callerId of a call, or meet other needs of your public infrastructure.

To learn more, check out our documentation or try it out in the Console now!