Key takeaways
- AMD starts where call signalling stops. The network tells you a call was answered. Only the audio can suggest who or what answered it.
- Accuracy is the wrong first question. Two detectors can both score 92% while one drops ten times as many people. Ask for the false-machine rate instead.
- Background detection doesn’t remove the wait. It starts your call flow at once, but an agent held for the verdict still stays quiet until the verdict arrives.
- Phones now answer for people. iPhone, Pixel, and Truecaller screening can all put a spoken assistant in front of the person you called.
- India’s denominator differs. TRAI’s 2018 criterion measures abandoned calls against attempted calls, while the US and UK measure against live answers.
What does answering machine detection decide?
AMD answers one narrow question after a call connects: is this a person? Ringing, busy, and no-answer are different outcomes, and they arrive as call progress and hangup signals. A voicemail system looks like an ordinary answer to the network, so the detector has to work from sound. Result labels vary by product. Typical results cover a person, a machine, a fax, or an unknown answer, and some say how a greeting ended. Three common uses follow from that verdict:- Protect agent time. Connect only answered humans to a live agent.
- Protect AI spend. Keep a voice AI agent from talking to a recording.
- Deliver a message. Wait for the greeting to end, then leave a voicemail.
How does a detector tell a person from a machine?
Most detectors weigh a few signals in the opening seconds. People tend to say something short and wait for a reply. Recordings tend to keep talking because nothing is listening.
The last row matters for Indian traffic. A transcript-based check can only match phrases in languages its speech recognition handles. A timing rule ignores language, but it still assumes people everywhere greet at a similar length. Neither assumption should ship without a test on your own audience.
Why does a 92% accurate detector still fail?
Accuracy blends two different mistakes into one number, and those mistakes have very different costs.- False machine. A person is classified as a machine. You hang up on them or play them a recording.
- False human. A machine is classified as a person. An agent or AI talks to a recording until someone notices.
Does background detection remove the wait?
Only part of it. Detection needs audio from the answered call, which often takes a few seconds. Very short timeouts tend to hurt accuracy. The design choice is what the person hears during that time.- Blocking detection suits flows with no live conversation, because the branch is simple and nobody is waiting to talk.
- Background detection with an immediate greeting sounds fast, but it damages the sample. The person answers over the agent, and the classifier loses the “hello, then pause” shape it depends on.
- Background detection with a held agent is usually the right design for voice AI. You still pay for the verdict in seconds, so size the timers deliberately and add a fallback.
What changed when phones began answering for people?
Some “machines” are now assistants with a person behind them. That breaks the old assumption that a machine answer means nobody is there.
A screening prompt is long, continuous speech, so a duration rule tends to call it a machine. The person may join seconds later, which is why an automatic hang-up on that verdict can lose a real contact.
We found no reliable public figure for how many Indian calls reach voicemail or a screener. Don’t import a US voicemail rate into an Indian campaign plan. Measure it on a labelled sample, as described below.
How do you measure AMD on your own calls?
You can’t find false machines by reading AMD results alone. Ofcom made this point in 2010: the equipment can’t identify its own false positive as a call picked up by a live person. So you need to hear what happened after the verdict.- Keep the call open. Run a small test where a machine verdict doesn’t end the call, so the audio after the verdict still exists.
- Record lawfully. Follow your consent and retention duties. Compliant call recording pipelines covers the design.
- Label by listening. Mark each call as person, voicemail, screener, or network announcement, without looking at the verdict.
- Split the results. Report by country, operator, language, device group, and time of day where you can. Tuning on a handful of devices can mislead you once you deploy widely.
- Tune one timer at a time. Then repeat the test, because a change that saves people can let more machines through.
Which AMD setup fits your campaign?
Start from what should change when a machine answers. Sometimes nothing should, and then AMD only adds a wait and a way to fail.How do regulators treat AMD mistakes?
Regulators mostly don’t regulate the detector. They regulate what happens to the person who answered, and a false machine can count against you. Rules change often, so confirm the current text and take legal advice for your campaign.The denominator changes your result
Take 1,000 attempts that reach 300 live people, with a detector that drops 5% of them. That is 15 people, and nothing else goes wrong.- Against live answers, as in the US rule and Ofcom’s formula, the rate is 5%. That is above the US limit of 3%.
- Against attempted calls, as in TRAI’s 2018 criterion, the rate is 1.5%, which is below 3%.
India: three layers of text
The 2018 regulations. TCCCPR 2018 defines abandoned calls as above and tells access providers to report entities above 3% abandoned, or above 1% silent, over 24 hours. Read the definition of a silent call closely. TRAI means a very short call designed to prompt a callback. Ofcom means a call where the person gets no message. Dead air from a slow detector fits Ofcom’s meaning, not TRAI’s. The February 2025 amendment. The Second Amendment replaced regulation 4 with a duty to notify your originating access provider in writing, in advance, about auto dialler or robo-call use and its purpose. We found no amendment deleting the 2018 definition or the 3% criterion, but we also found no consolidated text. Treat their current force as a question for your provider or counsel. The September 2026 amendment. The Third Amendment defines an A2P call as one started by an application, software system, or automated platform without direct human dialling. Four points from it affect AMD users:- Declaration. Senders must declare A2P use and CLI ranges in advance, and undeclared calls count as unsolicited.
- Live agents don’t exempt you. TRAI considered excluding calls with a human agent and kept its definition, so a predictive dialler that connects agents appears to be in scope.
- Transactional calls count. TRAI says the rules apply to all A2P calls, not only commercial ones.
- A per-minute charge. TRAI’s press release describes a termination charge of up to ₹0.05 per minute between operators, with designated series exempt. Ask your provider how this reaches you. Minutes spent talking to a machine may matter more once it applies.
US: a two-second clock, under review
47 CFR 64.1200(a)(7) and the FTC’s 16 CFR 310.4(b)(1)(iv) both start the clock at the person’s completed greeting. A detector that waits for silence spends that time first.How Vobiz handles AMD
Vobiz machine detection is a set of parameters on the Make Call API, not a separate endpoint. It applies to outbound calls placed through that API.- Background results. Set
machine_detection_urland optionallymachine_detection_method, and Vobiz sends webhooks (callbacks) with the result. The payload includesMachine,IfMachine,CallUUID, and anEventofMachineDetection. - Reporting. A call ended by
machine_detection=hangupcloses with hangup cause9100, Machine Detected, which separates it from other outcomes in your data. - Greeting-end timing. In VobizXML,
<Wait>withsilencemoves on once a greeting stops, andbeepwaits for a voicemail beep. The two are mutually exclusive, and the docs describe both as best-effort, so pair them with a fallback. - AI agents. Tuning for AI voice agents gives balanced, high-accuracy, and low-latency starting profiles. It also gives the gating steps: hold the agent, branch on
Machine, and treat a late callback as a human. - Working example. The LiveKit AMD agent classifies the pickup before the conversation starts, and leaves a recorded message on voicemail.
- Audio for agents. Audio streams and WebSocket streaming connect call audio to your agent. Vobiz also has Vapi and LiveKit integration guides.
- Campaign sizing. Model channel needs in the CPS and concurrency calculator. The outbound campaign guide covers running at volume.
Frequently asked questions
What does answering machine detection do?
What does answering machine detection do?
It listens to the first seconds of an answered outbound call and judges whether a person or a machine picked up. Your application then acts on that verdict. It might connect an agent, start an AI agent, leave a message, or end the call.
How accurate is AMD?
How accurate is AMD?
Published figures vary widely, but vendors measure them differently and most are self-reported. A single accuracy number also hides which mistakes occur. Measure how many live people your setup wrongly marks as machines, using your own destinations and call types.
What is an AMD false positive?
What is an AMD false positive?
It usually means a live person was classified as a machine. The call may be dropped or sent a recording, so this is normally the costliest error. The opposite error, often called a false negative, sends a machine to your agent or AI.
Does AMD add delay to a call?
Does AMD add delay to a call?
Yes. The detector needs audio before it can decide, which often takes a few seconds. Running detection in the background lets your call flow start immediately, but an agent held for the verdict still waits.
Can AMD recognise call screening assistants?
Can AMD recognise call screening assistants?
Sometimes, but a duration rule can read a spoken screening prompt as a voicemail greeting, even though a person may join moments later. Test screened calls separately, and treat a machine verdict on them as uncertain until you have measured it.
Is answering machine detection allowed in India?
Is answering machine detection allowed in India?
We found no TRAI rule that bans AMD itself. The rules govern the calls around it, including advance notice of auto dialler use and limits on abandoned calls. TRAI’s September 2026 amendment adds an A2P declaration. Confirm the current text and take legal advice for your campaign.
Further reading on Vobiz
- Scaling outbound: automated calling and AMD · What is a voice API? · What is a call leg?
- Machine detection reference · Make Call API ·
<Wait>reference - Automated outbound calling · Campaigns · DLT registration
Sources
Regulators and law- TRAI, Telecom Commercial Communications Customer Preference Regulations, 2018, July 2018.
- TRAI, Second Amendment Regulations, 2025, February 2025.
- TRAI, Third Amendment Regulations, 2026, 18 September 2026.
- TRAI, Press release 119/2026, 18 September 2026.
- Cornell Legal Information Institute, 47 CFR 64.1200 and 16 CFR 310.4, read November 2026.
- Federal Register, FCC proposed rules on call branding and TCPA provisions, 5 December 2025.
- Ofcom, Persistent misuse: statement of general policy, December 2016, applying from 1 March 2017.
- Ofcom, Refresher messaging on silent and abandoned calls, January 2026.
- Ofcom, Revised statement of policy on persistent misuse, September 2008. Historical.
- Ofcom, Tackling abandoned and silent calls: statement, October 2010. Historical.
- Asterisk, AMD dialplan application.
- Apple, iOS feature availability.
- Google, Screen your calls before you answer them.
- GSMArena, Truecaller Assistant launches in India for Android users, July 2023.
- Business Today, Truecaller launches free AI-powered voicemail for Android, December 2025.
- Kelley Drye, FCC includes proposals to roll back several TCPA rules, November 2025.
Build outbound on Vobiz
Provision a number and test machine detection on your own outbound calls.