Go back to dialerseat.comsales@dialerseat.com
Guide

Answering machine detection (AMD), explained for developers

Answering machine detection (AMD) listens to the first seconds after a call is answered and decides whether a person or a machine picked up, from the length of the greeting, the silence after it and the beep. Voice APIs sell it per call: Twilio lists $0.0075, Telnyx $0.002 for standard and $0.0065 for premium. What your code does with each verdict decides whether agents hear people or voicemail.

Checked 2026-11-15 against the sources linked at the end.

How AMD decides

A person usually answers with a short greeting and waits. A voicemail greeting runs longer, without a pause, and often ends in a beep. AMD listens for those patterns in real time and returns a verdict while the call is live.

Verdicts vary by provider. Telnyx's detect setting returns human or machine; its premium setting returns human_residence, human_business, machine, silence, fax_detected or not_sure, and reports a beep separately. Some settings keep listening after a machine verdict until the beep, so a message can be left at the right moment.

What it costs on a voice API

ProviderAMD price on its own pricing page
Twilio$0.0075 per call
Telnyx, standard$0.002 per call
Telnyx, premium$0.0065 per call

These are per-call prices on top of the minutes. Each provider notes that rates can vary; check its page before you budget.

The two-second rule

In the US, the Telemarketing Sales Rule counts a call as abandoned when a person answers and is not connected to a sales representative within two seconds of finishing their greeting, 16 CFR 310.4(b)(1)(iv). A detector that is still listening after a person has said hello is spending those two seconds. Fast verdicts on people matter more than perfect verdicts on machines.

Screened calls are a third answer

iPhones can screen unknown callers, and Live Voicemail transcribes a message while the phone rings. To a detector this is neither a clean human nor a clean machine. Telnyx's premium AMD now reports the iOS screening flow in real time, per its May 2026 release note, so your code can decide whether to speak, wait or move on.

What to do with each verdict

  • Human: connect the agent at once. Every extra moment counts against the two seconds.
  • Machine: hang up and move to the next lead, or wait for the beep and leave a message.
  • Not sure: treat it as a person. A wrongly dropped person is worse than an agent hearing a greeting.
  • Fax or silence: mark the number and stop dialing it.
  • Record the verdict on the call, so you can measure how often agents still hear machines.

Open-source AMD: Asterisk's AMD application

Asterisk, the open-source PBX that VICIdial and many self-hosted dialers run on, ships an AMD dialplan application that "attempts to detect answering machines at the beginning of outbound calls". It sets AMDSTATUS to MACHINE, HUMAN, NOTSURE or HANGUP, and AMDCAUSE to the measurement that decided it, such as LONGGREETING, MAXWORDS, INITIALSILENCE or TOOLONG.

It works from timings you tune: the longest initial silence, the longest greeting, the silence after a greeting, the total analysis time, and the words counted in a greeting. Defaults live in amd.conf. Tuning is a trade: a shorter greeting limit catches more machines and drops more people who say a long hello.

How DialerSeat for Developers handles it

Answering-machine detection runs on every mode except preview. On a machine, the agent is released straight away and the next lead comes up, so voicemail, no answer and busy never reach the agent. The verdict arrives on the call.answered webhook as pending while it is still listening, and as the final result on call.ended. In the sandbox, a test number ending in 7 answers as a machine, so you can build the machine path without placing a call.

Related: build a power dialer on Twilio, VICIdial API, call disposition codes list and dial modes in the docs.

Sources


More: the developer FAQ, the comparisons, Salesforce Open CTI retirement: what it means, Webhook signature verification failed? Find the cause, Do-not-call API: what the national registry offers, Moving from VICIdial's API to an embedded dialer, A click-to-call button in your CRM, Your own UI on the dialer, with DialerSeat.connect, A live status board for managers, or the quickstart, free in sandbox mode.