Preview Audrey 0.7: speech recognition for real calls
Explainer · 13 Oct 2026

What a turn detector decides at every pause.

Finished, or just pausing? The one decision our models make, the two ways to get it wrong, and where it sits in a voice agent.

The decision

Our models do one job: at every pause, they decide whether the speaker has finished or is just pausing.

Get this wrong one way and the agent cuts people off. Get it wrong the other way and it waits too long to reply. Both feel broken to the person on the call, so a detector has to be judged on both at once.

One call, step by step

  1. CallerI'd like to move my appointment toPause. The detector keeps listening.
  2. CallerThursday afternoon, if you have anything.Finished. End of turn, the agent replies.
  3. AgentThursday at two is open. Shall IThe caller starts talking over the agent.
  4. CallerTwo is perfect.Interruption. The agent stops.

An example, not model output. The first pause is mid-sentence, so the detector holds. The second is the end of the turn, so the agent can reply. When the caller cuts in, the detector marks an interruption and the agent stops speaking.

Where it sits

A voice agent has four jobs: hear the words, know when the speaker is done, decide what to say, and speak. Our models do the second one. They work with any speech recognizer, any LLM and any voice.

How we report it

Three numbers matter together: recall, the share of true events the detector catches; false-positive rate, how often it fires when it should not; and latency, how long after the event it decides. We quote latency as the median and show the p10 and p90 where we have them.

Our current numbers are in the TurnBench post and on the turn-1 page.