A chatbot that never lets you reach a person is one of the most frustrating things on the internet. A chatbot that hands over too early saves no one any time. Getting the handoff right is what makes a support bot worth having.

Signals that a person should take over

The customer asks for a person. "Talk to a human", "agent", "call me". Always respect this.
The bot does not know the answer. It should say so and hand over, not guess.
The customer is upset. Complaints and frustration need a human tone.
The issue needs judgement or access the bot does not have: refunds, exceptions, account changes.
The same question goes round in circles. Two or three failed answers is enough.
High-value moments, such as a large order or a sales lead ready to buy.

Keep the whole conversation

The worst handoff is one where the customer has to start again. The person taking over should see everything the customer said, what the bot answered, and any details already collected, such as an order number or email. That alone removes most of the frustration of being passed along.

Be honest about wait times

When a conversation goes to the queue, tell the customer what happens next.

During business hours: "A member of our team will reply shortly."
Out of hours: "Our team is back at 9am. We will reply here, and you will get a notification."

Never pretend a person is coming in minutes when nobody is online.

Decide what the bot does while the customer waits

Some teams let the bot keep helping with simple questions while the conversation waits for a person. Others pause the bot so the customer is not confused about who is replying. Either works, as long as it is consistent and clear.

Make it easy to ask

Offer a "Talk to a person" button, not just a hidden keyword.
Recognise common ways people ask, in the languages your customers use.
Do not make people answer five questions before they can reach someone.

Use handoffs to improve the bot

Every handoff tells you something. If many conversations about one topic go to a person, the bot probably needs better content on it. Review handoff reasons regularly and add the missing answers.

When a chat should become a ticket

If the person who took over cannot finish the job in that conversation, for example a replacement needs to be shipped, turn it into a ticket with an owner and a priority, so it is tracked until it is done.

How handoff works in IotaBot

IotaBot hands a conversation to your team when the customer asks for a person, when keywords you choose appear, or when the AI cannot answer. Your agents see the full history on every channel, you can limit automatic handoff to business hours, and issues can be turned into tickets. See the help desk software page.