# When should an AI support response hand off to a person?

Canonical: https://trutool.co/community/customer-support-ai-handoff
Author: Sandeep (https://trutool.co/authors/sandeep)
Last modified: 2026-10-08T16:11:05.281Z

Hand off when the answer is unsupported, the user asks for a person, or the issue involves exceptions, sensitive information, or a consequential decision. Make the boundary explicit and pass the conversation context to the human reviewer.

## Quick answer
Hand off when the answer is unsupported, the user asks for a person, or the issue involves exceptions, sensitive information, or a consequential decision. Make the boundary explicit and pass the conversation context to the human reviewer.

## Define the allowed scope
List questions the system may answer and situations that always require escalation. Include account, billing, security, and policy exceptions as relevant.

## Test difficult requests
Use incomplete questions, frustrated users, conflicting knowledge, and requests outside scope. Check that the system admits uncertainty and escalates appropriately.

## Review the handoff
Confirm the human receives the history, relevant account context, and unresolved question. Track repeated failures and update the knowledge source.

## Before you decide
- Keep the escalation path easy to find.
- Assign an owner to maintain approved answers.
- Review outcomes, not only ticket deflection.

## Keep in mind
A confident unsupported answer can damage trust even if it reduces the number of human tickets.

## Useful tools
- [Intercom](https://trutool.co/tools/intercom): Customer support and service teams considering Intercom for this job: Customer support and AI service workflows.
- [Zendesk](https://trutool.co/tools/zendesk): Customer support and service teams considering Zendesk for this job: Support tickets and customer service.