# The Voice Failure Atlas

> What voice-agent builders are hitting, across every platform, with a link to who reported it and a status re-checked daily.

Subscribe to the machine surface rather than scraping these pages:
- [feed.json](https://hotato.dev/atlas/feed.json): every entry, its reports, its status history with evidence links, and whether hotato measures it.
- [feed.schema.json](https://hotato.dev/atlas/schema/feed.schema.json): the documented, stable schema (hotato.atlas-feed.v1).
- [feed.atom](https://hotato.dev/atlas/feed.atom): the same entries as Atom 1.0.

## How to read an entry

- `statement` is one plain-English sentence describing what happens to the caller.
- `status` is one of open, acknowledged, fixed, stale, withdrawn. It changes only when a daily re-check stores an evidence link, quote and date; `status_history` carries that evidence.
- `report_count` counts independent public reports; each carries the reporter's public handle, the canonical link, and a quote of at most 30 words.
- `hotato_coverage.command` is a command you can run yourself, or an empty string when no shipped hotato command measures that mode.

## Terms

Link-first: quote at most 30 words and link the original. Do not use the handles here to build an outreach list. Removal requests: atlas-remove@hotato.dev, honored within 24 hours.

## Entries

- [When the caller interrupts the agent mid-speech, the system's interrupt handling fails to cleanly tear down the in-progress turn, corrupting the conversation state.](https://hotato.dev/atlas/barge-in-teardown-race/): acknowledged, 7 report(s), measured by `hotato autopsy ./call.wav`
- [The agent's speech synthesis silently produces no audio even though it logs the turn as spoken, and the safeguard meant to detect and recover from this never triggers, leaving the caller in permanent silence.](https://hotato.dev/atlas/silent-tts-failover-deadlock/): acknowledged, 3 report(s), no hotato command published
- [End-of-turn detection fires at the wrong moment, so the agent either answers before the caller has finished or waits after they have.](https://hotato.dev/atlas/endpoint-misdetection/): acknowledged, 7 report(s), no hotato command published
- [The system fails to detect the caller's speech because voice-activity detection misjudges frame windowing and retained internal state, so the caller appears silent when they are talking.](https://hotato.dev/atlas/vad-endpoint-misdetection/): open, 2 report(s), no hotato command published
- [After the system re-prompts a silent caller, a turn-completion gate that only resets when the caller speaks treats the caller's reply as already answered and silently discards the agent's response.](https://hotato.dev/atlas/idle-reprompt-turn-latch-response-drop/): open, 1 report(s), no hotato command published
- [When the agent calls a tool while still speaking, the system marks buffered audio as fully played once generation finishes, cutting the agent's speech off mid-word and sometimes stalling the call.](https://hotato.dev/atlas/tool-call-mid-utterance-audio-truncation/): open, 1 report(s), no hotato command published
- [A delayed decision about whether an earlier overlap counted as an interruption gets wrongly applied to a later, unrelated moment, cutting the agent off for speech that was never actually judged an interruption.](https://hotato.dev/atlas/async-interruption-response-misattribution/): open, 1 report(s), measured by `hotato autopsy ./call.wav`
- [When the agent's turn is split into multiple speech segments, such as around a tool call, a later segment resets interruption tracking so the caller's still-ongoing interruption is silently ignored.](https://hotato.dev/atlas/segmented-turn-interruption-disarm/): open, 1 report(s), no hotato command published
- [The agent starts speaking while the caller still holds the floor, cutting the caller off mid-utterance.](https://hotato.dev/atlas/agent-interrupts-caller/): open, 1 report(s), measured by `hotato autopsy ./call.wav`
- [A queue-ordering race in assembling the agent's own spoken output into conversation history drops the turn's final word from the stored record, even on a normal turn with no interruption, though the caller still hears the full sentence.](https://hotato.dev/atlas/tts-word-drop-context-race/): fixed, 1 report(s), no hotato command published
- [The caller finishes and the line goes silent for seconds before the agent responds, with no audible acknowledgement in between.](https://hotato.dev/atlas/dead-air-after-caller/): open, 1 report(s), measured by `hotato autopsy ./call.wav`
- [A speech-to-text result that finalizes just after the system has already ended and flushed the caller's turn is still processed, racing against the turn boundary and risking corrupted turn state.](https://hotato.dev/atlas/late-stt-final-race-after-turn-flush/): open, 1 report(s), no hotato command published
- [After switching to neural voice-activity detection, the system takes an unusually long time to respond when the caller gives a short one-word reply.](https://hotato.dev/atlas/endpointing-latency-short-reply/): open, 2 report(s), measured by `hotato autopsy ./call.wav`
- [A tool call the agent decided on before being interrupted still executes afterward, so an action like hanging up can fire even though the caller is still on the line.](https://hotato.dev/atlas/tool-fire-after-cancel/): acknowledged, 1 report(s), no hotato command published
- [On outbound calls, the answering-machine-detection timer starts before the callee has actually answered, so ring or early media triggers a false timeout that the system wrongly treats as a voicemail greeting.](https://hotato.dev/atlas/amd-premature-timeout-before-answer/): open, 1 report(s), no hotato command published
- [The agent process is dispatched to an inbound call so many seconds after it arrives that the caller has already hung up before the agent joins.](https://hotato.dev/atlas/agent-dispatch-latency-before-connect/): open, 1 report(s), no hotato command published
- [Voice-activity detection registers that the caller is speaking, but the speech-to-text stage fails to produce any transcript even though the same audio is clearly audible in a separate recording of the call.](https://hotato.dev/atlas/vad-fires-but-stt-yields-no-transcript/): fixed, 1 report(s), no hotato command published
- [When the agent's response takes too long to generate, the telephony layer reads the resulting silence as call inactivity and tears down the call itself, then misreports that the caller hung up.](https://hotato.dev/atlas/silence-timeout-teardown-during-processing-gap/): open, 1 report(s), no hotato command published
- [Voice-activity detection treats non-speech or a backchannel as a floor claim, so the agent yields to something that was not a turn.](https://hotato.dev/atlas/vad-false-trigger/): open, 1 report(s), no hotato command published
- [The agent's own synthesized speech bleeds into the audio input and voice-activity detection mistakes it for the caller starting to talk, triggering a false interruption.](https://hotato.dev/atlas/self-echo-vad-false-trigger/): open, 1 report(s), measured by `hotato trust --stereo ./call.wav`
- [After the agent completes one or more tool calls within a turn, its spoken response never gets synthesized, leaving the caller in silence.](https://hotato.dev/atlas/tool-call-audio-output-silence/): open, 1 report(s), no hotato command published
- [The system stops listening for the voicemail beep tone as soon as it detects silence after the greeting, so a beep arriving just after is missed and the tone-triggered action never fires.](https://hotato.dev/atlas/amd-tone-detection-premature-teardown/): open, 1 report(s), no hotato command published
- [The system's answering-machine-vs-human classification only comes back after the call has already been answered and engaged, so the agent cannot act on whether it reached a person or a machine in time.](https://hotato.dev/atlas/amd-result-arrives-after-call-answered/): open, 1 report(s), no hotato command published

data as of 2026-07-29T05:42:30Z