AI agents can answer a large share of routine questions. The moments that shape how customers feel, though, are often the ones the AI should not handle alone. A clean handoff is what makes an AI agent feel helpful rather than in the way.
When to hand over
Write down clear rules before you go live. Common triggers:
- The customer asks for a person. Always honour this, quickly.
- Sensitive topics. Complaints, refunds, cancellations, legal or medical questions.
- Low confidence. The agent cannot find an answer in your content.
- Repeated failure. The customer has rephrased the same question twice.
- Negative sentiment. Frustration or anger in the messages.
- High value. A large order, a key account or a sales opportunity.
Start with a broad set of handoff rules. You can narrow them once you have seen real conversations.
Route to the right team
A handoff to "anyone" is barely better than no handoff. Use what the agent has learned to pick the destination:
| Signal | Route to |
|---|---|
| Billing or refund intent | Billing team |
| Product question with buying intent | Sales, round-robin |
| Technical problem | Support, by product |
| VIP tag on the contact | Account manager |
| Outside business hours | Next-day queue, with a clear expectation |
Never make the customer repeat themselves
The worst handoff is the one where a person says "How can I help?" after the customer has already explained everything. Give the agent a summary instead. A good handoff summary includes:
- What the customer wants, in one sentence.
- Key details: order number, account, product.
- What the AI has already tried or told them.
- Why it is handing over.
In Whatsuite, the AI writes this summary automatically and pins it to the top of the conversation when it is assigned.
Tell the customer what is happening
Be honest and specific.
- Weak: "Please wait."
- Better: "I am passing you to our billing team. Someone usually replies within 15 minutes during opening hours, and they will see everything you have told me."
Only promise a response time you can meet. Outside opening hours, say when someone will be back.
Pause the AI while a person is replying
Once a person takes over, the AI should stay quiet. Two voices in one chat confuses everyone. Good practice:
- Pause the agent as soon as a person is assigned or starts typing.
- Resume it only when the chat is closed, or when the person hands it back.
- Let the person ask Copilot for a draft privately, without the AI writing to the customer.
Respect the messaging window
Handoffs can take time. Remember that free-form replies are only possible while the 24-hour customer service window is open. If a person picks the chat up late, they may need an approved template to continue. Whatsuite shows the time left on each chat so agents can prioritise.
Measure the handoff, not just the AI
Look at these numbers every week:
- Handoff rate, and which reasons trigger it most.
- Time from handoff to first human reply.
- Resolution after handoff.
- Customer feedback for AI-only and handed-over chats.
If one topic triggers lots of handoffs, consider adding content so the AI can answer it, or adding a tool so it can complete the task. If handoffs wait too long, the fix is staffing or routing, not the AI.
A simple starting setup
- Hand over on request, on sensitive topics and on low confidence.
- Route by intent to three or four teams.
- Add an automatic summary to every handoff.
- Pause the AI when a person replies.
- Review a sample of handed-over chats every week.
That alone puts you ahead of most AI deployments.