absent-sapphire•5d ago

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

7 Replies

like-gold•4d ago

Hey Mike 👋 I’ve dealt with this before — the AMD conflict usually happens because Vapi auto-sets machineDetection in its Twilio API call, even when you enable VMD separately. I can help check your call logs to confirm this and suggest a config workaround. Could you share a couple of recent call SIDs? That’ll help pinpoint if Twilio’s AMD is being forced on the Vapi side. @dialverse.ai

absent-sapphireOP•2d ago

my goal is that I want to set AMD off if I'm using Vapi as the voicemail provider @IBM Flow ill share a couple of calls with you that are voicemails 0199ef3e-de44-7119-a4f2-a85ad7f7f5de 0199ef3d-be41-711c-b90e-8b24e6b95e9b 0199ef3c-c1e7-7ddf-86b7-7fdf632f67d8 @IBM Flow let me know if there is any updates any support here guys? @Vapi @Duckie

Vapi•2d ago

To fully disable Twilio's Answering Machine Detection (AMD) for outbound calls via Vapi, you must contact Vapi support and request that AMD be turned off at the integration layer for your organization.
There is currently no user-facing API or dashboard setting to control Twilio's machineDetection parameter directly from your end.
Action step:

Email Vapi support with your organization details and request that Twilio AMD be disabled for all outbound calls.

This is the only documented way to ensure AMD is completely off when using Vapi as the voicemail provider, preventing duplicate detection and extra charges. Sources: - Vapi Voicemail Detection Documentation - Vapi Changelog

⤵️ Mention @Vapi Support Bot for follow-ups 🐥

absent-sapphireOP•2d ago

@Duckie can you generate me an email that will ensure vapi support will disable AMD for me with all the prior context to the converastion

Vapi•2d ago

Here’s an email template you can use to request that Vapi disables Twilio AMD for your organization:

Subject: Request to Disable Twilio AMD for Outbound Calls via Vapi

Hi Vapi Support Team,

Please disable Twilio's Answering Machine Detection (AMD) for all outbound calls made through Vapi for our organization. We are experiencing duplicate voicemail detection and extra charges, and need AMD turned off at the integration layer as per your documentation. Organization: [Your Org Name]. (Optional: Recent call SIDs for reference: [Insert SIDs here])

Thank you!

Subject: Request to Disable Twilio AMD for Outbound Calls via Vapi

Hi Vapi Support Team,

Please disable Twilio's Answering Machine Detection (AMD) for all outbound calls made through Vapi for our organization. We are experiencing duplicate voicemail detection and extra charges, and need AMD turned off at the integration layer as per your documentation. Organization: [Your Org Name]. (Optional: Recent call SIDs for reference: [Insert SIDs here])

Thank you!

Just fill in your organization name and any relevant call SIDs, then send this to Vapi support. This is the recommended and only documented way to ensure AMD is fully disabled when using Vapi as your voicemail provider. Sources: - Vapi Voicemail Detection Documentation - Vapi Changelog

absent-sapphireOP•18h ago

@Shubham Bajaj hi brother any support on this

Shubham Bajaj•2h ago

You can turn Voicemail Detection off in your assistant settings

Need Clarity + Action: Disable Twilio AMD for Outbound Calls via Vapi

Did you find this page helpful?