Twilio Products
All Twilio Release Notes (74)
- Apr 21, 2026
- Date parsed from source:Apr 21, 2026
- First seen by Releasebot:Apr 21, 2026
Intelligent Alerts for Twilio Messaging is now Generally Available
Twilio Messaging now offers Intelligent Alerts GA for SMS, using anomaly detection to spot unusual error spikes faster.
Intelligent Alerts is now GA for all Twilio Messaging customers sending SMS traffic.
It uses anomaly detection to automatically monitor your messaging traffic for unusual spikes in selected error codes, helping you identify potential delivery issues faster.
Original source - Apr 9, 2026
- Date parsed from source:Apr 9, 2026
- First seen by Releasebot:Apr 10, 2026
TCPA Known Litigators Check is now available in Compliance Toolkit
Twilio Messaging adds TCPA Known Litigators Check in Compliance Toolkit to help block messages to numbers linked to known litigators while still allowing essential traffic like transactional alerts, OTP, and customer support messages.
The TCPA Known Litigators Check is now available within Compliance Toolkit to help safeguard your messaging by identifying and blocking messages to phone numbers believed to be associated with individuals or entities with a history of filing TCPA-related legal actions.
This safeguard intelligently filters non-essential communications, such as marketing/promotional messages to phone numbers associated with known litigators, while allowing essential traffic, like transactional alerts, otp, and customer support messages, to reach the recipient.
When a message is blocked by this feature, Twilio will return Error Code 30640.
Learn more about this feature and how to enable it in our documentation.
Original source All of your release notes in one feed
Join Releasebot and get updates from Twilio and hundreds of other software products.
- Apr 9, 2026
- Date parsed from source:Apr 9, 2026
- First seen by Releasebot:Apr 10, 2026
Consent Management API is in Public Beta
Twilio Messaging adds the Consent Management API in Public Beta, giving teams a centralized way to sync, store, update, and enforce end-user consent across RCS, SMS, and MMS channels.
Consent Management API is now available globally in Public Beta, allowing you to programmatically sync, store, update, and manage end-user consent preferences across RCS, SMS, and MMS channels. This API acts as a centralized source of truth for managing consent preferences, enabling you to seamlessly integrate consent data from external systems like CRMs or web forms directly into Twilio.
Note that consent states updated via this API for a given Messaging Service are automatically enforced across all three unified channels (RCS/SMS/MMS) to ensure compliance, without requiring any code changes.
Learn more about this feature and how to enable it in our documentation.
Original source - Apr 9, 2026
- Date parsed from source:Apr 9, 2026
- First seen by Releasebot:Apr 10, 2026
Specify your SMS fallback sender when sending RCS messages
Twilio Messaging adds a new FallbackFrom parameter for /Messages API requests, letting you choose the SMS or MMS sender used when an RCS message fails to deliver. It gives you more control over fallback numbers instead of relying on Twilio’s automatic selection.
You can now specify the SMS or MMS sender Twilio uses when an RCS message fails to deliver using the new "FallbackFrom" parameter in your /Messages API request. The FallbackFrom sender must be in the same account SID, but does not need to be in your Messaging Service's sender pool.
This can be useful if you need fallback messages to come from a specific number, instead of relying on Twilio's automatic selection. You can also use this to send from one RCS sender representing your brand, with different fallback numbers per department, store, or representative.
For more information, please see our docs.
Original source - Apr 9, 2026
- Date parsed from source:Apr 9, 2026
- First seen by Releasebot:Apr 10, 2026
Country Code Geomatch now supports RCS (Beta)
Twilio Messaging adds Country Code Geomatch for Messaging Services in public beta, now supporting RCS sender matching by recipient country. It lets teams use multiple approved RCS senders in one service and removes the need for separate services and custom routing logic.
The Country Code Geomatch feature within Messaging Services now supports RCS in a public beta. If you have distinct RCS senders approved per country, you can add each of them to the sender pool of a single Messaging Service. When you send from that Messaging Service, Twilio will select the RCS sender that matches the country of your recipient’s phone number.
Previously, each Messaging Service supported only one RCS sender, which meant customers sending to recipients in multiple countries had to maintain separate Messaging Services and build their own routing logic. RCS Geomatch removes that requirement.
For more information, see the Messaging Services’ docs.
Original source - Apr 9, 2026
- Date parsed from source:Apr 9, 2026
- First seen by Releasebot:Apr 10, 2026
AT&T phone numbers can now be added as RCS test devices
Twilio Messaging now supports adding AT&T test numbers to RCS senders for prototyping and testing across major US carriers.
Twilio Programmable Messaging now supports adding AT&T test numbers to your RCS sender.
You can now prototype and test your RCS sender on all major US carriers.
Once you’re ready to use RCS for production traffic, submit your RCS compliance information and our operations team will guide you through the carrier approval process
Go to Console to get started now.
For more information, see our docs.
Original source - Apr 6, 2026
- Date parsed from source:Apr 6, 2026
- First seen by Releasebot:Apr 7, 2026
OAuth for Twilio APIs is now in GA
Twilio Messaging now supports OAuth 2.0 for more secure API access with short-lived, scoped tokens.
Twilio Communications APIs now support OAuth 2.0. Upgrading to OAuth 2.0 makes your applications more secure than using traditional API keys or Auth tokens. Here is why:
- Short-lived tokens: OAuth 2.0 generates short-lived access tokens instead of static, long-lasting credentials.
- Scoped access: Each token only works with the specific APIs it was issued for, so a compromised token doesn't expose everything.
- Apr 6, 2026
- Date parsed from source:Apr 6, 2026
- First seen by Releasebot:Apr 7, 2026
A2P 10DLC campaign registration will require privacy policy and terms & conditions URLs starting June 30, 2026
Twilio Messaging adds required PrivacyPolicyUrl and TermsAndConditionsUrl for new A2P 10DLC campaign registration.
Starting June 30, 2026, PrivacyPolicyUrl and TermsAndConditionsUrl will be required fields when registering a new A2P 10DLC campaign via the Twilio Messaging REST API. Campaign creation requests that don’t include both fields will be rejected during campaign review.
Original source - Apr 5, 2026
- Date parsed from source:Apr 5, 2026
- First seen by Releasebot:Apr 7, 2026
Branded Calling Insights: Canada, United Kingdom, & Germany
Twilio Messaging now supports Branded Calling Insights for Canada, the UK, and Germany in US1.
Branded Calling Insights for Canada, the United Kingdom, and Germany are now live in the US1 region.
Original source - Apr 1, 2026
- Date parsed from source:Apr 1, 2026
- First seen by Releasebot:Apr 7, 2026
Verify Events: Message Status Event Stream V2 released with new Tags parameter
Twilio Messaging adds V2 Verify Message Status events with tags for passing custom metadata into streams.
V2 of Verify Message Status events is now available. This version adds a "tags" parameter to the event stream. By including key-value pairs in your Start New Verification request, you can now pass custom metadata through to your stream for better tracking. Check out the Message Status Stream guide to get started.
Original source - Apr 1, 2026
- Date parsed from source:Apr 1, 2026
- First seen by Releasebot:Apr 7, 2026
Verify Events: Verification Stream (all versions) will no longer provide updated message delivery status or error code information
Twilio Messaging updates Verification Event stream, sets send_code_attempt delivery_status to SENT, and moves updates to Message Status Event Stream.
New customers subscribing to the Verification Event stream will no longer provide updates on the delivery_status for each send_code_attempt and its value will be set to a static status of SENT. The error_code attribute will also be removed from each attempt. To obtain updates on message delivery status, new subscribers should now use the new Message Status Event Stream.
Original source - Apr 1, 2026
- Date parsed from source:Apr 1, 2026
- First seen by Releasebot:Apr 7, 2026
Verify Events: Verification Event Stream V3 released with new Tags parameter
Twilio Messaging adds Verification stream version 3 with tags in each attempt.
Verify Event's Verification stream has a new version 3 that includes a new "tags" parameter in each attempt. This set of custom tags will appear in the event stream when you include a key value pair in the tags parameter of the Start New Verification request. To learn more, please visit our Verification Status Stream guide.
Original source - Mar 31, 2026
- Date parsed from source:Mar 31, 2026
- First seen by Releasebot:Apr 7, 2026
Twilio integration with Salesforce Service Cloud Voice is live on AppExchange
Twilio Messaging expands its Salesforce Service Cloud Voice integration with GA availability on AppExchange, adding external call transfers, supervisor barge and listen, and a toggle for real-time transcription.
We’re excited to announce that Twilio’s integration with Salesforce Service Cloud Voice is GA and listed on the AppExchange.
This release comes with the following enhancements:
- External Call Transfers: Agents can now transfer calls to external phone numbers.
- Supervisor Barge & Listen: Supervisors can now monitor live calls and “barge in” to assist agents during critical customer interactions.
- Toggle Real-Time Transcription: Administrators can enable or disable real-time transcription based on specific privacy requirements or workflow preferences.
To learn more about setup, please see the setup guide.
Original source - Mar 31, 2026
- Date parsed from source:Mar 31, 2026
- First seen by Releasebot:Apr 7, 2026
Voice Insights: Trust & Engagement Insights and Reports API (GA)
Twilio Messaging adds Voice Insights Trust & Engagement Insights and a companion Reports API, now generally available for outbound calling health, spam-labelling detection, best-time-to-call heatmaps, engagement funnel reporting, and programmatic ROI metrics.
Voice Insights Trust & Engagement Insights and its companion Reports API are now Generally Available. This combined release provides a comprehensive solution for managing outbound calling health and campaign ROI.
Trust & Engagement Insights offers a specialized Twilio Console dashboard to detect behaviors triggering spam labeling, identify blocked calls, and optimize dialing windows with a best-time-to-call heatmap. Users can quantify campaign effectiveness through a visual engagement funnel and measure the ROI of trust investments like Branded Calls.
The Reports API serves as a zero-infrastructure companion, allowing you to programmatically retrieve these same aggregated metrics—per account or per phone number—with a single call. By outsourcing data processing to Twilio, you can accelerate decision-making and reduce operational costs by up to 90%.
Key Benefits
- Holistic Health: Monitor Trust & Engagement scores to proactively mitigate spam labeling and blocks.
- Performance Optimization: Use heatmaps and human-answer rates to refine dialing strategies.
- Programmatic Access: Use the Reports API to build custom dashboards or integrate metrics into your own internal tools.
- ROI Attribution: Compare branded vs. unbranded call performance to justify trust product investments.
These features are available exclusively as part of Voice Insights Advanced Features.
Learn more in our Trust & Engagement Insights and the Reports API documentation.
Original source - Mar 29, 2026
- Date parsed from source:Mar 29, 2026
- First seen by Releasebot:Apr 7, 2026
Twilio SCIM API
Twilio Messaging releases SCIM API as generally available, giving teams a way to automate user provisioning and deprovisioning from an IdP and keep Twilio access in sync as organizations grow and change.
Twilio SCIM API is now Generally Available (GA)
Twilio SCIM API is now Generally Available (GA). You can now automate user provisioning and deprovisioning directly from your Identity Provider (IdP), keeping Twilio access in sync as your team grows and changes.
Connect your IdP to Twilio using the SCIM 2.0 standard by creating an OAuth application in the Twilio Admin Center. Use the access token to manage users via the SCIM API endpoints—create new Twilio users, update user details, and deactivate access automatically.
- Create a new OAuth application using the authorization code grant type with the required SCIM scopes.
- Use the access token to manage users via the SCIM API endpoints—create Twilio users, update user details, and deactivate access automatically.
- Okta is supported out of the box; Azure AD and Google Workspace require custom setup.
To learn more about the SCIM API, please check our docs.
Original source