Fast / Slow Path: response, deeper work and handoff
Not every turn needs the same depth of processing. Interaction signals guide escalation and define when to hand over.
Begin with an ordinary response
Fast / Slow Path describes different processing depths. Ordinary interactions take a normal response path. Persistent dissatisfaction, prior negative feedback and repeated content can trigger escalation. These are routing strategies, not latency guarantees.
Increase support in stages
The current dialogue router has four tiers. T0 uses ordinary settings. T1 adds recovery guidance with the same model. T2 increases reasoning, tools, search and retrieval resources. T3 creates a human-escalation record and responds with a handoff message.
The system can adjust its approach within a conversation without sending every request through the heaviest process. Creating an escalation record must still be evaluated together with notification delivery, review and follow-up.
Distinguish different kinds of failure
A poor conversation, a learning difficulty and a document-recognition failure are different problems. Dialogue escalation is not a complete learning-difficulty detector or an OCR repair pipeline. Explicit triggers, outcomes and human responsibilities make the behavior traceable.