Product changelog and announcements

Twilio Alarms, a near real-time monitoring and alerting experience for Twilio customers, is now Generally Available (GA).

The first full scale implementation of Alarms supports Error Logs. This enables you to proactively monitor error logs at the minute level and receive a notification whenever there is a spike in errors, warnings, or informational events of interest, across your Twilio applications.

You can learn how to create and use Alarms with this Twilio guide or watch this demo.

We are sunsetting our old Alert Triggers product. If you have created Alerts on our old platform, they have already been migrated onto this new Alarms platform. You will be able to access these in the Manage Alarms page.

Twilio SendGrid has always grouped your email statistics by mailbox provider in our console. This allows you to easily see how your email is performing at Yahoo compared to Microsoft, for example. Our system also helps clean up this data by grouping mailbox providers together. On November 16, 2022, Twilio SendGrid will release an update to our current Mailbox Provider groupings that will make this part of our application even more powerful. Specifically, we will be adding more mailbox providers to our list, increasing from 50 to almost 250. This will result in far less data being lumped into the “Other” bucket when you review your mailbox provider statistics. Check out our blog post to learn more about the change and see examples for more information.

In 2H 2023 Twilio will be updating the media IPs and port ranges for SIP and Voice SDK calls in all regions. We will be moving from a per-region IP range allocation to a single global range; 168.86.128.0/18. Additionally, we will be expanding the media port range from 10000-20000, to 10000-60000.

We are making this change to provide flexibility, reliability, and scalability. There is no action required at this time, and we will provide a more precise timeline approximately six months before the change. At that time you will need to update your network infrastructure to ensure that you have whitelisted the full IP and port ranges. Failure to do so will result in one-way audio and dropped calls.

We are launching a new attribute `requireMatchingInputs` within <Prompt> verb which is used in conjunction with the `for` attribute to prompt the caller to enter a specific payment detail twice. The first <Prompt> verb prompts the user to enter a given payment information.

The second <Prompt> which contains `requireMatchingInputs` set to `true` will give the caller a different prompt asking the caller to enter the information again. Once the customer enters the information, both inputs are validated against each other and if they match, they will be sent to the downstream payment gateway for processing.

This attribute works for ACH-debit <pay> transactions of type purchase/tokenization that require users to enter a bank account number or routing number. This enhancement was introduced to catch any user input errors upfront, reducing the error rates reported by payment gateways to meet the error thresholds defined by NACHA.

For more information about this feature, check out the API Docs.

Super SIM Usage Insights now lets you export a CSV file containing your SIMs’ usage record data. With just the click on a button, you can download an extract of the table currently being displayed in the browser. Having this data in the form of a CSV allows you the flexibility to perform subsequent analysis using any application of your choice – a database, spreadsheet, or data visualization tool.

All of the Usage Insights tabs support the CSV Download feature:

• Usage by Time
• Usage by SIM
• Usage by Fleet
• Usage by Country
• Usage by Network

Access CSV Download for Super SIM Usage Insights in Console by navigating to Monitor > Insights > Super SIM and clicking on the button labeled “Export CSV”.

Segment for Healthcare is now HIPAA-eligible. 

Twilio's BAA now covers Segment for all Business tier customers. Customers can now use personal health information (PHI) and personally identifiable information (PII) in Segment to deliver personalized care journeys for patients at scale. You can refer to our Architecting for HIPAA documentation and healthcare specific Recipes for how to build on Segment for Healthcare compliantly.

For more information, see HIPAA Eligible Segment.

We are excited to announce that the Conversations API is now generally available in Ireland (chat only). The availability of Conversations API in Ireland gives you control over where you data is processed and stored. It also offers data processing that is closer to your applications, therefore reducing latency and improving performance.

Click here to learn more on how to get started with Conversations API in Ireland.

The Intercom Web and Cloud Mode (Actions) destinations allow customers to create leads, contacts, and companies in Intercom. Contacts and companies can be updated with their latest attributes and events. With this data, customers can personally communicate with their users with targeted content, behavior-driven messages, and conversational support. Learn more in the documentation:

• Intercom Web (Actions)

• Intercom Cloud Mode (Actions)

The Pardot (Actions) destination is now in Public Beta. With this destination, customers can create and update prospects in Pardot. Data is sent server-side and can be used to automate marketing campaigns. 

For more information, see the Salesforce Pardot (Actions) documentation.

The new HubSpot Web and Cloud Mode destinations, built on Destination Actions, are now in Public Beta. With these destinations, customers can benefit from a number of improvements, including OAuth support, clearer mapping of data for an easier setup, and support for custom behavioral events. Learn more in the documentation:

• HubSpot Web (Actions)

• HubSpot Cloud Mode (Actions)