First time unanswered calls are being handled correctly as voicemail, however second time calls are being marked as customer ended call despote the fact that the call has gone to voicemail https://cdn.discordapp.com/attachments/1359916492396695714/1359916492807999731/Screenshot_2025-04-10_164118.png?ex=67f9386d&is=67f7e6ed&hm=ccf7b6f506929ea2220b2852f30893e13e7a9055993311ee898f9a8c67c40e9d&

Hi there! 👋 I see you're experiencing an issue where second call attempts are being incorrectly marked as "customer ended call" instead of being properly identified as voicemail. I don't have access to your specific account settings, but I can definitely help troubleshoot this issue! Based on the information I've found, this is a known issue that can occur with Vapi's voicemail detection. Here are some troubleshooting steps you can take: ### Check Voicemail Detection Configuration The issue might be related to your voicemail detection settings: 1. Review your voicemail detection settings - Make sure they're properly configured for both first and second call attempts. According to the [documentation on voicemail detection](https://docs.vapi.ai/phone-calling/voice-mail-detection), Vapi uses two methods: - Twilio's built-in voicemail detection - Vapi's own LLM-powered voicemail detection tool 2. Check your

machineDetectionTimeout

setting - If this is set too low (e.g., 4 seconds), it can cause legitimate calls to be cut off prematurely and misclassified. Try increasing this value to give the system more time to properly detect voicemail. 3. Verify your

voicemailDetectionTypes

- Ensure these include all relevant types:

machine_start

,

machine_end_beep

,

machine_end_silence

,

unknown

, and

machine_end_other

. ### Additional Settings to Check Some users have resolved similar issues by: 1. Setting

endCallFunctionEnabled

to true in the dashboard, which has helped resolve this issue for other users. 2. Adjusting speech and silence thresholds - Parameters like

machineDetectionSpeechThreshold

,

machineDetectionSpeechEndThreshold

, and

machineDetectionSilenceTimeout

can affect how Vapi interprets call endings. ### Potential Causes This issue might be occurring because:

Hey! To help track down this issue, could you share: - The call ID This would really help us figure out what went wrong!