Platform
Dead end
A dead end is a point where a conversation has no valid transition, action, resolution, or recovery path.
A dead end is a point where a conversation has no valid transition, action, resolution, or recovery path.
What Dead end means
A dead end is a point where a conversation has no valid transition, action, resolution, or recovery path.
Dead ends can appear when an answer does not match expected choices, an integration fails, required data is unavailable, or a branch was never connected. The caller may hear repetition, silence, an irrelevant response, or an abrupt ending.
How it works
Testing and conversation logs reveal nodes where progress stops or loops. Designers add clarification, fallbackFallbackA fallback is a safe alternate path used when input is unexpected, a tool fails, or the agent cannot complete the intended step confidently., human handoffHuman handoffHuman handoff transfers a conversation, context, and next action from an automated agent to a person., alternate actions, or a graceful close. Monitoring should distinguish true completion from abandonment caused by missing logic.
Practical use cases
Finding a branch with no next node
Recovering from an unavailable scheduling integration
Handling an unsupported request without trapping the caller
Every node should answer three questions: what counts as success, what can fail, and where does the conversation go next. If one is missing, the flow is unfinished.
Frequently asked questions
Why does Dead end matter?
Every node should answer three questions: what counts as success, what can fail, and where does the conversation go next. If one is missing, the flow is unfinished.
How can teams detect dead ends before launch?
Run structured tests for invalid answers, silence, interruptions, contradictory details, unavailable tools, closed destinations, and requests that fall outside the happy pathHappy pathThe happy path is the ideal route where expected inputs are available and the conversation reaches its intended outcome without detours..
Source: Thoughtly’s testing documentation.
Related concepts: fallback, happy path, conversation flowConversation flowA conversation flow is the designed path through greeting, intent capture, qualification, actions, routing, fallback, and closing., human handoff.