AI & Automation

AI to human handoff: when your chatbot should pass the conversation to a person

When should a support chatbot hand the conversation to a person, and how do you do it without losing the customer? The triggers, offering versus transferring, and what a good handoff looks like.

C

Clara Ferrer

Equipo de contenido de Helpium

· 6 min
AI to human handoff: when your chatbot should pass the conversation to a person

A support chatbot is judged less by the questions it answers than by the moment it can't. A customer with a damaged order, a billing mistake or a question nobody wrote down doesn't want a clever bot: they want to know a person will take it from here. That moment is the AI to human handoff, and getting it right decides whether automation saves you time or quietly costs you customers.

In this article we explain when a chatbot should pass the conversation to a person, the two ways to do it, what a good handoff looks like for the customer and for your team, and the mistakes that make people hate talking to bots.

Why the handoff matters more than the bot

Most conversations a business gets are repetitive: order status, opening hours, prices, how to do something. An AI chatbot handles those well, and that's where the time savings come from. We covered it in the 80/20 rule of support.

The other conversations are the ones customers remember. If the bot keeps answering in circles when someone needs a person, the customer doesn't blame the bot: they blame your business. A clear way out to a human is what makes customers trust the automated part in the first place.

When the chatbot should hand off

There is no single rule, but these situations cover almost every case:

  • The customer asks for a person. "Can I talk to someone?" should always work, in any language and however it's phrased. Arguing with that request is the fastest way to lose a customer.
  • The AI doesn't know the answer. If your knowledge base doesn't cover the question, a good bot asks one clarifying question and, if it still can't answer, offers a person instead of guessing.
  • The case needs judgment. Refunds outside the policy, damaged products, exceptions, complaints. You decide which ones, and the bot follows that rule every time.
  • Sensitive topics. Health, legal or financial advice, or anything involving someone's safety, should reach a person no matter how confident the AI is.
  • The conversation goes in circles. If a process isn't moving forward after several turns, it's time for a human to take over.

What is not on the list: frustration alone. Customers type in capitals or complain about the weather; that doesn't mean they want a person. Transferring on every sign of annoyance floods your team with conversations the bot could have closed.

Offer or transfer: the two ways to hand off

There are two approaches, and the right one depends on how your team works:

  • Offer a button. The bot shows a "Talk to a human" option when it can't help or when the customer asks. The customer decides. Your team only gets conversations from people who really want a person.
  • Transfer automatically. As soon as the customer asks for a person, the conversation goes to your team without an extra tap. Faster for the customer, more conversations for the team.

Many businesses start with the button and switch a channel to automatic transfer once they see how many requests they really get. It can also differ per channel: on WhatsApp, where customers expect a conversation, automatic transfer often feels more natural than on a website chat.

What a good handoff looks like

For the customer, a good handoff is boring in the best way:

  1. They know what happens next. "Someone from the team will reply here" is better than silence or a vague "please wait".
  2. They don't repeat themselves. The person who takes over has already read the conversation: the order number, what the customer tried, what the bot already said.
  3. The bot stops talking. Nothing is more confusing than a bot that keeps answering after a person was promised.
  4. Nobody promises a time they can't keep. "In two minutes" at 11 PM breaks trust. Say the team will reply in this same conversation, and let your business hours set the expectation.

For your team, a good handoff arrives with context: a short summary of what the customer needs and the details they already gave, so the first human message solves something instead of asking questions again.

What to do outside business hours

Customers message at night and on weekends. When they ask for a person and nobody is there, don't pretend otherwise: transfer the conversation anyway and tell them honestly that the team is away and will reply in the same conversation when they're back. We go deeper into it in after-hours messages: what to reply without losing sales.

Mistakes to avoid

  • Hiding the human. Making people type "agent" five times to reach someone saves nothing: they leave.
  • Handing off at the first doubt. If every slightly unusual question goes to a person, the bot isn't saving your team any time.
  • Losing the context. A handoff where the agent starts with "How can I help you?" undoes everything the bot did.
  • Never looking at the numbers. The share of conversations the AI resolves on its own tells you which questions your knowledge base is missing.

How Helpium handles it

In Helpium you choose how the handoff works on each channel (website chat, WhatsApp, Instagram and Messenger): disabled, when the customer taps "Talk to a human", or automatically as soon as the customer asks for a person.

  • Asking for a person always works, in any language. When the AI isn't sure of an answer, it asks once to clarify and then offers a person instead of guessing.
  • Sensitive topics always offer a person, and you can write your own rules for when to hand off. AI Workflows, the procedures your team writes in plain language, can include a "hand off to a person" step for the cases that need one.
  • When a conversation is handed off, the AI stops replying, the conversation lands in your inbox and your team is notified by email, in the app and on their phones. The customer is told someone will reply there, or that the team is away if it's outside your business hours.
  • The agent gets a handoff summary with what the customer needs and every detail they gave, and the first person to reply takes the conversation. Agents can also step into any conversation at any time.

The analytics dashboard shows how many conversations the AI resolves without a person, so you can see which questions to add to your knowledge base. If you're still deciding whether a chatbot makes sense for you, start with when is the right time to implement a support chatbot.

In short

  • The handoff is what makes customers trust the automated part of your support.
  • Hand off when the customer asks, when the AI doesn't know, for cases that need judgment and for sensitive topics. Not on frustration alone.
  • Choose between offering a button and transferring automatically, per channel.
  • A good handoff tells the customer what happens next, never makes them repeat themselves, and gives your team the full context.

AI-powered support without AI-powered pricing

Unlimited seats. One flat price. Serve customers with AI and a human team when it matters.

Keep reading