Twilio Changelog

TaskRouter now emits events for Workspace, Workflow, and Activity resources upon create, update, and delete operations.

For more detailed information please refer to the Events
Reference documentation.

You can now update your existing Fleets’ data limits. This allows you to easily increase or decrease the data limit for your SIMs. Previously, you had to create a new Fleet and move your SIMs to the new Fleet to give them a new data limit. You can update an existing Fleet’s data limit in Console or via the /Fleets API.

Twilio SendGrid will no longer support SendGrid for New Relic and the related integration features after August 30, 2022.

.Effective August 30, 2022, Twilio SendGrid will remove New Relic integrations and dashboard. On this date, you will no longer be able to access the New Relic dashboard to view your email statistics and visualizations. This data is already available through SendGrid’s Deliverability Insights dashboard, which includes bounce and block classifications.

If you use New Relic integrations to review your email program metrics, please use Deliverability Insights for a streamlined, in-app view of your email delivery performance over time.

If you don’t use New Relic integrations, no action is required; this removal does not affect your ability to send mail.

We're excited to announce that Twilio Frontline's web interface is now available in Public Beta. Your employees can now communicate with your customers wherever they are, whether that's at their desk, or on the go.

Frontline's web client layers seamlessly on to our existing mobile apps (available on iOS and Android), and no additional development effort is required. You can learn more from our blog, or log in now with any existing Frontline account at https://frontline.twilio.com.

Twilio Verify has released Automatic SMS Fraud Detection to help you combat fraud and improve your SMS OTP conversion rate. This feature works automatically at no additional cost.

• Read our blog about how it has already helped some customers reduce their daily spend by as much as 35% and doubled their conversion rate in certain countries.
• Check out our docs for feature details.
• Request a consultation to have it enabled for you.

Twilio customers sending messages via US A2P 10DLC can now log into Twilio Console - Trust Hub - A2P Messaging to check whether they have been incurring penalty fees from sending unregistered message segments.

The Twilio Programmable Voice <Connect> TwiML verb now supports the new TwiML noun <Conversation> as a resource target. This allows for fine-grained customization of Voice and Messaging workflows in Twilio Frontline. Frontline developers can inject custom actions into different stages of an active call. Example use cases include:

• Executing other Voice TwiML instructions before connecting a customer and a Frontline worker (e.g. customers are sent to an IVR before being connected to a Frontline worker)
• Configuring in-call behavior (e.g. to enable recording for all calls)
• Configuring call behavior after a participant leaves the call or when an error occurs (e.g. a customer is prompted to leave a voicemail message in the event no Frontline worker answers their call)

Check out the docs for more information on how to use the new <Connect><Conversation> TwiML functionality in your application.

You can now utilize the ampersand (&) character in Twilio Alphanumeric Sender IDs. This can help you send text messages from a sender that better represents your brand name: for example, Owl&Co. This feature is only available in Alphanumeric Sender ID-eligible countries. Please refer to this guide to learn how to use Alphanumeric Sender IDs with Twilio messaging services.

The Twilio Programmable Voice <Connect> TwiML verb now supports the new TwiML noun <Conversation> as a resource target. This allows for fine-grained customization of Voice and Messaging workflows in omnichannel applications. Twilio Frontline is a prime example of where this new capability is particularly useful - with today’s release, Frontline developers can inject custom actions into different stages of an active call. Example use cases include:

• Executing other Voice TwiML instructions before connecting a customer and a Frontline worker (e.g. customers are sent to an IVR before being connected to a Frontline worker)
• Configuring in-call behavior (e.g. to enable recording for all calls)
• Configuring call behavior after a participant leaves the call or when an error occurs (e.g. a customer is prompted to leave a voicemail message in the event no Frontline worker answers their call)

Check out the docs for more information on how to use the new <Connect><Conversation> TwiML functionality in your application. We can’t wait to see what you build!