However good an AI assistant is, some conversations need a person: a complaint, a sensitive situation, an unusual request, an urgent problem or a customer who simply prefers to talk to a human. What happens at that moment decides how the customer remembers you. A smooth handover feels like a helpful colleague stepping in with full context. A poor one feels like being dropped: waiting with no explanation, repeating everything, or discovering that nobody is there. This guide explains how to design the handover: when it should trigger, how to notify your team, what context to pass, how to set expectations honestly, what to do out of hours and how to measure how well it works.
When the assistant should hand over
| Trigger | Example | Handover style |
|---|---|---|
| The visitor asks for a person | 'Can I talk to someone?' | Immediate, always honoured |
| Complaint or anger | 'This is unacceptable' | Fast, with empathy |
| Sensitive topic | Medical, legal or financial situations | Handover with careful wording |
| Emergency or safety | 'There is a gas smell' | Safety instructions first, then urgent alert |
| Unanswerable question | The documents do not cover it | Offer a person or callback |
| High-value opportunity | Large job or group booking | Notify a person to take over |
| Repeated failure | Assistant misunderstood twice | Offer a person |
| Money or refunds | A dispute over a charge | Person decides |
Write the triggers down as rules, and test them with realistic messages. Err on the side of handing over sensitive cases.
Never make a handover hard
- Do not hide the option to reach a person.
- Do not make visitors pass several bot questions before they can ask.
- Do not pretend the assistant is a person.
- Do not promise an immediate answer if nobody is available.
- Do not loop the visitor back to the assistant without acknowledging their request.
The best assistants say something like: 'Of course. I will pass you to the team. They can see our conversation.'
What the visitor should see and hear
- Acknowledge: 'I will connect you with a team member.'
- Explain what happens next: 'They can see what we discussed, so you will not need to repeat it.'
- Set an honest expectation: 'Someone will reply within 15 minutes' or 'We reply by 9:30 a.m. on working days.'
- Offer an alternative: 'If it is urgent, call us on this number.'
- Confirm the channel: 'We will reply here in the chat, or by email if you leave one.'
Silence is the enemy. A visitor who does not know what is happening will leave or try again.
What your team should see
| Item | Why it matters |
|---|---|
| A notification with the reason for handover | Context in the first second |
| The full conversation | So nobody asks the visitor to repeat |
| Contact details captured | To follow up if the chat ends |
| What the assistant already promised | So the person does not contradict it |
| The page the visitor was on | Context on what they were doing |
| Priority | Emergencies and complaints first |
In Crescelo, a person can take over any conversation from the dashboard in one click and is notified by email, with the whole history attached. See the human handover feature.
How to notify your team
- Email: reliable, works for everyone, includes the conversation.
- Team chat such as Slack: fast for teams who live there; see webhook automations.
- Text or push alerts: for urgent cases, via an automation.
- Dashboard notification: for people already working in it.
Choose at least two routes for urgent handovers, so a missed email does not cost a customer. Make sure the alert goes to a person who is actually on duty, not to a shared inbox nobody watches.
Handover out of hours
Nobody is there at 10 p.m., and the assistant should say so honestly. Three good patterns:
- Offer a callback or email reply at a set time the next working day, and capture the contact.
- Offer the next available booking so the visitor secures a slot now.
- For emergencies, direct to your emergency line or emergency services with approved wording.
Then make sure the next morning's team sees these handovers first. See after-hours appointment booking.
Taking over and handing back
When a person takes over, the assistant should stop replying so visitors do not get two voices. When the person is done, decide whether the assistant resumes or the conversation closes. Give the person a way to end the takeover cleanly. Let them mark the outcome, such as resolved, booked or follow-up needed, so you can review it later.
Etiquette for the person who takes over
- Greet by name and acknowledge what was said already.
- Read the whole conversation before replying.
- Do not repeat questions the visitor has answered.
- Correct any mistake the assistant made, without blaming it.
- Reply quickly, even if only to say when you will have an answer.
- Close the loop: confirm the outcome.
See live human handover etiquette and best practices.
Measure handover quality
| Metric | What it tells you |
|---|---|
| Handover rate | Share of conversations passed to a person; a very high rate means the assistant needs better content |
| Time to first human reply | Whether the team responds fast enough |
| Reasons for handover | Which topics to improve or keep human |
| Repeat questions after handover | Whether context passes correctly |
| Resolution rate after handover | Whether people actually help |
| Handovers with no response | Process failures to fix urgently |
Review handover conversations weekly as part of your chat review routine. Every handover is either a sign that a person was needed or a gap to close.
Common mistakes
- A handover button that goes nowhere.
- Alerts sent to an unattended inbox.
- Making visitors repeat themselves.
- No expectation set about waiting time.
- The assistant and a person both replying.
- Never reviewing why handovers happen.
Worked example: a complaint about a bill
| Speaker | Message |
|---|---|
| Visitor | I was charged twice for my appointment. This is ridiculous. |
| Assistant | I am sorry about that. Billing needs a person to check, so I am passing this to our team now. They can see this conversation, so you will not need to repeat it. Someone will reply within 30 minutes during office hours, and I have noted your contact details. Could you tell me the email you used to book? |
| Visitor | sam@example.com |
| Assistant | Thank you, Sam. I have passed everything on. If it is urgent, our number is below. |
The assistant did not try to resolve a billing dispute. It acknowledged the problem, explained the next step, set an expectation, captured the missing detail and flagged the conversation as a complaint. The person who picks it up starts with the whole picture.
A handover policy you can adapt
- The assistant always hands over when asked.
- It always hands over complaints, refunds and billing disputes.
- It hands over sensitive topics with approved wording and never gives advice.
- For emergencies it gives safety instructions first, then alerts an on-call person.
- Handovers are answered within a stated time in business hours, and by a stated time the next working day otherwise.
- Every handover is logged with a reason and an outcome and reviewed weekly.
Write it down, share it with your team and revisit it quarterly.
Training your team for handovers
Handover works best when the people receiving it know what to expect. Spend fifteen minutes walking the team through a real handover: where the alert arrives, how to open the conversation, how to reply and how to close it. Agree who is on duty in each time slot and who covers when they are away. Role-play an awkward case, such as an angry customer, so that the first real one is not the first time anyone has tried it.
When to hand back to the assistant
Some handovers are brief: a person answers one question and the conversation could continue with the assistant. Decide whether your setup lets the assistant resume, and how the visitor is told. If it does, the person should say so ('I will let the assistant take over booking now'), and the assistant should confirm it has the context. If it does not, the person should finish the conversation, so the visitor never talks to two voices that contradict each other.
Frequently asked questions
When should a chatbot hand over to a human?
When the visitor asks, for complaints, sensitive topics, emergencies, unanswerable questions, high-value opportunities and repeated failures.
How does the human see the conversation?
Good handover passes the full conversation and contact details to the person, so the visitor does not repeat anything.
What if no one is online?
Say so honestly, capture contact details, offer a callback or a booking, and direct emergencies to the right route.
Does Crescelo support human handover?
Yes. Your team can take over any conversation from the dashboard, with notifications and the whole history.
How many handovers are normal?
It varies. Very high rates suggest content gaps, and very low rates may mean people cannot find the option.
Should the assistant continue after a person joins?
No. Pause the assistant while a person is talking to avoid two voices.
See the human handover feature, try a handover request in the playground and start a free trial.
Further reading
- Google Search Central: creating helpful, people-first content: What Google looks for in useful pages.
ANSWER EVERY VISITOR. BOOK THE ONES WHO ARE READY.
Deploy Crescelo on your website in 15 minutes
Train your assistant on your price lists, documents, and service policies. Enable 24/7 grounded answers and conflict-free in-chat appointment booking.