Why the hand-off matters most
In a 2024 Gartner survey of 5,728 customers, 64% said they'd prefer companies didn't use AI for customer service, and the top concern was that it would become harder to reach a person. Gartner's advice to service leaders was to make sure AI lets customers reach a person when it can't help. Gartner: survey on AI in customer service
Put the other way round: an AI agent that answers the easy questions and hands over the hard ones quickly removes the main objection customers have to it.
When to hand off
| When | Example | Why |
|---|---|---|
| They ask for a person | “Can I speak to someone?” | Making them argue with a bot is the fastest way to lose them |
| The knowledge doesn't cover it | A question your pages never mention | A person beats a guess |
| They're upset | “Third time I'm asking, nobody cares!” | Empathy and authority both matter here |
| It's a decision | A refund, an exception, a complaint | Money and policy calls need a person, or a case for one |
| It's going in circles | The same question twice, differently | The bot isn't understanding; a person will |
| It's sensitive | Health, legal trouble, a bereavement | Some conversations shouldn't be automated |
When not to
- Greetings and thanks. “Hi” isn't a request for a person.
- Questions it can answer well. Handing off an easy question wastes your team's time and makes the customer wait.
- “Am I talking to a bot?” That's a question, not a request: answer honestly that it's an AI, and keep helping.
Being honest about AI is also becoming a legal duty. The EU AI Act's Article 50 requires that people are told when they're interacting with an AI system, unless it's obvious; it applies from 2 August 2026. Check with your own adviser how it applies to you. EU AI Act: Article 50
How to hand off well
- Step 1
Tell the customer what happens
“I've passed this to our team; someone will reply here.” Say when, if you can.
- Step 2
Keep the whole conversation
The person who picks it up should see everything the customer said, so nobody asks them to repeat it.
- Step 3
Stop the AI
Once a person is on the chat, the AI should stay quiet for that customer until it's handed back.
- Step 4
Alert the right person
Where they'll see it: email, a messaging app or the inbox, and to one owner rather than everyone.
- Step 5
Reply quickly
On WhatsApp a business can only send free-text replies within 24 hours of the customer's last message, so a slow hand-off can lock you out. Meta: customer service windows
- Step 6
Hand it back
When the person's done, let the AI answer new messages again.
Outside opening hours
- Say plainly that the team is closed and when they'll be back, instead of a hand-off message that implies someone is coming now.
- Keep the chat waiting for the team, at the top of their list in the morning.
- For anything that needs follow-up, take the details now: a case or a contact number means nobody has to start over.
- Let the AI keep answering what it can; most out-of-hours questions are easy ones.
What to measure
- How many chats are handed off, and why: a request, a knowledge gap, a rule.
- How long the customer waits for the first reply from a person.
- Chats nobody answered at all.
- The questions behind knowledge-gap hand-offs: each one is a page you can write, so the next customer gets an answer.
How HeyKiko does it
Kiko hands the chat to your team when a customer asks for a person in their own words, and optionally when your knowledge barely covers a real question or an agent's AI budget runs out. The customer gets your hand-off message, or your closed message outside opening hours. Your team replies from the shared inbox with the whole conversation, Kiko stays paused for that customer, and you can send every hand-off to one person and be told if nobody replies in time. Asked “am I talking to a bot?”, Kiko says it's an AI and carries on.
While a person has the chat, Kiko doesn't run for that customer, so no AI credits are used.
See human hand-off for every setting, or try it free for 14 days.
Sources
Checked on 5 November 2026. We make HeyKiko, which this guide uses as its example.
