--- title: "When Flows Should Refuse a Query Instead of Guessing" description: "Copyable AI assistant escalation rules for a Flows concierge: refuse with no cited page, escalate to a person, and treat a sub-10% handoff rate as guessing." url: "https://articles.flowcrews.com/when-flows-should-refuse-a-query-instead-of-guessing" category: "Concierge" date_published: 2026-10-08 reading_time_minutes: 8 word_count: 1793 --- # When Flows Should Refuse a Query Instead of Guessing *A three-outcome card a cited-page concierge can follow: answer, refuse and log, or hand off.* ![When Flows Should Refuse a Query Instead of Guessing](https://pub-07fb5e4955ba485b822d6b388be96d9a.r2.dev/2e474d51-a072-472e-ab2f-1a43a8990566/when-flows-should-refuse-a-query-instead-of-guessing/hero-0515772e-74ba-423a-8694-715e40e56440.jpg) **TL;DR:** - Write escalation rules as if-then holds before launch; do not leave the model to decide when it should stop. - Use three outcomes: cite and answer, refuse and log, or hand off to a person. - Hard-refuse when there is no retrieved source, the question is off the product map, or the next step is irreversible, regulated, or a complaint. - Honor an explicit request for a human on the first ask, without another bot retry. - Treat a handoff rate meaningfully below 10% as likely guessing; several support guides treat roughly 15–25% as a healthy band. ## When an AI assistant should refuse a query instead of answering ## Refusing a query versus escalating it to a human ## How do you stop a grounded assistant from answering outside its scope? ## Honor a human request immediately—don't wait for a miss quota ## A healthy chatbot escalation rate, and when a low one is a red flag ## What context must travel with an AI-to-human handoff? ## What to log when the assistant refuses, and how to test the rules first ## Conclusion - Three outcomes — A cited-page Flows concierge should cite and answer, refuse and log, or hand off to a person, and should not guess when it has no source, the stakes are too high, or the reader asked for a human. - Can't, Won't, Shouldn't — Refuse and log a no-source or out-of-map ask; escalate on the first human request or repeated frustration; hard-escalate billing disputes, complaints, regulated issues, deletions, and permission changes. - Scope binding — Out-of-scope answers are stopped by tying the assistant to the two-job product map and citable pages, and by abstaining when passages are empty instead of inventing an answer. - Immediate honor — An explicit request for a person is handed off on the first ask, with no retry or miss quota, while a knowledge gap with nobody waiting stays a logged refusal rather than a fake ticket. - Escalation band — A healthy support escalation rate sits roughly in the mid-teens to mid-twenties; rates near zero often mean the assistant is guessing, and a clean refusal counts as a citation-safe success. - Packet, log, and test — Every refusal or handoff should carry the query, outcome, named trigger, citations or an explicit none, and the transcript, and the holds should be script-tested—including a persuasive override—before launch. Write those if-then holds into the workflow, bind them to the product map, and test the packet before the concierge answers live queries. ## Frequently Asked Questions ### When should a Flows concierge refuse instead of answering? Refuse when no retrieved page contains the answer, when the question sits outside the product map, or when the next step is irreversible, regulated, or a complaint. Hyperleap’s rule is to decline to guess rather than produce a fluent wrong answer, and to log the miss so it can become a brief or a page patch. ### What are the three outcomes an escalation card should allow? Cite and answer, refuse and log, or hand off to a person. A single handoff button hides the difference between a grounded answer, a knowledge-base gap, and a case a person must own. ### Should an explicit request for a human be retried by the assistant first? No. Hyperleap says an explicit request to speak with a human should be honored immediately, without the assistant attempting another resolution first. ### What escalation rate suggests the assistant is guessing? Hyperleap warns that a rate meaningfully below 10% can mean the AI is answering questions it should escalate. It treats 15–25% as a healthy range for many deployments. Measure transfer success, re-ask rate, and post-handoff resolution, not deflection alone. ### Why do policy-restricted topics need a hard rule? A model can sound confident while giving advice it should not give. Hyperleap separates policy-restricted topics—billing disputes, complaints, and regulated issues—from confidence tuning, and requires a hard always-escalate rule. ### What must travel with a handoff so the reader does not repeat themselves? Pass the transcript, the trigger, and any citations. IrisAgent reports that customers who have to repeat their issue rate the experience 30 to 40 points lower, and that a clean handoff with full context cuts handle time on transferred conversations by 40% to 60%. ## Sources - [https://hyperleap.ai/blog/chatbot-human-handoff-best-practices](https://hyperleap.ai/blog/chatbot-human-handoff-best-practices) - [https://hai.stanford.edu/ai-index/2026-ai-index-report/technical-performance](https://hai.stanford.edu/ai-index/2026-ai-index-report/technical-performance) - [https://genai.owasp.org/llmrisk/llm06-sensitive-information-disclosure/](https://genai.owasp.org/llmrisk/llm06-sensitive-information-disclosure/) - [https://www.eesel.ai/blog/how-to-handle-support-escalations-with-ai](https://www.eesel.ai/blog/how-to-handle-support-escalations-with-ai) - [https://irisagent.com/blog/what-is-ai-agent-handoff/](https://irisagent.com/blog/what-is-ai-agent-handoff/) - [https://aloware.com/blog/ai-to-human-handoff](https://aloware.com/blog/ai-to-human-handoff) - [https://www.userflow.com/blog/prevent-ai-agent-hallucinations-support](https://www.userflow.com/blog/prevent-ai-agent-hallucinations-support) - [https://ideaplan.io/metrics/human-escalation-rate](https://ideaplan.io/metrics/human-escalation-rate) - [https://stealthagents.com/research/ai-customer-service-human-handoff-statistics-2026](https://stealthagents.com/research/ai-customer-service-human-handoff-statistics-2026) - [https://www.usefini.com/guides/customer-service-escalation-management-ai](https://www.usefini.com/guides/customer-service-escalation-management-ai) - [https://owlish.bot/blog/ai-customer-support-hallucinations/](https://owlish.bot/blog/ai-customer-support-hallucinations/)