Bring your own turn detection
Keep your existing turn detection and drive Flux STT turn endings yourself with eot_threshold and ForceEndTurn.
Deepgram Flux STT detects the end of a turn natively, and for most voice agents that’s the right default. But if you’ve already invested in a turn detection stack — a VAD, an endpointing model, push-to-talk, or your own detector — you can keep it and adopt Flux STT for transcription without ripping out that logic. This guide shows the recipe for taking full ownership of turn endings.
The recipe
Two settings put you in control:
- Set
eot_thresholdto1.0. This suppresses Flux STT’s naturalEndOfTurnevents — the model won’t end a turn on its own confidence. - Leave
eager_eot_thresholdunset. Eager end-of-turn is off by default; keep it off so noEagerEndOfTurnevents fire.
Then send a ForceEndTurn message whenever your own detector decides the turn is over. Flux STT ends the turn and emits an EndOfTurn with "trigger": "manual".
How it works
- Send audio as usual. Flux STT transcribes continuously and emits
StartOfTurnandUpdateevents. Witheot_threshold=1.0, it never emitsEndOfTurnon its own. - Your detector decides the turn is over. A push-to-talk release, a VAD silence event, a DTMF tone — whatever signal you rely on.
- Send
ForceEndTurn. Flux STT ends the turn and emitsEndOfTurnwith the transcript decoded so far and"trigger": "manual". - Dispatch the transcript. Treat the
EndOfTurntranscript as final and hand it to your agent.turn_indexincrements and Flux STT is ready for the next turn.
What still ends a turn
With eot_threshold=1.0, three things can still end a turn:
ForceEndTurn— your explicit signal ("trigger": "manual").eot_timeout_ms— a safety net. If this much silence passes, Flux STT force-ends the turn with"trigger": "timeout". Set it high enough that it only fires when your own detection has failed. The maximum is60000(60 seconds).CloseStream— closes the connection without finalizing the active turn. NoEndOfTurnis emitted for it; treat the most recentUpdateas the last transcript for that turn.
Keep eot_timeout_ms as a backstop, not a primary mechanism. If it fires often, your external detection is missing turn endings. Tune your detector rather than lowering the timeout.
Example
This loop wires an external detector to Flux STT. When your detector fires, it sends a ForceEndTurn; Flux STT replies with an EndOfTurn you treat as final.
When to use this
- You already have turn detection you trust and don’t want to migrate off it to adopt Flux STT.
- Your turn-end signal is external and definitive — push-to-talk, DTMF, a UI action.
- You’re migrating from Nova-3 and want to keep your existing endpointing while gaining Flux STT transcript quality. See Migrating from Nova-3 to Flux STT.
If you don’t already have a turn detection stack, prefer Flux STT’s native detection — it’s purpose-built for conversational turn-taking. See End-of-turn detection parameters.
Related resources
- Force End Turn - The control message reference
- End-of-turn detection parameters - Tune
eot_threshold,eager_eot_threshold, andeot_timeout_ms - Understanding the Flux STT state machine - Turn events and state transitions
- Migrating from Nova-3 to Flux STT - Migration guide