AI to Human Handoff Template: The 5 Fields That End Repeats

Routing decides who answers. The handoff decides what they know when they open the thread. Five fields turn a six-minute reconstruction into a sixty-second reply, and stop the customer repeating themselves a third time.

A property-management company with 340 units put an AI agent on its tenant chat line. A tenant wrote in about a slow leak under the kitchen sink, explained that maintenance had already visited once and rescheduled, and added the two windows when they'd be home. The agent recognized the escalation trigger and handed off in under a second. Technically flawless.

Then the human opened the thread and typed: "Hi, how can I help you today?"

The tenant, who had now explained the same leak three times to three surfaces, closed the chat and wrote the review instead. The escalation worked. The handoff failed. Those are different problems, and only one of them gets any attention.

Routing decides who. Handoff decides what they know.

Most teams build escalation as a trigger. Sentiment drops, a keyword matches, confidence falls, and the conversation routes to a human. Then the work is considered done.

But routing only answers the question of who replies. It says nothing about what that person knows when the thread opens. Without a payload, the human starts from zero, and the customer pays for the blank start with a fourth retelling.

The cost is measurable, and it's not the cost you'd guess. In the deployments I've audited, the median human reply time after an AI escalation was over six minutes — and most of that wasn't thinking. It was archaeology: scrolling the transcript, working out what had already been promised, deciding what to say next. With a payload in front of them, the same replies went out in under sixty seconds. The humans didn't get smarter. They stopped reconstructing context from scratch.

The five-field payload

Every escalation should carry exactly five fields. Not a transcript dump — five fields, filled every time.

1. Contact    — name + one reachable channel
2. Summary    — one sentence, in the customer's own words
3. Tried      — what the agent already answered or promised
4. Open       — the unresolved question, stated plainly
5. Suggested  — a draft reply the human can edit and send

Here is a filled example, for the leak:

1. Contact:   Tenant in Unit 12B, prefers SMS
2. Summary:   Slow leak under kitchen sink; maintenance visited once and rescheduled
3. Tried:      Confirmed a ticket exists; did NOT promise a visit time
4. Open:       Needs a confirmed appointment; tenant home 4–7pm this week
5. Suggested: "Hi — apologies for the reschedule. I can book a tech Thursday
               between 4 and 6pm. Does that work, or would Friday be better?"

Look at field 3. "Did NOT promise a visit time" tells the human the schedule is still open, so there's no risk of contradicting a promise the agent already made. That one line prevents the most expensive handoff failure there is: a human, not knowing what was said, over-promising a second time.

The transcript is not the payload

The instinct is to attach the whole conversation. More context must be better, right?

In practice a raw transcript makes the handoff slower. The human has to read interleaved messages, separate what the customer wants from what the agent guessed, and draft a reply in their head. The five fields do that compression work before the human opens the thread. Ten seconds of reading replaces two minutes of detective work.

Keep the transcript one click away for the rare case it matters. Make the five fields the thing that's already open.

Bad handoff, good handoff

The difference is visible in a single line.

What the human receives	What it costs the customer	What good looks like
"A customer needs help"	A fourth retelling	One sentence in the customer's own words
A raw transcript	Two minutes of reading before typing	Five fields, pre-compressed
A summary with no history	Risk of re-promising what the agent already said	"Tried" names what was and wasn't promised
No draft	A blank-page pause	A suggested reply, editable in ten seconds
No channel	A round of tag	Name plus one reachable channel

[!TIP]
Make field 3 honest about the negative. "Did NOT offer a refund" is more useful to the human than "discussed refunds." The gap is what they need to see.

Where to put the payload

Three options, in order of usefulness:

1. Ticket description. The payload is the ticket body. Best when escalation creates a ticket — the human reads before they click anything.
2. First internal note. If your tool separates the description from internal notes, put it there so it sits above the transcript.
3. Pinned internal message. Minimum viable. Best for Slack- or Teams-based support, where the whole channel is the inbox.

Whichever you pick, one rule governs it: the payload is the human's starting state. If they have to ask "what did this customer want again?", the handoff is broken no matter how much text you attached.

The 90-second drill that proves it works

You don't need a statistic to know whether your handoff holds up. You need a stopwatch.

1. Trigger three escalations with distinct scenarios — a billing question, a safety or allergy question, and a complaint.
2. Time a human from the moment they're assigned the thread to the moment their reply is sent.
3. Target: under sixty seconds per reply, using only the payload.

If the human has to open the transcript to write the reply, a field is missing. If they have to ask the customer a question before replying at all, field 3 or field 4 is too vague. Both failures show up in the first drill and are cheap to fix.

Common mistakes

• Attaching the whole transcript. It feels thorough. It makes the human read instead of reply.
• Writing the summary in the agent's words. The customer's own phrasing carries intent the agent's paraphrase flattens.
• Leaving field 3 blank. This is the field that prevents double-promising, and it's the one most teams skip.
• No suggested reply. A draft converts a blank-page pause into a ten-second edit.
• Routing to a queue instead of a person. An unassigned escalation with a perfect payload still waits.

What to do today

1. Add the five fields to your escalation output and make the payload the ticket body, not an attachment.
2. Run the 90-second drill on three escalations and time the human replies with a stopwatch.
3. Fix whichever field is missing when the drill fails — usually field 4, the plain statement of what's still open.
4. Make "did NOT" lines mandatory in field 3, so no human ever re-promises what the agent already said.

An escalation that lands with context does three things at once: the customer never repeats themselves, so they don't leave; the human answers in one pass, so the queue drains; and nothing gets promised twice, so you don't honor a refund nobody authorized. Five fields, filled every time. That's the whole method.

---

This guide lives at AgentFast, where you'll also find a free audit tool that checks your own agent's instructions against these failure modes. Posted here with a canonical URL pointing at the original.