A human handoff works when the person taking over understands the request, knows what has already happened, and knows what they can decide. The handoff needs to be designed as a stage of service, with a destination and continuity.
Define when a person needs to participate
List the reasons for handoff with the team providing service. Distinguish a decision reserved for a person, a request outside the scope, an explicit request for human assistance, and a failure that prevents continuation. Different reasons may require different destinations. A commercial exception, for example, should not go to the same queue as a technical problem just because both need intervention.
Write down what the agent can do while handing off: confirm the request, gather available information, or explain the next stage. Avoid asking for new data without a purpose. When there is urgency or a specific operational rule, the path must be defined by those responsible for that process; this guide does not establish care protocols or specialized decisions.
Prepare a summary that allows the work to continue
The summary should answer five questions: what the person requested, why the handoff happened, what information was confirmed, what has already been tried, and what remains pending. When relevant, include a reference to the request or the system record. Preserve the distinction between what the person reported and what was confirmed by a source.
Review the material with whoever will receive it. The full history can remain available, but the person should not need to read all of it to find the pending issue. Include only the context necessary for the task and respect each team's access permissions. A long summary with irrelevant information can also delay service.
Agree on the destination, responsibility, and waiting
Define the receiving queue or team and how it becomes aware that work is waiting. Handing off, taking over, and resolving are different moments. The transfer record does not confirm that someone is already handling the request. Agree on who monitors unassigned items and what happens outside the team's availability hours.
The message to the user should reflect that situation. If the request is waiting, explain the next stage without promising an immediate response the operation cannot provide. Also define how to handle channel changes and repeat contact so two people do not work on the same request without realizing it, or so the interaction does not disappear between queues.
Record completion and use the feedback
On completion, the team needs to record what was decided, what action took place, and what still depends on another party. When the interaction returns to AI, determine which context should accompany it and which decisions have already been made. The agent should not restart questions the person just resolved or undo a decision without justification.
Review recurring reasons for handoff. Some indicate an appropriate limit to automation; others reveal missing information, integration failures, or a confusing design. Do not use a reduction in human handoffs as an isolated goal. The desired outcome is for the right person to take over when necessary and be able to continue handling the request.
Illustrative example · no customer data
Commercial terms outside the rules
Illustrative example: a person receives a proposal and requests terms the agent cannot grant. The summary for the team states the proposal presented, the terms requested, the data already confirmed, and that no exception has been approved. The reason for the handoff is a commercial decision, not a technical failure.
The conversation enters the responsible queue. When a salesperson takes over, they record the decision and continue from the pending point. If the team is unavailable, the person receives an explanation consistent with the wait. Testing the flow checks all three moments: request handed off, interaction taken over, and decision recorded.
When the approach needs to change
If there is no integrated queue, agree on a temporary procedure with a responsible person and a way to check it. If the person requests human assistance before data collection is complete, preserve what is already available and hand off according to the agreed scope. If the reason is uncertain, include that uncertainty in the summary instead of inventing a classification.
A point to watch: Handing off the conversation without saying why it needs a person or without a receiving team.
The worksheet is ready to move forward when…
- Each reason for handoff has a destination and a responsible person.
- The team can continue using the summary and available references.
- Handling is defined for waiting, completion, and any return to AI.
Complete the guide with the team that receives the conversations. Then walk through the example in the human handoffs environment and check whether the necessary information is visible.
Your worksheet
Complete it with your team.
Record what you know and what still needs confirmation. Answers stay in memory and are not submitted.