Design the handoffs between your team and an AI agent
Overview
This prompt designs a shared workflow between your team and an AI agent, with clear handoffs both ways. You fill in the process, what the agent will do, the people involved, the volume and timing, and what is at stake. It returns a workflow table, the packet a person receives at each handoff, how people send work back to the agent, queue and ownership rules, an exception lane, the effect on each role and a small pilot plan. You get a workflow plan ready to pilot.
Use cases
Show all 6Show fewer
Prompt
Copied 0
Design a workflow where my team and an AI agent share a process, with clear handoffs in both directions. **The process:** [WHAT IT ACHIEVES and its main steps - e.g. "triage inbound supplier invoices and resolve mismatches"] **What the agent will do:** [TASKS, systems it can reach, actions it can take] **People involved:** [ROLES, working hours, how they will be notified - e.g. "AP clerk via Teams", "finance manager via email"] **Volume and timing:** [items per day, deadlines, service levels] **Stakes:** [what goes wrong if a handoff is missed or wrong] Return: 1. **Workflow table:** Step | Owner (Agent / Human / Agent then human check) | Input | Output | Handoff to | Handoff trigger | Time limit. 2. **Handoff packets** - for every agent-to-human handoff, exactly what the person receives: the item, what the agent did, what it is unsure about, the evidence, and the decision needed. Keep each packet readable in under a minute. 3. **Return path** - how a person sends work back to the agent (approve, correct, reject with a reason) and how the agent uses the correction. 4. **Queue and ownership rules** - who picks up items, backup cover, what happens to items left waiting, and how nothing is lost between shifts. 5. **Exception lane** - cases that skip the agent entirely and go straight to a person. 6. **Team impact** - what changes in each role, the new skills needed, and the review workload this creates, marked as estimates. 7. **Pilot plan** - run it on a small, low-risk slice first, with the measures that decide whether to expand. Rules: never let an item sit with no named owner; default to a person when the agent is unsure; keep decisions about people, money commitments, and anything irreversible with a human.
Can AI?
- Design the handoffs between your team and an AI agentPaste into a general LLM and design the handoffs between your team and an AI agent.