Published · Updated
When an AI hands a case to your support team, the customer still needs someone to finish it. Decide who will take the next step, what context they need and when the customer can expect a response. Creating a ticket starts that transfer; it does not prove anyone has accepted it.
Design the waiting period as carefully as the escalation trigger.
The examples below come from Typewise conversations in 2026. They describe requirements and proposals; the operating rules are our recommendations.
Make acceptance visible
Record a handoff in the system your support team uses. Include the receiving queue, acceptance deadline, current status and eventual owner. Until someone accepts it, show it as waiting rather than assigned work in progress.
Tell the customer what has actually happened. "I've created a request for our support team" is different from "A colleague is working on it." Give a reply time only if the team can meet it.
Decide who watches unaccepted requests. When the deadline passes, route them to a backup or supervisor. Track time to acceptance separately from time to resolution, so a queue of untouched cases cannot disappear inside an average response time.
Say what happens outside staffed hours
In a workshop, one of our customers in retail subscriptions asked what would happen when someone used the AI outside opening hours and then needed a person. The requested behavior was specific: explain that the team was unavailable, create a ticket and promise an email on the next working day. This was a requested design, not evidence that it had been deployed.
For your own service, choose the response per request type. An informational question might continue with AI. A request needing human judgment might wait in the normal queue. An action that cannot safely stop halfway may need to wait until staff are available.
Make the wait clear before the customer spends time on a process that cannot finish. Name the team responsible when service resumes, including a backup for absences.
Keep the case open while work is pending
A customer saying "thanks" should not close an unresolved internal task. Nor should a new question erase the original request. Test both situations and check that the pending work remains visible.
Action timeouts need particular care. If the AI requested a refund but received no confirmation, the outcome is unknown. It may have succeeded.
Check the refund system using the original transaction identity before retrying, and send the case to a person if the status cannot be established. Otherwise a retry could create a duplicate refund.
The permissions guide covers the checks before an action is allowed. The handoff must carry any unresolved action and its identity afterward.
Count a partial human step as human work
In a partial handoff, AI has completed an identifiable useful part and a person finishes the remaining work. In a full handoff, AI could not complete a useful part of the service request, so a person takes over the substantive work. Passing along context or lookup results alone does not establish partial resolution. Record which happened and what the person still had to do. For reporting, both stay in the original AI-entry group; transferring the case does not remove it from the denominator.
A travel company evaluating Typewise proposed an interim reservation workflow: the AI would collect details, a colleague would perform a step in a system that was not yet connected, and the result would return to the conversation. This was a proposal, not a completed pilot result. The engineering lead also distinguished reservation questions from making a reservation, where the company preferred its controlled app experience.
If you use a partial handoff, specify what the person must do and how the result returns. Include an acceptance deadline and an escalation path. Do not call the case fully automated because the AI wrote the final message; record the human time.
Sometimes the right answer is to direct the customer into the existing booking or account workflow. A chat conversation should not bypass safeguards built into that experience.
Send the context the next person needs
Attach the customer's request, verification state, relevant lookups, actions attempted and their confirmed or unknown outcomes. State what remains unresolved. Keep the original case identity when a conversation moves between systems, and apply the same access and retention rules to attached information.
Before launch, run a case through an after-hours handoff, a missed acceptance deadline and an unconfirmed action. Verify the receiving person can finish the work without asking the customer to start again. Use those cases in your go-live checks, and report partial handoffs separately in your resolution metrics.

