A chatbot handoff message is what the bot says when it passes a conversation to a person, and what that person says when they arrive. It has three jobs: tell the customer a human is coming, set an honest expectation for the wait, and make sure nobody has to repeat themselves. Below are 18 copy-ready examples for every moment of the handoff, from the offer to the first human reply.
Use this pair today if you only need one:
Bot: I'll bring in someone from our team for this. They'll see
everything we've talked about, so you won't need to repeat it.
Current wait: about [X] minutes.
Agent: Hi [name], I'm [agent name]. I've read the conversation, so
I know you're asking about [issue in their words]. Let me
[first action].
Key Takeaways
- The handoff has five moments: the offer, the confirmation, the wait, the arrival and the offline fallback. Each needs its own line.
- Promise "you won't need to repeat it" only if your agent really sees the chat history.
- Give a wait time or a channel, never "someone will be with you shortly".
- The agent's first line should prove they read the conversation.
- When nobody is online, say so and collect an email. Leaving the customer in a queue until they close the tab loses them.
When a chatbot should hand off to a person
A chatbot should hand off when the customer asks for a person, when the question needs a decision the bot cannot make, or when the bot has failed to help twice. Everything else it can usually answer from your help content.
Common triggers worth writing handoff lines for:
| Trigger | Example | Why the bot should step aside |
|---|---|---|
| The customer asks for a person | "Can I talk to someone?" | Refusing feels like a trap |
| An exception to a policy | A return after the deadline | Someone must decide |
| Account or payment problems | A charge they don't recognize | Needs verification and judgment |
| Frustration | Repeated questions, "this isn't helping" | Every extra bot reply makes it worse |
| Sales intent | "Can you do a custom plan for 40 seats?" | A person closes this, a bot loses it |
| The bot isn't confident | No source in your content answers it | A guessed answer does more harm than a wait |
The last trigger matters most with AI chatbots. An AI agent that answers only from approved content should hand off the moment that content runs out, instead of improvising. That is how Conecto's AI agent is set up in the human handoff flow.
Chatbot handoff message examples by moment
Moment 1: Offering the handoff
The offer should come before the customer has to fight for it. Name what the person can do that the bot can't.
1. Plain offer
I'm not the right one to sort this out. Would you like me to bring in someone from our team?
2. When a decision is needed
Returns after 30 days need a person to review them. Want me to pass this to our team? They'll see everything you've told me.
3. After two failed answers
I don't think I'm getting this right, and I don't want to waste your time. Let me get a person to help.
4. For sales questions
A custom plan is best handled by our sales team. Shall I connect you now?
Moment 2: Confirming the handoff
Once the customer says yes, confirm three things: a person is coming, they'll see the history, and roughly when.
5. Standard confirmation
Done. I've passed this to our team. They'll see our whole conversation, so you won't need to repeat anything. Current wait: about 4 minutes.
6. With a named team
You're in the queue for our billing team. [Agent name] usually picks these up within 10 minutes.
7. When the customer is upset
I'm sorry this has been frustrating. A person from our team is taking over now and will see everything you've written.
Moment 3: While the customer waits
A wait feels shorter when the customer can do something useful with it, or knows they can leave.
8. Invite useful details
While you wait, you can add your order number or a screenshot here. Whoever joins will see it first.
9. Let them leave
You don't need to stay on this page. If you leave your email, we'll reply there if you've gone by the time someone joins.
10. The wait got longer
It's busier than usual, so it's taking longer than I said. You're still in line, and nothing you've written is lost.
Moment 4: The agent joins
The agent's first line sets the tone for the rest of the conversation. Use their name, show you read the history, and start working.
11. Show you read it
Hi Sam, I'm Alex. I've read the conversation, so I know the refund for order 1042 hasn't arrived. Let me check the payment now.
12. Ask one sharp question
Hi Sam, I'm Alex. I can see you've already tried resetting the password. Which email address are you using to log in?
13. Take ownership of a mess
Hi Sam, I'm Alex, and I'm sorry you had to go back and forth with the bot. I'll handle this myself from here.
Moment 5: When nobody is available
An honest offline message keeps the customer. A queue that never moves loses them.
14. Outside business hours
Our team is offline until 9 AM CET. Leave your email and question here and a person will reply first thing, with this conversation attached.
15. Everyone is busy
Everyone on our team is helping other customers right now. Leave your email and we'll reply within 2 hours, or keep chatting with me in the meantime.
16. Ticket created
I've created a ticket for this (#4821) and sent the details to your email. Reply to that email any time and it goes straight to our team.
Moment 6: Back to the bot, or closing
17. Agent hands back for a routine question
I've sorted the refund. If you have other questions about delivery or sizes, our assistant can answer those right away, and I'm here if you need me.
18. Closing the loop
Is there anything else I can help with? If not, I'll close this chat. You can reply here later and it will reopen with the whole history.
What makes a handoff message work
A handoff message works when every promise in it is true in your setup. Check these before you publish your lines:
- "They'll see everything" must be true. If your agents get a new ticket without the chat history, the customer will repeat themselves and notice the broken promise.
- The wait time must be real. Show a live estimate, a typical range, or none at all. A made-up "2 minutes" that becomes 20 is worse than no number.
- The customer can always leave. Offer email or a ticket so the conversation survives a closed tab.
- The first human line is written by a human. Templates help with structure, but the agent should rewrite the opening around the actual problem.
- The bot stops talking. Once a person has joined, the bot should not reply over them.
Handoff mistakes that frustrate customers
- Hiding the human option. Making customers type "agent" five times teaches them your bot is a wall.
- Starting over. "How can I help you today?" after a ten-message bot conversation is the most common handoff failure.
- No offline plan. A handoff at 11 PM with no email capture ends with the customer gone.
- Vague waits. "Someone will be with you shortly" means nothing.
- Handing off too late. Two failed bot answers is enough. A third makes the customer angry before the person even arrives.
Handoff on the page, not just in the chat
Some handoffs go better when the person can see what the customer sees. With Beside, a teammate who joins the conversation can ask to see the page the visitor is on and, once the visitor allows it, point at the right button instead of describing where it is. The handoff lines above still apply; the agent's first message can simply say "I can see the page you're on".
Frequently asked questions
What is a chatbot handoff?
A chatbot handoff is the moment a conversation moves from an automated assistant to a person, ideally with the full chat history passed along so the customer doesn't repeat anything.
What should a chatbot say before handing off to a human?
It should say that a person is coming, that they'll see the conversation, and when to expect them, for example: "I'll bring in someone from our team. They'll see everything we've talked about. Current wait: about 5 minutes."
How long should customers wait for a human after a handoff?
As short as your staffing allows, but the number matters less than honesty. Show a real estimate, and offer email when the wait is long or the team is offline.
Should the agent introduce themselves after a handoff?
Yes. Use your first name and one sentence that shows you've read the conversation. It tells the customer they won't have to start over.
How do I write handoff messages for an AI chatbot?
Use the same moments as above, and add one rule: the AI should hand off whenever your content doesn't answer the question, instead of guessing. More reply templates for the rest of the ticket are in our customer support email templates.
Put your handoff lines in place
Pick one line for each of the five moments, check every promise against how your inbox really works, and test the full path with a colleague acting as the customer. If you want the AI agent, the handoff and the shared inbox in one place, start a Conecto workspace and turn on human handoff.