Hi team! Just experienced a failed call :

b0033ec9-b533-473a-a710-93ef72d83dd4

that I can't manage to explain. Seems like 11labs' fault ? -> The user said "Allo, Allo, ..." -> Assistant has time to answer but is'n't saying anything -> Ends up with a Twilio AMD error as the assistant does not say anything @Shubham Bajaj could you help me understand ?

For unexplained failed calls like this, the best next step is to contact Vapi support with your call ID and account email for a detailed investigation. You can do this by emailing [support@vapi.ai](support@vapi.ai) or using the [support page](https://docs.vapi.ai/support). This will allow the team to review backend logs and help determine if the issue is related to ElevenLabs, Twilio, or another component. Tip: Include the call ID

b0033ec9-b533-473a-a710-93ef72d83dd4

and a description of the issue in your message for faster resolution. Sources: - [Vapi Support Documentation](https://docs.vapi.ai/support) - [Call Ended Reasons](https://docs.vapi.ai/calls/call-ended-reason)

@User 😉

Looking into it

@Omogen Since the VoiceMail message was not set, and the call was detected as voicemail, the call ended with the reason`"customer did not answer`

logs

19:48:16:431 [LOG] Customer is known as voicemail,

twilio

detected beep, speaking message...

Yes thanks! I was wondering if the fact that the agent doesn't speak comes from an 11labs/openai incapacity at that moment. But probably just some random latency! Thanks

Glad the issue was resolved. Please reach out to us if you have any other questions regarding this issue