Design · 7 min read

Handing over to a person

The moment a bot passes a customer to a person decides how people feel about the whole experience. This guide covers when to hand over, how, and what the rules say.

Updated 15 November 2026 · Sources at the end

In short

  • Offer a person as soon as someone asks. Never make them argue with the bot.
  • Plan the triggers: asking for a person, complaints, payments, sensitive topics, repeated confusion.
  • Pass the conversation on, so the customer does not start again.
  • Say when the team is available, and what happens out of hours.

Why the handover matters most

People are wary of chatbots used as a wall. In a 2026 survey for Citizens Advice, 40% of those who tried to reach a human after meeting a chatbot found it difficult or impossible (opens in a new tab). In Ofcom’s research, people saw access to a person as key for complex or sensitive issues (opens in a new tab), and globally, 64% of customers told Gartner they would prefer companies did not use AI in customer service at all (opens in a new tab).

A clear, quick way to a person is what makes a bot acceptable. It is also, increasingly, a requirement.

Plan the triggers

  • The customer asks. “Person”, “human”, “agent”, “speak to someone”. Hand over straight away.
  • A complaint. Apologise once, then hand over. Do not try to resolve it with an FAQ.
  • Money. Payment failures, refunds, disputes and anything that needs a decision.
  • Sensitive topics. Health, bereavement, debt, safety, or someone who sounds distressed.
  • Confusion. Two answers in a row the bot is not sure about, or the customer repeating themselves.
  • Your own list. Important customers, legal threats, press enquiries.

Hand over well

Say what is happening and what comes next: “I’ll pass you to the team. They’re in until 6pm and will reply here.” Pass the conversation and any details already collected, so the person can pick up without asking again. If the route is a call back or an email, confirm the contact details first.

Out of hours, be honest. Say when the team is back, offer to take the details, and give an urgent route if there is one. Do not pretend a person is coming now when they are not.

What the rules say

Several rules now expect a route to a person:

Avoid the loops that frustrate people

  • Never answer “I want a person” with another menu
  • Never ask the customer to rephrase more than once
  • Never end a conversation without saying what happens next
  • Never hide the phone number or email to push people into the chat

The bot designer has a handoff step for the triggers, route, hours and out-of-hours message, and its test chat shows you exactly when your bot hands over.

Questions people ask

Should a bot always offer a person?

It should always be possible to reach one, and the bot should offer one when it cannot help. It does not need to offer a person in every message if it is solving the problem.

What if we have no one available to take chats?

Use a call back or an email reply with a clear time frame. A route that takes a few hours but is honest is better than a live chat promise you cannot keep.

How do we measure the handover?

Count how many conversations hand over and why, and read a sample. A falling handover rate is good only if customers are getting their answers, not giving up.

Design your bot in an afternoon

Free, no sign-up. Pick its jobs, write its answers, set the handoff, then test it in your browser and export the plan.