voicemail detection
# support
v
I’m having trouble getting voicemail detection to work. Ideally I would like it to identify the answering machine and end the call before it connects. I’ve played around with a bunch of settings and timers in ‘Update Assistant’ documentation. However, every time it seems to leave an awkward message (Eg. start greeting followed by 30s of silence before hanging up). This is not only costing me $, but it leaves a poor impression on potential business customers. Has anyone had success with setting this up so it actually works. Ie. Ends the call before or at the ‘beep.’ ??? Any help would be greatly appreciated 🙏
v
@V1PER.6 I'm sorry to hear you're experiencing issues with the voicemail detection. It sounds like you've been proactive in trying to adjust the settings to get it right. To ensure the system ends the call before the answering machine's beep, we need to fine-tune the voicemail detection settings. Based on the context you've provided, here are a few suggestions: 1. **Machine Detection Timeout**: The
machineDetectionTimeout
parameter is currently set to 31 seconds. This might be too long if the goal is to hang up before the answering machine beep. Consider reducing this timeout to a shorter interval that aligns with the typical duration before the beep occurs on most answering machines. 2. **Speech Thresholds**: The
machineDetectionSpeechThreshold
and
machineDetectionSpeechEndThreshold
are set to 3500 and 2750 milliseconds, respectively. These settings determine how long the system considers a voice to be an answering machine. Adjusting these thresholds might help the system better differentiate between a human and an answering machine. 3. **Silence Timeout**: The
machineDetectionSilenceTimeout
is set to 6000 milliseconds (6 seconds). If the system is waiting for 6 seconds of silence before making a decision, it might be too late. Reducing this timeout could help the system decide faster and hang up before the beep. 4. **Detection Types**: Ensure that the
voicemailDetectionTypes
includes both
machine_end_beep
and
machine_end_silence
. This allows the system to use both cues to detect an answering machine. Would you like me to assist you in adjusting these settings? If so, please provide the desired values for each parameter, and I'll help you update them accordingly.
You can continue this conversation by mentioning me in the message.
v
So this seems to be an infra error that is occuring. Everything seems to be working from the outset. Ie. The Vapi call recording actually stops at the point the voicemail message ends. (This gives the impression that the AMD is working, yet the call actually continues past this point for another 30 seconds - unaccounted for by your system). However, if you refer to the actual call outcome it states "silence timed out." This is reflective of the experience (I called my own phone number to test the theory and sure enough once the voicemail message ends the assistant states the start greeting. ie. "Hey, how's it going?" and then continues to wait on the line in silence until it is timed out and automatically ended after 30s timeout.) For reference here is the call ID: d351301c-c08e-4955-8733-4c9362b85efc Let me know if you would like me to send the voicemail recording from my phone...
Update: SUCCESS ✅ I have been playing around with further settings and seems to be working correctly now.. I applied the following:- "provider": "twilio", "enabled": true, "machineDetectionTimeout": 5, "machineDetectionSpeechThreshold": 2400, "machineDetectionSpeechEndThreshold": 1000, "machineDetectionSilenceTimeout": 3000 }, I am still getting billed by both Twilio and Vapi for those 5 seconds but it's better than leaving random voicemails on customers accounts. ⚠️
5 Views