With a note the person can act on and a customer who knows what happens next. A good handover passes who the customer is, how they were verified, what they asked, what the agent did and did not do, and why. The customer is told who will pick it up and roughly when, and never has to repeat themselves.
What should the handover note contain?
The note is the whole handover from the receiving person's point of view. If it is thin, they start again and the customer notices. A usable note has:
- Customer and verification. Who, and how they were verified, so the person does not ask the security questions again unless the next step requires a stronger check.
- The request, in one line. "Wants refund of 140 for a damaged sofa delivered on the 3rd."
- Facts gathered. Order number, photos received, delivery record, prior contacts on the same issue.
- What the agent did. "Booked collection for Thursday." Actions taken are listed with their results.
- What the agent did not do, and why. "Refund above my limit; drafted and held." This is the most useful line and the one most often missing.
- Anything said to the customer that matters. Especially timescales and next steps.
- Flags. Distress, vulnerability, complaint, legal threat, fraud concern.
A fill-in version of this note is worth standardising; the broader question of what to record for every conversation is covered in what a support agent should log about each conversation.
What should the customer hear?
Three things: that a person is taking over, roughly how long it will be, and whether they need to do anything. "I'm passing this to our returns team now. They'll reply here within the hour. You don't need to send anything else." If the wait is longer, say so plainly and offer a callback instead of a queue.
The customer should not hear internal detail: queue names, staff shortages, or the agent's limit in figures.
How does the handover differ by situation?
| Situation | How to hand over | What stays with the person |
|---|---|---|
| Customer asks for a human | At once, without arguing; one-line note | Everything from here |
| Request above the agent's limits | Draft attached, held for approval | The decision |
| Complaint | Note with the complaint stated in the customer's words | Complaint handling |
| Distress or vulnerability | Priority route; warm handover where possible | Support and any flexibility |
| Voice call | Warm transfer: the agent briefs the person before connecting, or passes the note to their screen | The call |
| Out of hours | Callback booked; customer told when | The follow-up |
In chat, the handover should happen inside the live chat tool so the person sees the full conversation; the steps are in handing a live chat over to a person with an AI agent and, for the tool integration, letting an AI agent hand a chat to a person in your live chat tool.
An illustrative example
Take a furniture retailer's chat agent. A verified customer reports a damaged sofa and asks for a full refund of 140 rather than a replacement.
The agent collects photos, checks the delivery record, books a collection and drafts the refund. The amount is above its limit, so it hands over. The note reads: customer verified in the app; sofa delivered on the 3rd, damage shown in two photos; collection booked for Thursday morning; refund of 140 drafted and held, above agent limit; customer prefers refund to replacement; no prior contacts. The customer is told the returns team will confirm the refund by the end of the day and that the collection is already booked.
The returns team member reads the note, checks the photos, approves the refund and replies in the same chat. The customer never repeats a word.
What about consent and recording across the handover?
If the agent told the customer the conversation is recorded, or asked for consent, that carries across the handover and the person should not need to ask again. The note should record what was said. When consent is needed at all is covered in whether a support agent should ask for consent before recording a conversation.
Which controls make handovers reliable?
- A fixed note template, filled by the agent and checked for completeness before transfer.
- Receiver ratings. The person marks whether the note was enough. Thin notes become test cases.
- Wait-time honesty. The agent quotes wait times from the queue system, not guesses.
- No dead ends. If no queue is open, the agent books a callback rather than leaving the customer waiting.
Why this moment matters more than any other is argued in the handover to a person is where support agents are judged.
Where Pryme fits
In Pryme, a handover is a held verdict filed with the bound that triggered it, the facts with their sources, and any draft. The person in the Workspace sees what the agent saw and why it stopped. More is in the AI support agent that knows when to say no.
Questions people ask
Should the agent stay in the conversation after handing over?
It can stay available to fetch information for the person, but it should stop replying to the customer.
What if the person disagrees with the agent's draft?
They change it. The original draft and the person's decision are both recorded, which helps improve the agent.
Can the handover go back to the agent?
Yes, for routine follow-ups such as confirming a collection. The person decides and notes it.