Endpointing / Turn Detection
Endpointing identifies a boundary in incoming speech at which a system may finalize an utterance or start responding. End-of-turn detection asks whether the speaker has actually yielded the conversational turn. Implementations sometimes use these labels interchangeably, but a pause or finalized transcript segment does not necessarily mean the person has finished their thought. Voice activity detection identifies speech activity; turn-taking requires an additional decision about conversational timing.
Origin and context
Turn-taking is a longstanding speech and dialogue problem. The 2022 Voice Activity Projection work trained models to predict future voice activity and evaluated turn shifts and backchannels. LiveKit later described adding transcript semantics to endpoint decisions, and in 2026 introduced an audio-based detector using acoustic and semantic cues. These are different approaches to the same interaction problem, not evidence that a single silence threshold works everywhere.
Why it matters
An early boundary makes the agent interrupt the speaker; a late one creates avoidable silence. The effect is especially noticeable when a user hesitates, corrects a number or pauses within a long request. Better timing can improve a voice interface without changing the language model. It should be considered together with response cancellation and interruption handling, while remaining a separate decision from what action the agent is authorized to perform.
Example
In an illustrative booking conversation, the user says “move it to Thursday” and pauses before adding “after three.” A silence-only policy may act on the incomplete request. A test set should include this pause, genuinely finished requests, acknowledgments and overlapping speech. Compare premature responses and delay after the actual turn end, then verify that any interruption stops obsolete speech and that the requested booking is confirmed before commitment.
Maturity and evidence
Maturity 3 reflects established turn-taking research and working voice-agent implementations. The underlying competence is stable even though detector architectures and APIs change. A vendor result should be read with its languages, audio conditions and evaluation protocol; it does not establish that turn detection is solved for every deployment.
Limits and open questions
Noise, accents, hesitation and multi-speaker audio can shift the trade-off between delay and false boundaries. Semantic cues may help but can depend on transcription quality; audio models have their own coverage limits. Evaluate the target users and channels. A correct endpoint neither guarantees correct recognition nor replaces confirmation of a consequential action.
Related terms
References
- Voice Activity Projection: Self-supervised Learning of Turn-taking EventsEkstedt and Skantze / KTH · 2022-05-19 · class A
- Using a transformer to improve end of turn detectionLiveKit · 2024-12-20 · class B
- Solving end-of-turn detection: LiveKit Turn Detector v1.0LiveKit · 2026-06-17 · class B
Last updated: 2026-10-23
This term is also covered in the Skills Atlas as voice agents skill.
This term is also covered in the Skills Atlas as livekit skill.
This term is also covered in the Skills Atlas as speech recognition skill.
Referencing this analysis in documentation, research, or an engineering write-up? Copy a formatted link or citation below:
Show citation text & canonical URL
[Endpointing / Turn Detection — AI Glossary — Skills Intelligence](https://www.skillsintelligence.tools/glossary/term/endpointing-turn-detection)Skills Intelligence. (2026). Endpointing / Turn Detection — AI Glossary. Skills Intelligence AI Glossary. Retrieved from https://www.skillsintelligence.tools/glossary/term/endpointing-turn-detection