call id: b736e123-8ffd-4b0a-a84b-5a523eb127ae

To help track down this issue, could you share one or two: - When exactly this happened (the timestamp) - What response you expected to get - What response you actually got instead This would really help us figure out what went wrong!

I figured you could see all that with the call ID this was using twilio voicemail detection because the vapi detection was broken. 1 out of 5 calls that where detected voicemail would play both the first message and the voicemail message back to back , most voicemails played the voicemail message only. I am using the vapi voice detection now, if this happens again I will create a new support with the data you requested

voicemail_config

"firstMessageMode": "assistant-waits-for-user",
      "voicemailDetection": {
        "provider": "twilio",
        "enabled": true,
        "voicemailDetectionTypes": [
          "machine_end_beep",
          "machine_end_silence"
        ]
      }

logs

🔵 19:58:38:061 [user LOG] Twilio detected "machine_end_beep" in 9599ms You needs to play with voicemail settings. There is no one method that works for all universal kinds of settings. Also needs to do A/B testing, testing out different values for your calls and according to your calls. For more you can learn from here, and even can try out VAPI's voicemail detection as well which we recently launched https://docs.vapi.ai/calls/voicemail-detection