> ## Documentation Index
> Fetch the complete documentation index at: https://docs.duvo.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Agent Handover

> Let one agent pass its work to another agent when a Run completes, for triage, escalation, and multi-step workflows.

Agent Handover lets one agent pass its work to another agent when a Run completes. Use it to build multi-step workflows where a general agent routes work to a specialist, or where one stage of a process hands off to the next.

## Key Capabilities

* **Route work automatically**: An agent can hand off to a pre-configured target agent at runtime—no manual intervention needed.
* **Configure targets in the AOP**: Mention other agents with `@Assignment Name` directly in the AOP to set them as allowed handover targets.
* **Works with Queue**: For case-based workflows, the case is released and routed to the target agent through the regular case dispatcher.
* **Works with standalone Runs**: For non-case Runs, a new Run is started for the target agent, not carrying over any context from the source run.

## How to Use It

<Steps>
  <Step title="Open the Agent Builder" icon="square-pen">
    Open the agent you want to configure as a handover source and navigate to the AOP editor.
  </Step>

  <Step title="Mention a target agent" icon="at-sign">
    In the AOP textarea, type `@` followed by the name of the agent you want to hand off to. A dropdown appears listing available agents in your team.

    Select the agent. A badge is inserted inline in the AOP text—this registers it as an allowed handover target.

    Place the mention within naturally written rules for handover. You can add multiple targets if your agent may route to different specialists depending on the situation.

    **Example AOP instruction:**

    > After reviewing the customer request, determine whether it needs billing support or technical support. If billing, hand over to @Billing Specialist. If technical, hand over to @Technical Support.
  </Step>

  <Step title="Save and test" icon="save">
    Save the AOP. On the next Run, the agent will have access to a `request_handover` tool. At runtime, the agent decides when to use it based on your AOP instructions.
  </Step>
</Steps>

### Handover flow

```mermaid theme={"dark"}
flowchart TD
    A[Agent reviews work during Run] --> B{Handover needed?}
    B -->|No| C[Agent completes the Run normally]
    B -->|Yes| D[Agent calls request_handover to a target named in the AOP]
    D --> E{Workflow type}
    E -->|Case-based| F[Case released and routed to target agent via case dispatcher]
    E -->|Standalone Run| G[New Run started for target agent, no source context carried over]
    F --> H[Target agent picks up and continues processing]
    G --> H
    H --> I[Source Run shows handover target in its results]
```

### Viewing handover results

After a handover occurs, the source Run shows the handover target in its results. For case-based workflows, the case timeline reflects which agent handled each stage.

## When to Use It

* **Triage workflows**: A general agent reviews incoming cases and routes each one to the right specialist.
* **Escalation paths**: An agent handles routine cases and escalates complex ones to a more specialized agent.
* **Sequential pipelines**: One agent completes an initial stage (data gathering, analysis) and hands off to another for the next stage (reporting, action).
* **Domain specialization**: Route work to an agent that has the right connections and context for a specific task type.

## Things to Know

* An agent can only hand off to agents configured as targets in its AOP—it cannot hand off to arbitrary agents at runtime.
* If a mentioned agent is deleted, the mention badge turns red in the AOP editor. Remove the deleted target before the next run.
* For case-based handovers, the target agent must have the **Queue (Consumer)** connection enabled. Agents without it are not available as handover targets in queue workflows.