When a forwarded call is picked up by the target's carrier voicemail, the carrier reports it as a completed call. Machine detection runs on the dialled leg and turns that verdict into 'missed — it rang through to a personal voicemail, so no one on the team heard it', which then drives the callback task and the text-back.
Also called: call said answered but nobody answered · went to my cell's voicemail · lead left a message on my personal phone
- 1machineDetection is attached to each <Number> target, with its own asynchronous callback
- 2The AMD verdict lands seconds after answer, before the after-dial result which fires at hangup
- 3upsertCall is MONOTONIC: a 'machine' verdict is definitive and a later 'completed' can never walk it back to answered
- 4machineDetection runs entirely on the dialed leg — the caller never waits for it and hears nothing different
- 5No detection is applied to browser clients
A call forwarded to a rep's cell and picked up by that cell's carrier voicemail comes back from the network as completed — indistinguishable from a human answering. So a lead worth $30,000 to $250,000 would land in a personal mailbox nobody checks while the system reported the call as answered, and nothing chased it. Answering-machine detection on the forwarded leg now catches those and records them as missed, which is what puts them into the rescue chain.
- Carrier voicemail counted as a successful answer
- Leads lost into personal mailboxes with the CRM reporting success
- Late webhook data overwriting a definite miss
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →