What is an agent handover?

An agent handover is the transfer of responsibility involving an AI agent, in one of two senses: passing a case from the agent to a person, with what they need to continue, or passing ownership of the agent itself from one person to another. Both are moments where context and accountability can be lost, and both need a record.

Why do handovers matter?

The case handover is where customers judge an agent. If the agent hands over a chat or a claim and the person has to start again, the customer pays for the agent's limits twice. A good handover lets the person pick up where the agent stopped, with the facts and the reason it stopped. That is the argument of the handover to a person is where support agents are judged.

The ownership handover is quieter but riskier. When an agent's owner leaves or changes role, the agent keeps running. If nobody takes ownership, its certification may lapse unnoticed and approval rules may go stale. Accountability for what it does next becomes unclear, a problem covered in who is accountable when an AI agent acts on its own.

How does each kind work in practice?

Agent to person. The agent stops, either because the case is outside its bounds or because the customer asks for a person. It passes a note covering what the customer wants, what has been done, what evidence exists and its provenance, why it stopped, and what remains. The handover note template gives fields, and summarising a case for handover covers the drafting.

Owner to owner. The outgoing owner prepares a record of the agent's scope, depth by capability, certification dates, approvers, known issues and open incidents. The incoming owner reviews it, confirms they understand it, and is named in the record before the outgoing owner leaves. The agent ownership handover template lists what to include.

What is an example?

A utility's billing agent handles a customer disputing an estimated bill. It finds the meter reading is declared, not verified, and the customer is asking for a credit beyond its limit. It hands over to a member of the service team with a note: dispute on estimated bill, customer's reading declared, credit requested beyond limit, no prior disputes. The colleague reads it, arranges a verified reading, and resolves the case without asking the customer to repeat anything.

A month later, the billing agent's owner moves to another department. Before she goes, she completes the ownership handover; her successor confirms it and becomes the named owner the same day.

How is a handover different from an escalation?

An escalation sends a case upward because it exceeds someone's authority or the agent's bounds; it is about who may decide. A handover transfers responsibility and context so someone else can continue; it is about continuity. A held action escalated to an approver is not a handover, because the agent's work stays open for a decision. A case passed from the agent to a person who now runs it is.

Which terms are related?

• Agent owner: the person whose responsibility passes in an ownership handover.
• Escalation: sending a decision to someone with more authority.
• Held action: work waiting for a named person, not handed over.

For the wider topic, read AI agent skills by role.