AMD false positive

An AMD false positive happens when amd (Answering Machine Detection) decides a real, live person is actually a machine. The person says hello, the detector misreads the pause or the tone, and the call gets hung up or routed away before an agent ever connects. From the prospect's side it just looks like a dropped or dead call, which is a poor first impression; from your side it is a lost contact you already paid to dial, and you may never get them to answer again.

This matters because AMD has to make a fast guess from the first second or two of audio. People who answer slowly, say a long hello, or have noisy lines can easily look like a voicemail greeting to the detector. Tuning beep detection and the detection timers too aggressively raises the false-positive count, while loosening them lets more real machines slip through to agents. There is no perfect setting; every campaign trades one kind of error for the other, and the right balance depends on how costly each mistake is for you.

How to catch it

Watch your contact rate against your dial volume. If AMD is switched on and your contact rate is lower than it should be, false positives may be quietly eating live answers. The trouble is that a false positive looks a lot like an abandoned call, so it can muddy your abandonment rate and drop rate numbers too, and you can end up chasing the wrong problem if you only read the totals.

To keep the error low, listen to a sample of AMD-classified calls now and then, lean on accurate answer supervision from your carrier, and only tighten the timers when you can prove machines are actually leaking through. Small adjustments, tested on real traffic and reviewed by ear, beat aggressive defaults you set once and never check again.