Call ID : 019cd6a8-3473-7773-8aad-18a32ccf393e Time stamp : Mar 10, 2026, 21:50 Expected Response : The call must be passed to the customer Actual Response : "Twilio Connection Failed" occured and the call was not even passed to the customer

For your urgent Twilio connection error, please check the call logs in your Vapi dashboard using the Call ID (

019cd6a8-3473-7773-8aad-18a32ccf393e

). Look for the

endedReason

code—if it shows

twilio-failed-to-connect-call

, verify your Twilio configuration and ensure the destination number is in the correct format (including country code). Example API call to fetch call details:

curl -X GET "https://api.vapi.ai/call/019cd6a8-3473-7773-8aad-18a32ccf393e" -H "Authorization: Bearer YOUR_API_KEY"

This will help you pinpoint the exact cause and next steps. Source: - [Call ended reasons documentation](https://docs.vapi.ai/calls/call-ended-reason)

This is what I got when I searched with the Call ID in the call logs https://cdn.discordapp.com/attachments/1481873699672952964/1481897810457792623/Screenshot_from_2026-03-13_11-42-31.png?ex=69b4fc62&is=69b3aae2&hm=2fca7c165ff87362c9473ab67cc884bd2bc15bfc9ee82e0d9cde840f7ee9484d&

It looks like the call failed at the point where it should’ve been handed off, and the “Twilio Connection Failed” error prevented it from reaching the customer. I’ve run into similar issues before where the call logs show the attempt but the handoff fails due to a configuration or connection step in the flow. Sometimes it’s related to how the Twilio bridge or webhook is set up rather than the call itself. @Azhar If you’re open to it, feel free to share a bit more about how your call routing or Twilio setup is configured I might be able to help narrow down where it’s breaking.

Actually this number +1 (318) 610 1377 was given for the customer and using Vapi we created campaigns to call this customer, and when the campaign executed we got this issue, What are the chances to get this "Twilio Connection Failed" issue

That error can happen occasionally, but it usually isn’t random. In most cases when I’ve seen “Twilio Connection Failed” during an outbound campaign, it’s tied to things like the destination number formatting, Twilio trunk/bridge configuration, or a temporary carrier connection issue when the call is being handed off. If it only happened once during the campaign, the chances are fairly low and it might just be a transient connection issue but if it repeats consistently for that number @Azhar

Hi, After reviewing the logs, it appears that Twilio’s telephony system failed to establish the connection and returned a CallStatus=failed webhook, which Vapi correctly processed. The timing pattern: multiple failures occurring at the exact same time, strongly suggests that the campaign attempted to launch too many outbound calls simultaneously, which may have exceeded your Twilio account’s concurrent call limit. When this limit is reached, any additional calls may immediately fail. Recommended next steps: 1. Check your Twilio Dashboard to review the specific ErrorCode / ErrorMessage for the affected calls. This will confirm the exact reason from Twilio’s side. 2. Review your Twilio account’s concurrent call limits to ensure that your current account tier supports the campaign volume you are trying to run. 3. Stagger the campaign calls instead of initiating them all at the same time. Adding a small delay between calls can help prevent hitting concurrency limits.