Why AMD Does Nothing in MANUAL and INBOUND_MAN Modes

You set the Campaign VDAD exten to 8369, you recorded a message, you double-checked the dialplan, and answering machine detection (AMD (answering machine detection)) still does absolutely nothing. Before you tear the config apart, check one thing: your dial method (Dial method). AMD does not run in MANUAL or INBOUND_MAN modes, full stop. This is the single most common reason detection appears broken.

The rule in plain terms

AMD only works with auto-dial methods, the modes where the dialer places calls on its own, such as ratio dialing (Ratio dialing) and adaptive dialing (Adaptive dialing). In MANUAL and INBOUND_MAN, an agent (Agent) places or receives calls by hand, and the call path simply does not run through the AMD-enabled processor at extension 8369. No processor, no analysis, no result.

Why the dial method matters so much

AMD is a server-side step that happens between the call connecting and the call reaching a person. The dialer needs to own that moment so it can insert the detection step and then decide where the call goes. In an auto-dial campaign (Campaign), the dialer is in full control of the call from the instant it answers, so it can route through 8369, run the analysis, and only then hand a live human to an agent.

In manual modes that control does not exist in the same way. The agent is on the call from the start, so there is no clean window for the dialer to silently analyze the audio and divert a machine. The whole point of AMD is to keep a human from ever hearing the machine, and in manual dialing (Manual dialing (click to dial)) the human is already there. By the time detection could form an opinion, the agent has already heard the greeting and the moment to save their time has passed.

flowchart TD
  A[Outbound call] --> B{Dial method}
  B -->|RATIO or ADAPT| C[Route through 8369]
  C --> D[Run AMD analysis]
  D --> E{Human or machine}
  E -->|Human| F[Send to agent]
  E -->|Machine| G[Divert or drop message]
  B -->|MANUAL or INBOUND_MAN| H[No AMD processor]
  H --> I[Agent hears whatever answers]

How to fix it

• Open the Campaign Detail page and check the Dial Method field. If it reads MANUAL or INBOUND_MAN, AMD cannot run on this campaign as configured.
• Switch to an auto-dial method such as RATIO or ADAPT if your campaign and your compliance rules allow it. Then confirm Campaign VDAD exten is 8369.
• If you must stay in a manual mode, AMD is off the table. Lean on a tuned dial timeout (Dial timeout) instead to reduce voicemail pickups, since that works regardless of dial method.
• After switching modes, do not assume it works. Place a handful of test calls to numbers you control, including one that hits a voicemail box, and confirm the machine call is handled the way you expect rather than landing on an agent.

There is a related trap worth flagging. Some operators see the setting on the screen, set Campaign VDAD exten to 8369, and assume that alone forces AMD on. It does not override the dial method. The two have to agree: an auto-dial method and 8369 together. Either one without the other leaves you with no detection, which is exactly why this issue is so easy to misdiagnose.

It is worth being honest about the trade-off here. Auto-dial methods bring their own pacing and compliance considerations, so do not flip to RATIO purely to get AMD without thinking about how aggressively you want to dial. If you are weighing whether AMD is even worth it for your setup, read when to use VICIdial AMD.

For a refresher on what AMD is and where it fits among detection tools, the AMD and CPD complete guide covers the full landscape.

Let us sort the mode for you

Choosing a dial method that fits both your AMD plans and your compliance posture is the kind of decision we help with directly. On VICIfast we configure the campaign, confirm AMD actually fires, and verify it against test calls. To get that hands-on setup, see VICIfast pricing.