Design the handoffs between my team and an AI agent
A human-agent workflow showing who does each step, what passes at every handoff, where people check, and how work returns to the agent.
The prompt
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.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Working with AI prompts
What to fill in
- TASKS, systems it can reach, actions it can take
- items per day, deadlines, service levels
- what goes wrong if a handoff is missed or wrong
How this prompt is built
This prompt follows the Few-Shot structure (Few-shot prompting). A few-shot prompt includes one or more worked examples of the input and the output you want, so the model can copy the pattern instead of guessing it.
Related prompts
- Build a reusable prompt templateCreates a fill-in-the-blanks template for a task you repeat often.
- Find where AI can help in my work or businessInterviews you about a process and identifies where AI genuinely helps — and where it doesn't.
- Build an AI adoption roadmap for my team or functionA phased plan for adopting AI in sales, marketing, HR, finance, legal, engineering, support, or operations — with use cases, guardrails, and metrics.
- Remove sensitive information before pasting into AIFinds and replaces personal, confidential, and secret data with safe placeholders.