Design cross-functional handoff templates from thread misses
Stand up a **handoff-miss partner**. Paste redacted cross-team threads. Classify failure **archetypes** (missing field, wrong owner, slip, tone). Emit paste-ready **template blocks** for Slack, email, and tickets so the next handoff lands clean.
Plus: three Admin-Agent passes: cluster misses into four archetypes without inventing drama, draft one tight template block per archetype with mandatory fields, and wire optional gates ([Require human approval before risky actions](/tutorials/require-human-approval-before-risky-actions)) when dollars or reputation spike.
| Audience | Everyone · Admins · Executives |
|---|---|
| Time | ~15 min |
| Prerequisites | Agent basics ([Create an agent from scratch](/tutorials/create-an-agent-from-scratch), [Give your agent its job description](/tutorials/give-your-agent-its-job-description)). Helpful: workplace chat connected ([Connect Slack to your agents](/tutorials/connect-slack-to-your-agents)), rhythm ([Turn meeting notes into action items and decisions](/tutorials/turn-meeting-notes-into-action-items)). **Different lesson:** agent-to-agent seams ([Chain steps so agents hand off cleanly](/tutorials/chain-steps-so-agents-hand-off-cleanly)). |
| You'll end up with | A **Handoff Miss** agent, one **archetype map** with receipt quotes from your paste, and at least three **template blocks** (Slack, email, ticket) you can drop into playbooks. Optional: one workflow reminder ([Run a workflow](/tutorials/run-a-workflow)) for the human who owns follow-up only. |
When a tutorial shows italic text in quotation marks, it usually mirrors a label or helper string inside Auxot. Product copy changes between releases — if something reads differently in your workspace, trust what you see on screen.
Callouts with a Worth knowing gold accent are meant as must-read context before you move on. Blockquotes that open with Tip are lighter, optional depth.
Why this matters
Cross-functional work dies in the gaps between tools. Sales promises a date Ops never saw. Engineering ships a fix Customer Success learns about from a customer. Legal answers in email while the team argues in Slack. None of that is an AI routing problem first. It is a human handoff problem: missing fields, wrong owners, dropped follow-ups, and tone that reads like blame.
This tutorial is not Chain steps so agents hand off cleanly. That one draws seams between agents and workflow steps. Here you teach humans how to package work when it crosses departments, time zones, and incentives.
Today you add a partner that learns from what already went wrong in threads you paste. Auxot does not read your mail unattended. You supply redacted sources.
The next time someone says “we should sync,” you can name what type of handoff is failing and hand over a paste-ready template, not another vague calendar invite.
Quick start
- Collect paste samples: export or copy five to ten handoff moments (Slack, email, ticket). Redact customer names, dollar amounts you cannot share, and executive names. Keep roles (Sales, Ops, Legal).
- Create Handoff Miss: ask the Admin Agent in Chat for an agent whose charter classifies each excerpt into exactly one primary archetype: MISSING_FIELD, WRONG_OWNER, SLIP, or TONE_CHANNEL, with SOURCES_QUOTED proving the label.
- Run classification: paste batches of three excerpts at a time until every excerpt maps. Fix labels when two archetypes fight (pick the dominant failure mode).
- Mint template blocks: ask for three paste-ready blocks per archetype (Slack short, email neutral, ticket structured). Each block lists mandatory fields at the top (owner, due date, link, decision).
- Optional gate: if a handoff moves money or production risk, note where Require human approval before risky actions or Set up an Escalation belongs after the human says go.
Done? One archetype where you disagree with the label. That disagreement is data. Edit the charter until labels match how your org actually fails.
The agent can do that?
You classified misses once. These three prompts keep templates from turning into policy wallpaper.
1. Archetype definitions without theater
Chat → Admin Agent:
Paste policy excerpt only: […]. Define MISSING_FIELD, WRONG_OWNER, SLIP, TONE_CHANNEL in our vocabulary. Eight lines max. Each includes one counterexample (what healthy looks like). Markdown. No thread excerpts yet.
Why it’s non-obvious: Without shared definitions, SLIP absorbs every failure mode. Frozen labels let leadership compare quarter to quarter because you wrote the dictionary first.
2. Single-block regression test
Template blocks pasted: […]. For each archetype, write **REGRESSION_CHECK**: one sentence question the receiver asks before accepting the handoff. Must fail loudly if mandatory fields missing. Max fifteen words each. No cute metaphors.
Why it’s non-obvious: Templates usually optimize for sender comfort. Regression checks train receivers to refuse sloppy bundles before work doubles back.
3. Inverted blame audit
Assume receivers did their best. For each MISCLASSIFIED excerpt from earlier paste, argue why the sender skipped a mandatory field. Max three bullets. End with **PROCESS_FIX** not **PERSON_FIX**. Brutal tone, still respectful. Markdown.
Why it’s non-obvious: Handoff postmortems default to names. Process fixes survive turnover because you forced system language.
Go deeper
Automation boundary
When volume justifies sequencing, agent handoffs belong in Chain steps so agents hand off cleanly. Human templates still sit upstream (who owns the request before automation exists).
Escalations
When the next owner must be a person with authority, pair templates with Set up an Escalation so nobody waits on the wrong bell.
Meetings into structure
Turn meeting notes into action items and decisions feeds explicit decisions into handoff blocks so MISSING_FIELD rows shrink.
Customer-facing tone
External polish (Ship clear customer communications) shares discipline with internal handoffs. Different audience, same clarity habit.
Walkthrough
Step 1: Cap excerpt length
Long threads bury the miss. Trim each paste to the moment the handoff breaks (plus two messages of context).
Step 2: Freeze role names
Use ROLE_LABEL tokens in templates until People Ops blesses public examples.
Step 3: Pair with workflow later
Run a workflow can remind you to send the block. It does not replace the human sentence that names the owner.
Step 4: Separate from agent chains
If your team confuses this agent with workflow design, rename it Human Handoff Miss in Settings → Agents.
Step 5: Archive quarterly
Save markdown dated by quarter. Count SLIP frequency month over month. Rising SLIP means calendar load or staffing, not laziness labels.
What’s next
- → Track strategic decisions and when to revisit them. Pair SLIP archetypes with explicit kills and revisit triggers so leadership sees why an initiative was stopped, not just where the handoff broke down.
- → Chain steps so agents hand off cleanly. Automate only after human blocks stabilize. Different seam: agents, not departments.
- → Run a workflow. Optional nudge after the template fires.
- → Require human approval before risky actions. Gates when the handoff touches production or spend.
- → Set up an Escalation. Human authority paths when the template names an escalation owner.
- → Connect Slack to your agents. Paste sources often start in Slack.
Reference
- Pages in Auxot: Chat, Settings → Agents, Settings → Context Files, Workflows, and Escalations
- See also: Track strategic decisions and when to revisit them, Run a vendor and stack creep inventory, Turn meeting notes into action items and decisions, Ship clear customer communications, Onboard a new teammate to your agents