Twilio AMD
We enabled VAPI voicemail detection on our product, but noticed that we're still getting billed for Twilio AMD. Is this expected behavior? If so, how can we ensure that Twilio AMD is disabled?
VEnabling Vapi voicemail detection does not automatically disable Twilio AMD (Answering Machine Detection) or its billing. To avoid Twilio AMD charges, ensure that AMD is disabled in your Twilio trunk or number configuration. In your Twilio Console, check your SIP trunk or phone number settings and make sure AMD is turned off, as Vapi's detection will handle voicemail detection independently.
Source:
Source:
⤵️ Mention @Vapi Support Bot for follow-ups 🐥
KCan you please provide a call id? We can investigate the logs and look at your assistant config
BHere is a call ID for you:
5dfd76d0-bd0b-4960-a6e1-5c89a6a5440fKLooks like your assistant config is correct, just check on the twilio dashboard to make sure AMD is turned off.
TWe never enabled AMD manually in twilio, and the twilio docs mention that it's enabled per-request when sending the outbound call. Do you happen to know where we would disable this in the dashboard or verify that it's no longer being used? (note that I'm chiming in here because I'm part of the same dev team - I promise I'm not just drive-by sniping the thread 
)
)BHere is the relevant documentation: https://www.twilio.com/docs/voice/answering-machine-detection#making-a-call-with-amd
Detect whether a human, answering machine, or fax machine has picked up your outbound voice API calls with Twilio's REST API Answering Machine Detection
KNot sure where to disable in the dashboard, but via API you can make these changes
BJust tried your suggestion and unfortunately it doesn't work. It looks like the API doesn't allow us to set
enableTwilioBeepDetection. Perhapse this property does not exist?
KAh my mistake, it was a property that exists in the codebase but is unable to be modified via API endpoint. If you absolutely need AMD, VAPI AMD by default uses twilio as a fallback, but this snippet may disable the fallback while still keeping VAPI AMD:
U@DonutDeflector Did you find a way to solve this?
B@Alan Moran It seems like VAPI's voicemail detection method uses a hybrid approach, combining Twilio's machine beep detection and LLM analysis. So getting billed for Twilio beep detection is actually expected behavior.
UHey! I got this response too but something is not sitting right. If I didn't link my Twilio account how would this work, still awaiting a response.
