Build a fallback ladder instead of one dead end

Failure moment A user asks to move a Paris trip because a passport is delayed. The bot is unsure whether this is a date change, cancellation, or exception request. The user has a real constraint; a generic fallback wastes the moment. Fallback ladder Repair -> Narrow -> Escalate Treat misunderstanding as a designed path. First expose likely interpretations, then constrain the task, then transfer context if the bot cannot resolve it. Sorry, rephrase Low effort, high user burden. The user always has a next move. Fallbacks should reduce ambiguity or transfer ownership; they should never ask the user to start…

Sign up free — one personalized lesson every day, matched to your role and goals.

Already have an account? Sign in