Handoff

A handoff is a transfer. An ongoing process changes hands mid-processing. The English term comes from relay racing: one runner passes the baton to the next without the race being interrupted. In technology, it usually refers to the moment when an automated program can’t proceed further and passes the matter on to a human. But there are also transfers between two programs. In both cases, it’s essential that everything so far travels along: the customer’s question, the answers already given, the customer number, the current status. Without this carrying-over, it isn’t a handoff, but a fresh start.

The moment automation stops

No automated system can do everything. A chatbot reliably answers standard questions but fails on special cases. Precisely for this reason, the handoff is not a stopgap but a planned component. A company deliberately decides which cases the software handles and at what point a human takes over.

For the user, the quality of the handoff determines the overall impression. Anyone who has already typed their order number three times and is asked to state it again to the employee is rightly annoyed. The fault then lies neither with the bot nor with the employee, but with the interface between them. Many complaints about bad chatbots are, in truth, complaints about bad handoffs.

This also matters legally. For contracts, cancellations, or medical questions, regulations often require that a human make the final decision. The handoff is then the technical means of complying with this requirement. The EU’s rules on Artificial Intelligence further reinforce this point for high-risk applications.

What gets passed along in the handover

First, a trigger is needed. Often this is low confidence on the system’s part: the program itself assesses how well it has understood the question, and hands off below a certain threshold. Other triggers are hard-wired, for example around keywords like cancellation, complaint, or refund. Sometimes it’s enough that the user asks the same question twice. And, of course, an explicit request to speak with a human suffices as well.

Then a package is assembled. It contains the complete conversation history, often supplemented by a brief automatic summary. Added to this are data from the customer account and the reason for the handoff. The employee sees all of this upon opening the case, instead of having to read through logs themselves.

A second case is the handoff between programs. In so-called agent systems, several AI programs work together, each with its own specific task. A program for general inquiries passes a billing question on to a program that has access to the accounting system. Here too, the prior conversation history travels along. The classic special case from mobile network technology, incidentally, is called a handover: there, one cell tower passes an ongoing call to the next as you sit on a train.

Handoffs in customer service and product announcements

The term is most commonly encountered in customer service. Chat on a bank or shop website almost always starts automatically. Sentences like I’ll connect you with a colleague mark the handoff. Phone hotlines work the same way: a computer voice pre-sorts the request and then forwards it.

In trade publications, the term comes up when enterprise software is being presented. Vendors advertise seamless handoffs, meaning that no information gets lost. Notably, there’s the handoff rate: the proportion of conversations passed on to humans. A declining rate is considered a success because it reduces staffing costs. If it drops too sharply, however, that’s a warning sign – it may mean customers are being fobbed off with unsuitable answers.

Outside of technology, the word is used similarly. In hospitals, the handoff describes the transfer of a patient at a shift change. There too, the greatest danger is the same: that knowledge gets lost during the transition.