Designing the Hand-Off From Chatbot to Human
By CodexierPublished 5 min read
Most chatbot frustration does not come from the bot failing to answer. It comes from what happens next: the customer is sent to a form, then asked the same questions again by a person two days later. A good hand-off is designed as carefully as the answers. This guide covers when to hand over, what to pass along, how to behave outside opening hours and how to use hand-offs to improve the bot.
Triggers for handing over
Triggers should be explicit rules, not left to the model's judgement. The model can detect some of them, such as frustration or a request for a human, but the list of what always goes to a person is a business decision you write down.
- The customer asks for a person, in any wording. Never argue or offer one more bot answer first.
- No approved source covers the question, or sources contradict each other.
- Refunds, complaints, damaged goods, invoices in dispute or anything that commits the company to money.
- Personal or sensitive situations: health, bereavement, legal matters.
- The same question has been asked twice, or the customer rephrases three times. That is a loop.
- High-value leads, for example a company asking for a quote for a large order.
Passing the conversation context
The single biggest improvement is making sure the person picking up already knows what the customer said. That means the hand-off creates a ticket, an email or a CRM record that carries the context automatically.
| Pass along | Why it matters |
|---|---|
| The full transcript | The person can read exactly what the bot said, including any mistakes |
| A three-line summary | Faster to act on than reading the whole thread |
| Contact details the customer gave | No need to ask for email or phone again |
| Order or booking number if found | Links the case to the right record |
| The reason for hand-off | Tells the team whether it is a gap in the bot or a genuine human case |
Where the case lands depends on your tools: a shared inbox, a help desk, or the CRM. The connection is usually the more technical part of a chatbot setup, and it is where most off-the-shelf widgets fall short because they only offer an email notification without structure.
Outside opening hours
A bot that offers live chat at 23:00 and then leaves the customer waiting in an empty window is worse than no offer at all. The hand-off logic must know your opening hours, including Swedish public holidays and summer closures.
- During opening hours: offer live transfer if someone is actually staffing the chat, otherwise a ticket with a reply time.
- Outside opening hours: say plainly that the team is away, collect contact details and promise a reply by a concrete time, such as before 10:00 the next working day.
- Urgent cases: if you offer an emergency line, show it. If you do not, say so rather than implying one exists.
- Holidays: update the calendar before midsummer, Christmas and the July shutdown, not after the first complaint.
Telling the customer what happens next
Uncertainty is what makes waiting unpleasant. The last message from the bot should answer three questions: who will contact me, how, and when. Something like: our customer service will reply by email before 14:00 today, and you do not need to write again. Send a confirmation email with a case number so the customer has proof the request was received.
Keep the promise realistic. A reply time you meet every time builds more trust than a fast promise you break once a week.
Reviewing hand-offs to improve the bot
Every hand-off belongs in one of two piles. Either the bot should have been able to answer, which means a document is missing or unclear, or the case genuinely needed a person. Sorting them weekly turns the first pile into document fixes and confirms that the second pile is going to the right place. Our guide on stopping a chatbot from making things up describes the same weekly loop from the answer side.
When you do not need this: if nobody on your team can answer chats or emails within a working day, fix staffing first. A polished hand-off into an unanswered inbox only moves the disappointment. And if customers mostly phone rather than chat, a chatbot is the wrong channel entirely. We are happy to say so on a free call.
Frequently asked questions
Should the bot offer a human from the start?
Offer it clearly but not first. A visible option to talk to a person reduces frustration, and many customers will still try the bot because it is faster for simple questions. Hiding the human option is what damages trust.
Can the hand-off go straight into our CRM?
Yes, if the CRM has an API, which HubSpot, Pipedrive and most modern systems have. The bot creates a contact or updates an existing one and attaches the transcript and summary as a note or ticket.
What if the customer gives personal data in the chat?
Treat the transcript like any other customer correspondence under GDPR: store it where your team can access it, set a retention period and make sure the chatbot provider has a data processing agreement with you.
How fast must we answer after a hand-off?
As fast as you promise, and the promise should match your real staffing. Same working day is a reasonable baseline for most small businesses; urgent categories may need faster routing to a phone.
Want a chatbot that knows when to step aside?
Tell us which tools your team answers customers in today and your opening hours. In fifteen minutes we can sketch the hand-off rules and where each case should land.
Book a free 15-minute call