Twilio Changelog

A new section in Console billing pages provide partners with up to the minute usage charges broken down on a per customer basis. These pages also show partners their usage costs as well as the cost for end customers. This capability is only available for partners with Reseller Tools enabled.

The new version of Marketing Campaigns now supports sending a Single Send to a segment based on contact custom field data for more personalized sending.

Starting July 1st, 2019, we have begun collecting Value-Added Tax (VAT) on the services sold to our customers in 32 countries in Europe. Nonresident entities, such as Twilio Inc. are now required by European taxing authorities to collect Value-Added Tax (VAT) on its sales of its services to customers located in the listed countries.

Twilio is only required to impose VAT on Business to Customer (B2C) transactions. Business to Business (B2B) customers are tax exempt, and will be treated as such when a valid VAT number is entered via the Billing Preferences page on console.

VAT for the previous month is assessed on the first day of the following month. For example, you will be charged VAT for your July usage in August. You can see the VAT amount charged in your invoice.

We have launched a new design for Twilio invoices starting June 2019. The new design is based on customer feedback and uses modern design principles and engineering solutions to provide an easy to understand invoice.

The design simplifies the ordering of information to provide the most important information upfront and connecting the dots for confusing concepts. Power users can continue to use the CSV supplement to invoices or the details section in the PDF.

Don't yet see this design on your invoice? We are rolling out the design in phases to customers and are iteratively launching sections of the new design between June and Dec 2019.

Curious to understand your new invoice? Check this article.

A new Voice SDK event has been added to Voice Insights. The selected-ice-candidate-pair event contains information about the local and remote ICE candidates including the transport protocol and type. This information allows you to identify connections which need to use TURN for media relay or TCP transport which can indicate a highly restricted local network environment. For more information see our docs.