Detection Accuracy

Use this guide if AMDY's results don't look right — voicemails reaching agents, false positives, accuracy that dropped, or too many calls being marked as answering machines.

First: get recordings

Don't troubleshoot accuracy from memory — always work from the actual call recordings.

1. In VICIdial: Reports → Export Calls Report. Set your date range and campaigns, status A, Rec Fields LOCATION, Export Type EXTENDED.
2. Upload the exported file to https://recs.amdy.io.
3. Listen to the calls in question and confirm what AMDY actually heard.

What you'll hear: - A genuine voicemail usually repeats the phone number ("you've reached 305-555-…"). - A false answer (FAS) is a carrier message such as "the call has been forwarded to an automatic voice message system" — no real person was ever on the line.

Common cases

Voicemails or false answers reaching agents

• Carrier "false answers" (FAS) happen when the carrier reports a call as answered even though no one picked up. There is no real audio session on these calls.
• Pull the calls from the recording portal to confirm what happened, and note each call's V-prefixed code when you contact support.

Too many answering-machine results on certain numbers

If specific outbound numbers produce a high answering-machine rate: 1. Check the DIDs (caller IDs) first — not AMDY. Those numbers may have a poor reputation. 2. Look them up in a DID reputation service such as FraudCentral.io. 3. If a DID's reputation is bad, rotate to fresh DIDs — that usually resolves it.

"It worked better yesterday"

Work through this in order: 1. Check your DIDs' reputation (see above) — reputation degrades over time. 2. Try a more aggressive detection ratio (for example, 8 instead of 5). 3. Review recordings — has your call mix changed (more spam-trap or automated answers)? 4. If outbound errors also started today, run the Connection problems check.

Routing genuine voicemail differently from other results

VICIdial's dialplan can branch on the AMD result, but there is no built-in one-click filter that separates "real voicemail" from other voicemail-like results — that needs a small custom dialplan script. Contact support if you'd like help designing one.

Results look like they came from the wrong detector

If a result looks unlike AMDY's normal output, confirm your campaign's Routing Extension is 8370 (AMDY) and not 8369 (standard Asterisk AMD). See Setup & installation.

What this guide is not for

• "AMDY isn't running" or "no logs" → Setup & installation
• "Agents are getting hung up on" with no misclassification → Agent & call experience

For what each result means, see Understanding AMD statuses & timing.