What changed in Twilio Voice Insights for blocked calls on October 1, 2026?
On October 1, 2026, Twilio said Voice Insights now tells you why a carrier blocked your call and how to reach that carrier for redress. Before, a blocked call showed you only a 603 response.
Twilio's changelog entry says the data comes from a reason header. It credits an FCC requirement that carriers who block calls using analytics return that header to the caller. The header names the blocking network and gives a contact method, which can be a URL, a phone number or an email address. Twilio shows it next to Last SIP Response in the Call Summary in Twilio Console, in the Voice Insights REST API, and in Event Streams.
Why does a blocked or spam-labelled call matter to a business owner?
A blocked call is a lost lead or a missed appointment, and the owner usually never finds out. An AI calling agent that dials new leads, or a reminder call that never rings, just looks like silence in your reports.
Until now the only clue was a 603 response, which says a call was declined but not by whom or why. Owners ended up guessing: change the number, change the script, blame the AI. The reason header gives a name and a place to file a complaint instead.
What does the reason header tell you?
It tells you which network blocked the call and how to contact that network to dispute the block. Twilio's Call Summary documentation describes it as the reason header from the carrier that blocked the call, with redress contact information.
According to that documentation, the field only appears for calls that receive a 603+ SIP response, which indicates the carrier blocked the call. A call that fails for another reason will not have it.
How do you look up the reason header for a blocked call?
Open the call in Twilio Console, go to the Call Summary in Voice Insights and read the reason header next to Last SIP Response. You can also pull it from the Voice Insights REST API or Event Streams if you track calls in your own system.
- Find calls that ended in a 603 response.
- Open the Call Summary for one of them and read the reason header.
- Note the blocking network and the contact method it gives.
- Repeat for a few calls to see whether one network is behind most of the blocks.
How do you file a redress request for a blocked call?
Use the contact method in the reason header. Twilio's entry says it is a URL, a phone number or an email address for the network that blocked the call.
Before you file, follow Twilio's own advice: if you see many 603 responses, confirm your traffic is signed with STIR/SHAKEN and registered with Twilio Voice Integrity. Voice Integrity is a Trust Hub offering that registers your US numbers with major analytics engines to help remediate spam labels. It requires an approved business profile, and only numbers assigned to that profile can be registered. Twilio's pages do not describe a standard form or a response time for redress requests, so what you must submit and how long it takes depends on the blocking network. That part is unverified.
Does this mean HighLevel shows the reason header too?
Unknown. Neither Twilio's entry nor any HighLevel source we checked says HighLevel exposes this header, so do not assume it does.
If your HighLevel account sends calls through LC Phone, we could not confirm that this data reaches you. Check your own call logs for a blocked-call reason, and ask HighLevel support if you see none. If you run Twilio directly or a custom build on it, you can use Voice Insights today.
What does this mean for outbound AI calling and appointment reminders?
Treat blocked calls as something you can measure and dispute. Registered numbers, signed calls and a caller name that matches your business give carriers less reason to label you, and the header shows you who to contact when they still do.
AI calling agents that place many first-touch calls to new leads are the most likely to draw analytics-based blocks, and a block can hide inside normal "no answer" results. Reminder calls fail the same way, and a patient or customer who never got the call simply no-shows. Review blocked-call counts as a regular report, not only after a complaint. If you are building outbound voice, see our AI calling agent service or AI receptionist. Blocking is only half the picture. Consent rules apply too, covered in HighLevel Voice AI outbound consent and is AI calling legal. Text messages have their own filtering, which we cover in HighLevel A2P rejection guidance.
How do you diagnose and fix a blocked call?
Start from the symptom, read the reason header, then fix registration and signing before you file a dispute.
| Symptom | Likely cause | Action |
|---|---|---|
| Call ends in a 603 response and you do not know why | A carrier blocked it using analytics | Open the Call Summary and read the reason header |
| Many 603 responses across numbers | Traffic not signed with STIR/SHAKEN or numbers not registered (Twilio's first check) | Confirm signing and register numbers in Voice Integrity |
| 603 responses mostly from one network | That network's analytics label your numbers | File a redress request with the contact method in the header |
| Header shows nothing | The call did not get a 603+ response, or your platform does not pass the field on | Check the final SIP response; on HighLevel, check your call logs and ask support |
| Calls connect but show a spam label | Number reputation (not covered by this changelog entry) | Register the number and keep the caller name matching your business |
The last row and the advice to keep the caller name matching your business come from the purpose of Voice Integrity and general practice, not from the changelog entry itself.
Frequently asked questions
What does a 603 response mean on a business call?
A 603 is a SIP response meaning the call was declined. Twilio says that until this update a blocked call showed only that response. Its Call Summary documentation says the new reason header appears only for calls that receive a 603+ response, which indicates a carrier blocked the call.
Does the FCC require carriers to tell callers when they block a call?
Twilio's changelog says the FCC requires carriers that block calls using analytics to return a reason header to the caller, naming the blocking network and a contact method. Twilio links to its blog for the details. We did not read the FCC order text itself, so check the order if you need exact wording.
What should I check before filing a redress request?
Twilio advises that if you see many 603 responses, you first confirm your traffic is signed with STIR/SHAKEN and registered with Twilio Voice Integrity. Fixing those first can reduce blocks. Then use the contact method in the reason header to dispute any block that remains.
Will my HighLevel account show the reason header?
We could not confirm it. No HighLevel or Twilio source we read says HighLevel shows this field. If your account uses LC Phone, look at your own call logs for a blocked-call reason and ask HighLevel support. If you use Twilio directly, Voice Insights shows it.
Sources
- Twilio changelog, Voice Insights now shows why carriers block your calls, October 1, 2026, checked 2026-10-14.
- Twilio docs, Voice Insights Call Summary, checked 2026-10-14.
- Twilio docs, Twilio Voice Integrity, checked 2026-10-14.
- Twilio blog, FCC new standard for blocked calls (603+), dated September 15, 2025, checked 2026-10-14. It cites FCC order FCC-25-15A1 and says use of 603+ becomes required by March 25, 2026. It does not itself mention the reason header or explain how to file redress.
