Human handoff: when the assistant must step aside
Definition
Human handoff is the mechanism by which an assistant stops answering and passes the request to a person. Far from an admission of failure, it is a central setting: an assistant unable to hand off compensates for ignorance by producing a plausible but wrong answer.The most common misreading
Many projects set out to reduce handoffs to a minimum, as if every transfer to a human were a failure. That gets the problem backwards.
An assistant has only two ways to handle a question beyond what it knows: hand off, or produce a plausible answer. The second is always available and cheaper in the short term. That is why an artificially low handoff rate should worry you rather than reassure you.
The four moments to step aside
- Information is missing: the question falls outside the documented scope and no reliable answer is possible.
- The stakes are high: money, a contract, health, a legal deadline. Doubt is not allowed.
- The person asks for it: a request to honour immediately, with no discouraging step in between.
- The tone changed: irritation, insistence, the same question repeated. Mechanically pressing on always makes it worse.
These four rules are written before go-live. Written after an incident, they arrive too late.
Handing off properly
A botched handoff is nearly as damaging as an invented answer. Three conditions make it acceptable to the person on the other side.
First, context follows: the human taking over sees the conversation and does not ask for everything again. Second, the wait is stated: when the answer will come, and through which channel. Third, the promise is kept. An assistant announcing a callback that never happens does more damage than one that promised nothing.
What handoffs reveal
Escalated requests are the best inventory of an organisation's knowledge gaps. They say exactly what people look for and fail to find.
Reading them weekly beats any satisfaction survey. That reading produces the list of content to write, in the order it is actually missing.
The public website case
On a website, handoff needs particular care: the visitor is anonymous, in a hurry, and under no obligation to stay. The classic contact form loses most people at exactly that moment.
A well-built website chatbot offers human follow-up without demanding a full case file: an address, the conversation attached, and the promise of an answer. The rest is asked later, once contact is established.
Read the last twenty handoffs before adding a single source. They will tell you what to write, and often that the problem sits on a page of your site rather than in the assistant.
Frequently asked questions
The mechanism by which an assistant stops answering and passes the request to a person. Not an admission of failure but a central setting: an assistant unable to hand off compensates for ignorance with a plausible but wrong answer.
In four situations: information is missing, stakes are high, the person asks for it, or the tone changed. Those rules are written before go-live; written after an incident, they arrive too late.
Not necessarily. An artificially low rate should worry you more: it often means the system answers anyway on questions beyond what it knows. Escalated requests are the best inventory of an organisation's knowledge gaps.
Related terms
At KERN-IT
We put an assistant on your site that answers from your pages and routes to you when needed.
→ Chatbot and assistant for your website