Twilio Changelog

Twilio has enhanced the Console UI to improve end-user usability by adding visibility of phone numbers associated with A2P registrations directly on the Campaign details page. This update introduces a new table that lists all phone numbers linked to a specific Campaign, making it easier to manage and review your numbers.

As an example, you can navigate to this page from Console UI -> Messaging -> Regulatory Compliance -> Campaigns -> Click on the campaign.

Visit our Twilio Docs for more information on A2P 10DLC. For details on confirming A2P registration, see our Support article.

We are committed to enhancing your integration experience and ensuring our customers can successfully send messages. However, we understand that sometimes errors occur, and we aim to provide you with the quickest guidance to resolve them. That is why we are updating the error code dictionary to improve clarity and usability. 

We're excited to announce that the Update Profile Traits Widget is in Private Beta. Use this widget to take information you learn about a caller during a flow execution and send it to Unified Profiles to update profile trait data. This allows you to enrich profiles to personalize future customer experiences based on their profile traits. 

Visit the Update Profile Traits Widget docs to learn more.

As of Friday July 25th, the SMS Pumping Risk Score package within the Lookup API is now Generally Available!

SMS Pumping Risk Score allows you to get real-time risk assessment on a phone number's involvement in SMS pumping fraud. It uses a proprietary risk assessment model that leverages data across our network including signals from Verify Fraud Guard as well as other signals associated with risky carriers, anomalous SMS traffic patterns, and low conversion rates.

Additional Documentation on this feature can be found here

As of July 2024, the Reassigned Number package within the Lookup API is now Generally Available!

Reassigned Number allows you to Query the Lookup API with a phone number and the date you last verified consent to contact that user, and we will tell you whether the phone number has been reassigned to a new user since that date. Successfully querying this API prior to contacting a user grants you Safe Harbor from TCPA Violation Fees imposed by the FCC.

Additional Documentation on this feature can be found here

Twilio believes that the security of our products and our customers’ data is of paramount importance and when an incident occurs that might threaten that security, we tell you about it.

Twilio has detected that threat actors were able to identify data associated with Authy accounts, including phone numbers, due to an unauthenticated endpoint. We have taken action to secure this endpoint and no longer allow unauthenticated requests. 

We have seen no evidence that the threat actors breached Twilio’s systems or that they obtained access to Twilio's systems or other sensitive internal data. As a precaution, we are requesting that all Authy users update to the latest Android and iOS apps for the latest security updates. While Authy accounts are not compromised, threat actors may try to use the phone number associated with Authy accounts for phishing and smishing attacks; we encourage all Authy users to stay diligent and have heightened awareness around the texts they are receiving.

This latest update addresses bug fixes, which include security updates. Please click on the link to download the latest version: 

• Android

• iOS

We know the security of our systems is an important part of earning and keeping your trust. We sincerely apologize that this happened. The Twilio Security Incident Response Team will post any updates here if there are any changes. If you have further questions, please reach out to your Technical Account Manager or our Support team.

Notice: If you cannot access your Authy account, we recommend you immediately contact Authy support. One of our specialists will respond to your request, and work with you to get your Authy account back up and running again.

TaskRouter now enables you to route tasks directly to a specific worker or task queue. This can be helpful when: 

• A customer only wants to speak to one specific worker.

• A customer sends an email with a technical question the worker who received it is unable to answer. However, the worker knows a specific worker or task queue who can help that customer. 

• You need to route tasks based on additional criteria beyond what is supported in TaskRouter’s workflows. For example, this can be helpful when you want to check task queue depth and route to a different task queue based on wait times.

To route a task to a person, task queue, or workflow, specify the worker, task queue, or workflow in the RoutingTarget parameter. 

If you want to make sure that you don’t route a task to a worker who doesn’t currently have capacity, set the new IgnoreCapacity parameter to false. This parameter only applies when routing a task to a worker; it does not apply when routing to a task queue or workflow. 

By default, the IgnoreCapacity parameter is set to true when routing to a worker, meaning that the worker will receive the task even if they don’t have capacity. For example, a customer who calls to speak to a specific worker can be routed to that person and leave a voicemail if they’re not available, rather than be routed to a different worker.

For more information about routing tasks, see our Task Resource documentation.

TaskRouter routes tasks in priority order, starting with the highest priority. If multiple tasks have the same priority, it uses the task creation time to break the tie, sorting tasks from oldest to newest so that the oldest task is routed first. 

However, in some scenarios, the task creation time doesn't reflect the actual date and time that the customer interaction originally began, and the task is sorted lower than it should be. For example:

• A customer calls, waits for 20 minutes, and is offered a callback. The customer hangs up and a new task is created for the callback. The 20 minutes that the customer waited during the first call are not captured in the task creation time for the new task.

• A customer begins a conversation in one channel, such as chat, and switches to a different channel, such as a voice call. Moving to another channel creates a new task with a later task creation time, so the new task is prioritized lower.

To correct how these types of tasks are prioritized, you can now specify a "virtual start time," which is an optional parameter. When specified, virtual start time is used in place of the task creation time to determine where the task is sorted in the list. 

For example, if we added a virtual start time to the second task that was created in the callback example above, we could set it to match the time that the original task was created. That would enable the customer to keep their place in line for a callback.

For more information, see our documentation:

• Queue Ordering for a more detailed description of how virtual start time works, including examples

• VirtualStartTime on the Task Resource page for information about how to use this parameter

As of June 28th, 2024, Real-Time Transcription is available in public beta. This feature offers a seamless way for you to receive and utilize voice call transcriptions in real-time, integrating effortlessly with your business logic for applications such as call center quality assurance and lead generation.

Real-Time Transcription is designed to enhance your voice communications by providing real-time insights and analytics from your calls.