AMD vs a Longer Dial Timeout: Which Dodges Voicemails Best

You are tired of agents picking up calls that turn out to be voicemail greetings. There are two clean ways to handle this in VICIdial, and they pull in opposite directions. One is answering machine detection (AMD (answering machine detection)), which analyzes the audio after a call connects. The other is simply tightening your dial timeout (Dial timeout) so the dialer hangs up before most machines pick up. This post helps you pick the right tool for the job.

What each one actually does

AMD lets the dialer route more live-human answers to agents while diverting answering-machine and voicemail calls somewhere else. It works by running an audio analysis on the connected call before deciding where to send it. The catch is that it adds processing time to every single call, not just the ones that hit a machine, and it is never perfect. You have to tune it to your leads and your telecom lines or you will get false positives, where a real person gets flagged as a machine.

Dial Timeout is far simpler. If set, it caps ring time at the number of seconds you choose whenever that value is less than the timeout in your dialplan (Dialplan). Most answering machines and voicemail systems pick up in a predictable window, so if you cut ring time to roughly 22 to 26 seconds, a large share of those machines never get the chance to answer. The call just times out as a no-answer instead.

How to choose

flowchart TD
  A[Goal cut voicemail pickups] --> B{Do you need to route live calls precisely}
  B -->|No just fewer machines| C[Set Dial Timeout 22 to 26]
  B -->|Yes split human vs machine| D[Turn on AMD]
  C --> E[No extra processing on calls]
  D --> F[Tune AMD to leads and lines]
  F --> G[Watch false positives]

For most campaigns, the simpler path wins. A tuned Dial Timeout costs you nothing on connected calls, needs no AMD tuning, and changes per campaign without an Asterisk reload. Reach for AMD when you genuinely need to separate humans from machines on calls that do get answered, for example when you want to leave a recorded message on machines through voicemail drop (Voicemail drop) while sending live people straight to an agent (Agent).

• Use Dial Timeout when your only goal is fewer machines reaching agents and you want zero added latency.
• Use AMD when you want to act on machines, such as dropping a message, instead of just dodging them.
• Combine carefully. AMD plus a very short timeout can fight each other, since a short ring window already filters many machines before AMD ever runs.

The compliance guardrail

Do not crank Dial Timeout down too far. USA FTC Safe-Harbor rules (FTC Safe Harbor) require at least 15 seconds of ring time, about four rings, on business-to-consumer calls. That is why the 19 to 26 second range is the sweet spot: long enough to stay compliant, short enough to skip a chunk of voicemail systems. AMD does not change this rule either, since the call still has to ring before anything answers.

If you are still deciding whether AMD belongs on your campaign at all, our guide on when to use VICIdial AMD walks through the trade-offs by campaign type. And for the complete picture on detection, read the AMD and CPD complete guide.

Get help dialing it in

On VICIfast we can set either approach up with you and watch your real results before committing to a number. If you want a managed VICIdial environment where AMD tuning and timeout testing are handled for you, see VICIfast pricing and we will help you choose the right path for your campaign (Campaign).