“A person can take over” sounds reassuring. But it leaves important questions unanswered: which person, with what information, through which channel, and after what delay?
A good hand-off is designed as carefully as the automated answer. It is not a fallback message added at the end of a project.
Define the trigger
Some requests should move to a person because they involve a sensitive decision. Others need review because information is missing, sources disagree or an integration has failed.
Write those triggers down. Examples might include a complaint, a request outside the approved policy or an action that requires authorisation. Do not rely on the assistant to invent its own boundary in every conversation.
Give the person context
A hand-off should explain what the user asked, what information is available, what remains unclear and what action is requested. It should distinguish the user's words from the assistant's interpretation.
Avoid a long transcript when a concise, checked summary is enough. Do not forward sensitive information simply because it appeared in a message. The receiving person should have appropriate access and a reason to receive it.
Be honest with the user
There is a difference between preparing a request and successfully submitting it. There is another difference between submission and a person accepting responsibility for it.
Use words that reflect the actual state. “Your request has been received” is appropriate after the system confirms receipt. “Someone is handling this now” needs evidence that a person really is handling it.
Design for failure
Notifications can fail. A team member can be unavailable. A queue can fill up. Decide what happens next: a retry, an alternative owner, a visible warning or a return to the previous process.
The aim is not to claim that nothing will ever go wrong. It is to make problems visible and give people a workable response.
In the demo studio, inspect the sample hand-off beside each conversation. Then consider what your own team would need to receive.
Try the related demo →