AMD and voice alerts: fewer false connects and wasted minutes

Answering machine detection sounds solved until the invoice shows minutes spent talking to voicemail greetings, IVR trees, and hold music. A false connect is not a rounding error — it is a paid minute that produced zero signal, plus a support ticket asking why an "urgent alert" played into an answering machine at 2am. Serious B2B teams treat AMD as a tuned control with owners, not a checkbox on a dialler feature list.

IOSOR keeps outbound voice alerts inside the same prepaid white-label wallet story as messaging: every dial attempt is a debit line, AMD behaviour is visible before volume, and a corridor stays honestly in setup until detection has been proven on your traffic — never marketed as universally solved.

False connects are a budget line, not an edge case

Every misclassified answer costs twice: the wasted minute itself, and the downstream cost of a missed or mistimed alert. Before raising volume, write down what a false connect actually means for your use case — a fraud alert that never reaches a human is not the same failure as a reminder that plays into voicemail.

How AMD actually decides human vs machine

AMD reads short audio cues — greeting length, energy pattern, pause after pickup — and guesses within roughly the first second or two. That guess is probabilistic, not certain.

Neither setting is "correct" in isolation — it depends on what the call is for.

Tune per severity class, not one global setting

A single AMD threshold across every campaign guarantees someone is unhappy.

1. Safety / fraud alert — bias toward reaching a human fast; a rushed greeting is cheaper than a missed alert.
2. Appointment / delivery notice — balanced default; a short pre-recorded fallback is acceptable.
3. Soft reminder / nurture — bias toward accuracy; never play a scripted line into a stranger's personal voicemail without review.

Document the class-to-threshold mapping so a new campaign cannot inherit the wrong bias by accident.

Where wasted minutes actually hide

Spend leaks rarely announce themselves as one bad setting.

Red flags

• One AMD threshold applied to every campaign regardless of purpose
• No log that lets you compare AMD guess against actual outcome
• Immediate voice retry on every ambiguous or machine-classified attempt
• No prepaid line-item visibility per dial
• Support blaming "the algorithm" with no owned tuning policy
• Live badge on a market with no reviewed call cohort

Start with IOSOR

Pick one severity class and one corridor. Write the AMD bias you want — reach a human fast for fraud, balanced for appointment notices. Run a real cohort, then compare each AMD guess to the actual human or machine outcome in the call log. Open the prepaid voice line: wasted minutes on greetings and hold music must be a named debit, not a mystery.

• Voice billing rounding and connect fee export
• TTS Language Locale Fallback for International Voice OTP Delivery
• Account access is not production send

IOSOR takeaway

Do: tune AMD per class, not one global threshold. Log the guess against the outcome before you raise volume. A false connect is a paid minute that produced zero signal.

Don't: retry immediately on every machine or ambiguous class, and don't blame the algorithm in support when the invoice is the log you never kept.