Voice Insights now shows why carriers block your calls

Voice Insights now tells you why a carrier blocked your call and how to reach that carrier for redress.

The FCC requires carriers that block calls using analytics to return the reason header to the caller. It names the network that blocked the call and tells you how to contact them: a URL, a phone number, or an email address. Until now a blocked call showed you only a 603 response. Now you can see which network blocked it and petition them directly.

The reason header appears alongside Last SIP Response in the Call Summary, in Twilio Console, the Voice Insights REST API, and Event Streams.

If you are seeing a high volume of 603 responses, confirm your traffic is signed with STIR/SHAKEN and registered with Twilio Voice Integrity before you start filing redress requests.

Learn more in our Call Summary documentation.