Twilio Changelog

Effective July 1st, 2022, all Twilio SendGrid Essentials 40k and 100k packages will change. The Essentials 40k package will become the Essentials 50k package with a new price, and the Essentials 100k package price will be changed.

The new Essentials 50k package will come with 50,000 emails/month for $19.95/month, and $0.00133/email overage. The Essentials 100k package will have a price increase to $34.95/month, and $0.0009/email overage.

We are committed to continued investment in our infrastructure and innovation to provide the best-in-class features you need to build exceptional experiences with email. The features included in the Essentials plan and prices of add-ons are not changing at this time. You can review past invoices and update your Plan and Billing Details in the SendGrid application. If you have any questions please reach out to our knowledgeable support team.

The new Usage by Fleet, by Country, and by Network tabs in Super SIM Insights provide even more ways to aggregate and analyze your Super SIM usage data.

• In Usage by Fleet, quickly identify how much data usage your most active Fleets have incurred over a user-specified time period.
  
• In Usage by Country and by Network, quickly pinpoint which countries and networks your Super SIMs have exchanged the most data with.

All tables also include a 3-dot icon on the rightmost column. This icon opens a dropdown menu that allows you to “drill down” on that particular row. Clicking on an entry in the dropdown takes you to the corresponding tab within Usage Insights and simultaneously applies that row as an additional filter.

Access the new Usage Insights by Fleet, by Country, and by Network tabs in Console via Monitor > Insights > Super SIM.

Starting 5/30/2022, phone numbers can not be assigned to more than a single regulation of a given kind. For example, if a phone number has been assigned to a Shaken/Stir bundle, it cannot be assigned to any additional Shaken/Stir bundles. This change will help to keep our phone number assignment clean and without issue.

We are excited to announce that Flex UI 2.0 is now available in Public Beta.

Since the launch of Functions & Assets in 2017, the two have been a powerful combination. Whether you were using private Assets to store shared logic between Functions or host MP3 files as public Assets for your Functions powered Twilio Voice application. In 2019, we launched a new editor that allowed you to manage your Functions & Assets in one editor interface and using one API, but the two remained separate products in the Console.

Today we are merging the two into one central place in the Console to reduce confusion and make them more easily accessible.

We are excited to announce that Flex Conversations is available in public beta.

Flex Conversations introduces the new async channel platform to easily build SMS/MMS, WhatsApp, and Chat channels in Flex. This release includes:

• Support for Conversations API, the single API to manage all asynchronous channels including SMS/MMS. WhatsApp, and Chat
• New Interactions API to set up and manage inbound and outbound communications
• An open source React based chat application to help you get started with creating and embedding webchat into your website
• Attachment support for all channels that support attachments
• Conversations support in Twilio Studio

Flex Conversations requires Flex UI 2.0. See the Flex UI 2.0 docs for more info and how to perform a migration.

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

Call recordings are now stored by Twilio in dual-channel by default for no additional cost, enabling you to process the individual participants of the call recorded. With this change, the recording audio files of a 2-party call will have two channels and contain the audio from each call leg in a separate channel.

Prior to this release, customers needed to specify dual-channel to record each participant in a separate channel, and all audio mixed in a single channel was the default behavior. With this release, a new RequestedChannels query parameter can be used to specify whether the file should be downmixed to a single channel or downloaded as a dual-channel file. For backward compatibility, when RequestedChannels query parameter is not specified, the default download will be either mono or dual, depending on what was requested for the recording.

It’s possible to continue enabling single-party call recordings using the recordingTrack parameter to select whether the inbound or outbound audio tracks of the call should be recorded, and the recording file will always be mono and no additional tracks recorded. Voice recordings where dual-channel is not supported, such as TwiML <conference> noun and <record> verb, all audio will be mixed in a single channel file.

With this release, storing dual-channel recordings comes at no extra cost compared to single-channel storage.

Dual-channel call recordings by default is now available on all new accounts and will be gradually deployed on existing accounts.

Learn more about how it can help unlock intelligence from your recordings by increasing transcription accuracy. on the Twilio blog.

Sending WhatsApp messages with media now supports additional content types in a public beta, including Microsoft Word, Excel, PowerPoint, and certain audio files. See this document more information on all the different media types we support.

In this release of Flex UI, we have introduced a Degraded mode for Flex UI - now Flex UI will initialize with limited capabilities, even if some of the components like SDK’s (TaskRouter, Conversations, Voice or Sync) are down. In case of disruptions in Twilio services, Flex User will be able to login to Flex and perform certain tasks that are still available. For example, in the case of Twilio Voice experiencing an incident, your agent will still be able to handle messaging tasks.

Users will see a notification informing them of a possible disruption in the normal operation of Flex UI and they will be able to download a thorough report with error details and logs.

For more on error handling and reporting, check out our Troubleshooting Flex UI guide.

Bounce Classifications are now included in the Twilio SendGrid Event Webhook. The event webhook is a powerful way for you to consume event level data to gather more insight to your email performance. Twilio SendGrid's Event Webhook will allow you to use a data aggregator of your choice and notify a URL via HTTP POST with information about events that occur as Twilio SendGrid processes your email. The addition of Bounce Classifications to the Bounce and Deferral event payloads will provide additional insight as to why an email was bounced, blocked, or deferred.