Need Clarity + Action: Disable Twilio AMD for Outbound Calls via Vapi
Hey @Vapi Team 
— I’m still trying to get a clear answer on how to fully disable Twilio’s Answering Machine Detection (AMD) for outbound calls made through Vapi.
Here’s the situation and context so far:
I’m using Vapi + Twilio for outbound campaigns.
Even though I have Vapi’s voicemail detection enabled, Twilio’s AMD still seems to trigger — causing duplicate voicemail detection, added delay, and extra Twilio charges.
I can’t manually set machineDetection: 'none' because Vapi handles the API call to Twilio internally.
I’ve already been told a few different things:
Vapi Support Bot (Oct 13): said I need to contact support to have AMD disabled “at the integration layer for my organization.”
Email response (Aniah @ Vapi, Oct 14): said I need to disable AMD directly in Twilio, but Twilio doesn’t allow that at the account or number level — only through the API call.
Kyle (Oct 15): mentioned that Vapi’s VMD uses both Twilio and Google, and that I can turn off VMD in the dashboard, but that doesn’t seem related to Twilio AMD behavior.
So I’m stuck between two conflicting explanations — some say it can be disabled by the Vapi team, others say it must be done in Twilio (which isn’t possible via console).
Can someone please clarify definitively:
Does Vapi set MachineDetection in its outbound API calls to Twilio?
If yes, can you please disable it for my organization so AMD is completely off?
If not, what’s the correct path to ensure Twilio’s AMD never activates when calls are initiated through Vapi?
I just want to make sure calls flow smoothly and avoid duplicate detection or charges.
Happy to provide specific call IDs or logs if that helps.
Thanks a lot — really appreciate some clarity and a clear next step
– Mike Mitchell
— I’m still trying to get a clear answer on how to fully disable Twilio’s Answering Machine Detection (AMD) for outbound calls made through Vapi.Here’s the situation and context so far:
I’m using Vapi + Twilio for outbound campaigns.
Even though I have Vapi’s voicemail detection enabled, Twilio’s AMD still seems to trigger — causing duplicate voicemail detection, added delay, and extra Twilio charges.
I can’t manually set machineDetection: 'none' because Vapi handles the API call to Twilio internally.
I’ve already been told a few different things:
Vapi Support Bot (Oct 13): said I need to contact support to have AMD disabled “at the integration layer for my organization.”
Email response (Aniah @ Vapi, Oct 14): said I need to disable AMD directly in Twilio, but Twilio doesn’t allow that at the account or number level — only through the API call.
Kyle (Oct 15): mentioned that Vapi’s VMD uses both Twilio and Google, and that I can turn off VMD in the dashboard, but that doesn’t seem related to Twilio AMD behavior.
So I’m stuck between two conflicting explanations — some say it can be disabled by the Vapi team, others say it must be done in Twilio (which isn’t possible via console).
Can someone please clarify definitively:Does Vapi set MachineDetection in its outbound API calls to Twilio?
If yes, can you please disable it for my organization so AMD is completely off?
If not, what’s the correct path to ensure Twilio’s AMD never activates when calls are initiated through Vapi?
I just want to make sure calls flow smoothly and avoid duplicate detection or charges.
Happy to provide specific call IDs or logs if that helps.
Thanks a lot — really appreciate some clarity and a clear next step
– Mike Mitchell
