> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.simz.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.simz.com/_mcp/server.

# Answer Machine Detection

> How SimZ avoids spending AI time and call credits on voicemail, answering machines, and fax lines.

When an outbound call is picked up by a voicemail box, answering machine, or fax line instead of a person, there's no value in letting the AI agent keep talking to it. SimZ uses a two-layer detection approach to recognize this quickly and end the call, so you aren't billed for AI time or credits spent on a recording. Detection is intentionally conservative — SimZ would rather stay on a real call a little longer than risk hanging up on an actual person.

## Layer 1: Carrier-level detection

SimZ uses Twilio's Answering Machine Detection (AMD) on outbound calls. Twilio analyzes how the call is answered and reports a result back to SimZ in real time.

| Twilio result                                                        | SimZ behavior                                                      |
| -------------------------------------------------------------------- | ------------------------------------------------------------------ |
| Machine, voicemail, fax, or answering machine (confidently detected) | Call ends early.                                                   |
| Human                                                                | Call continues normally.                                           |
| Unknown / inconclusive                                               | Call continues, so a real person is never disconnected by mistake. |

## Layer 2: Transcript-based detection

Carrier-level detection isn't perfect — it can occasionally miss a voicemail, especially when the greeting starts unusually fast. As a safety net, SimZ also checks the earliest finalized transcript of the call for phrasing strongly associated with voicemail greetings.

If a clear, unambiguous voicemail phrase shows up early in the call, SimZ ends the call rather than let the agent continue talking to a machine. Examples of strong signals include:

* "please leave a message"
* "after the tone"
* "after the beep"
* "mailbox is full"
* "the person you are trying to reach is not available"

Weaker signals — generic business greetings, IVR menu prompts, or ambiguous phrasing — are not treated as reliable enough to end a call on their own. SimZ logs these for visibility but stays on the line, because ending a live call by mistake is far more costly than an occasional missed voicemail. This second layer only runs briefly at the start of a call and stands down as soon as there's a clear signal that a real person is speaking.

## Billing impact

Detected voicemails and answering machines are billed based on how long the call ran before detection:

| Call duration when detected as voicemail/machine  | Billing          |
| ------------------------------------------------- | ---------------- |
| Less than 5 seconds                               | Not billed (\$0) |
| 5 seconds or longer (including exactly 5 seconds) | Billed normally  |

This rule applies the same way whether the call was ended by Twilio's carrier-level detection or by SimZ's transcript-based safety net — you're not charged twice for the same protection working at two layers.

## Identifying machine calls in webhooks

Both webhook events report machine-answered calls, each in its own way.

| Event                  | Field        | Value for a machine-answered call                                                                                           |
| ---------------------- | ------------ | --------------------------------------------------------------------------------------------------------------------------- |
| `call.completed`       | `status`     | `AMD Terminated`                                                                                                            |
| `call.completed`       | `amd_result` | The detection result — for example `machine_start` from the carrier layer, or `transcript_guard` from the transcript layer. |
| `call.audit.completed` | `status`     | `answer_machine`                                                                                                            |

On `call.audit.completed`, the classification follows the detection result itself, so a machine-answered call is reported as `answer_machine` no matter how little of the greeting was captured before SimZ hung up.

See [Webhook Events](/webhook-events) for the full payloads and the complete set of values each `status` field can take.