Twilio Changelog

SendGrid Marketing Campaigns now supports more unique identifiers per contact!

Our latest update to our SendGrid Marketing Campaigns product now allows for up to four unique identifiers per contact: Email, Phone Number ID, External ID, and Anonymous ID. This highly-requested update means an email address is no longer mandatory to store a contact in SendGrid.

Additionally, this new feature gives you greater flexibility in contact management and expanded opportunities for engaging marketing strategies across various channels, all while setting the stage for upcoming SMS capabilities and integration across Twilio and non-Twilio products.

For more information, check out how to Create and Manage Contacts in SendGrid.

We have begun enabling accounts for error log tracking of message creation API errors. Full details are available here. When your account is enabled, the banners on the messaging error log console page will update to reflect that your account is enabled. Note that accounts will be enabled on a per-account-sid basis over the coming weeks; thus certain sub-accounts may gain access before others.

We are excited to announce an enhancement in the Toll-Free Verification process. In our ongoing efforts to streamline and improve the user experience, we now support multiple rejection reasons, new rejection error codes have been added and existing rejection error code descriptions have been improved. These changes are supported in the Toll-Free Verification API, Console, Event Streams - webhooks and email notifications-about a rejected toll-free verification.

With this release, it’s important to note that the Toll-Free Verification API’s LIST, GET and webhook still supports a single rejection reason, but we strongly advise transitioning to the new “rejection_reasons” attribute, so that you pick up all the rejection reasons. 

Previous releases have included this metadata, which you may also find useful when processing a rejection: 

  "rejected_on": "2024-04-05T22:01:58.076Z",

  "edit_expiration": "2024-04-05T22:01:58.076Z",

  "edit_allowed": true,

Additionally, the Twilio-Rejected event webhook now includes the phone number DID: 

  "phonenumber": "+18002225555",

For a detailed list of all toll-free verification error codes please visit Twilio Error and Warning Dictionary.  

We are excited to announce that Flex UI 2.7.0 is now available. This release features the following additions and updates:

• We’ve added the following features to Agent Copilot (Public Beta) and Unified Profiles (Public Beta):

  • Agents have access to a new feature, customer highlights. The one-paragraph summary combines customer data and recent activity, so agents can start the conversation faster and have a more informed interaction. 

  • Agents have access to more  information in a customer’s profile details and history:

    • Wrap-up notes now appear in a customer’s history, so agents can see notes from previous interactions. 

    • Agents can now see recent customer web and app activity.

    • Outbound calls now appear alongside inbound calls.

    • Past interactions in the customer’s history include the queue of the agent who handled that task, in addition to  the agent’s name.

  • Administrators have more configuration options: 

    • Show or hide wrap-up notes

    • Configure how the customer header and search, customer details, and customer history appear to agents.  

• Email in Flex now includes the ability to pause and resume a task. When enabled, the pause action enables agents to put an email task on hold while keeping it in  their queue.

• If your agents use Azure Virtual Desktop to log in to Flex, you can now optimize your audio calls with Flex on Azure Virtual Desktop (Public Beta). 

• If your Flex instance uses legacy SSO configuration, you can now migrate to enhanced SSO configuration, a solution with enhanced security that uses OAuth 2.0 for login authorization.

• Two new metrics are available in the Real-Time Queues View, Completed (30 min) and Completed (Today), which show the number of tasks completed in the last 30 minutes or today. These metrics do not appear by default. If you want to show them, add them to your view.

You'll also notice a number of feature and UI enhancements, bug fixes, and more.

For complete details, see the Flex UI release notes for 2.7.0.

Effective April 15, 2024, new certificates have been deployed for all our REST API endpoints (e.g., api.twilio.com), including all regional edge locations. Only the end-user certificate has been renewed, as well as the certificate serial number. The root and intermediate certificates have remained the same. Such updates are common practice and do not impact customers that are using Twilio's services unless you are pinning certificates or are managing them manually.

We highly discourage customers from pinning certificates as it exposes them to potential security risks and can cause downtimes for their services. Twilio customers using pinned certificates have a high probability of failed API Requests. 

As of 1st April, 2024,  SMS Pumping Protection for Twilio Programmable Messaging is generally available to prevent fraudulent SMS traffic and lower its significant costs. This feature automatically detects messaging traffic driven by SMS pumping and blocks it from being sent.

SMS Pumping Protection requires no configuration. Enable it in the Twilio Console and Twilio will do the rest. 

The performance of the feature can be monitored via existing Messaging Insights & the newly launched SMS Pumping Insights.

To further customize your SMS pumping protection experience, we have also launched RiskCheck and the Global Safelist.