Short answer
In four cases: when the visitor asks for it, when the answer is not in its documents, on topics the organization keeps for a person, and when the conversation shows an unhappy customer. The handover works when the person reads the whole conversation and answers in the same window, without making anyone repeat.
Key takeaways
- The assistant hands over when the visitor asks, when the documents are not enough, on reserved topics and when the exchange becomes tense
- A good handover says who, what, why, what has already been said and in which language
- The visitor must know who will reply and within what realistic time, including outside opening hours
- Emergencies and safety get a fixed answer approved in advance, with 112
- Review handovers every week: they show which documents to write
Contents (18)
- When should an AI assistant hand over to a person?
- Why human handover matters as much as the answers
- How does the assistant spot that it should hand over?
- What makes a good human handover?
- What does the visitor see at the moment of handover?
- What should the assistant do outside opening hours?
- Which requests can you leave to the assistant?
- Which information should you pass on without asking for too much data?
- Who takes over what in the team?
- What can you learn from conversations taken over by the team?
- How do you keep a conversation from going unanswered?
- A handover done well, from first message to reply
- Giving control back to the assistant after the handover
- Prepared replies for the team
- How many people do you need behind the assistant?
- Handover and data protection
- Common mistakes in organizing handover
- How do you prepare a human handover that works from launch?
When should an AI assistant hand over to a person?
The assistant should hand over when the visitor asks for it, when the documents are not enough, when the subject is reserved for the team or when the exchange goes wrong. These situations must be planned in the initial instructions:
- The visitor asks for it: "I would like to speak to someone" calls for a handover, without forcing them to carry on with the assistant
- The answer is missing from the documents: the assistant acknowledges the limit and offers to pass the question on
- The subject is reserved for a person: disputes, complaints, commercial decisions and safety follow the rules set by the organization
- The customer is unhappy: a repeated complaint or persistent tension calls for a person, even if a document-based answer exists
Handing over to the team must remain possible even if the assistant thinks it has answered. The visitor may need a decision, a confirmation or a listening ear that documents cannot provide.
Why human handover matters as much as the answers
An AI assistant is judged on its good answers, but it is often remembered for its dead ends. A visitor who goes round in circles, repeats their question three times or finds no way of reaching a person keeps a poor image of the business, even if the assistant answered nine questions out of ten correctly.
Human handover is therefore part of the service, not an admission of failure. It also protects the business: commercial decisions, complaints and safety questions stay in the hands of people who have the authority and context to handle them. An assistant that knows when to stop avoids made-up answers where they would cost the most.
Finally, every handover is information. It shows what the documents do not cover, what visitors expect and where the decisions lie that cannot be automated. A business that reviews its handovers improves its assistant faster than one that only deals with them one by one.
How does the assistant spot that it should hand over?
The assistant spots the need for a handover from signals written into its instructions. Some are explicit, others need a finer rule:
| Signal | Example visitor message | Rule to write in the prompt |
|---|---|---|
| Direct request | "I want to talk to a human" | Hand over immediately, without insisting |
| Question outside the documents | A question about a service the documents do not describe | Say the information is missing and offer a handover |
| Sensitive keyword | "complaint", "lawyer", "refund", "gas leak" | Hand over according to the rule set for that topic |
| Repetition | The visitor rephrases the same question for the third time | Offer a handover rather than a fourth answer |
| Tension | Capital letters, reproaches, threats to leave | Acknowledge the problem and offer a person |
| Decision requested | "Can you give me a price?" | Collect the need and pass it on |
The repetition rule is often forgotten. An assistant that gives a correct answer three times to a visitor who does not find it satisfactory solves nothing: the real need lies elsewhere, and a person will find it faster.
Emergencies and safety
Some messages cannot wait for the team's reply. A smell of gas, a major water leak, a dangerous electrical problem, someone feeling unwell. For these situations, the prompt must provide a fixed answer approved in advance: the safety steps published by the business, the business's emergency number if it has one, and a reminder of the public emergency numbers (112 in Belgium). The assistant must neither play down the situation nor improvise a diagnosis. Plumbers and installers receive this kind of message more often than people think.
What makes a good human handover?
A good human handover passes on the history and the question to be handled so the visitor has as little as possible to repeat. The conversation arrives in a shared inbox; a person picks it up, reads the exchanges and replies in the same window.
Internal notes, invisible to the visitor, let the team pass the baton. They should distinguish the facts given by the customer, the information already checked and what remains to be decided. An assumption written down as a fact risks producing an unsuitable reply.
In a fictitious example of a Brussels property manager, a tenant disputes service charges. The colleague who takes over must find the question, the explanations already given and the document cited. They do not need an automatic conclusion on whether the dispute is valid: that judgement belongs to the competent person.
What a handover should contain
A useful handover fits in a few lines and answers five questions:
- Who: the name and contact details, if the visitor gave them
- What: the request summed up in one sentence, in the visitor's words
- Why the handover: missing information, decision, complaint, explicit request
- What has already been said: the assistant's answers and the sources cited
- The language of the conversation, so the right person takes over
The team should be able to decide in thirty seconds who takes the request and what to check before replying. If it has to reread the whole conversation to understand the need, the handover is too thin.
What does the visitor see at the moment of handover?
The visitor must understand what is happening, who will reply and when. Three elements are enough: a sentence announcing the handover, an honest indication of the timing and a confirmation of what the team has received.
Compare two holding messages. The first: "I am passing on your request." The second: "I am passing your question about the service charge dispute to the management team. They usually reply within the working day; you will receive the answer here and by e-mail at the address you gave." The second reassures, avoids a follow-up and sets a realistic expectation.
If the team is available in real time, the conversation can switch to live chat: a colleague replies in the same window while the visitor is still on the website. Otherwise, the handover becomes asynchronous: the reply comes later, through the conversation or by e-mail. Both are legitimate, provided the visitor knows which one applies.
What should the assistant do outside opening hours?
Outside opening hours, the assistant should explain when the team is available, collect the useful contact details and leave the request waiting to be picked up. It can state the next reply window if that information is defined and kept up to date.
The inbox must make it possible to spot waiting conversations, with a target time and an organized follow-up if no one picks them up. That time remains an internal goal as long as the business has not decided to make it a commitment to the visitor.
In a fictitious example of a plumber in Namur, a message sent at night can prepare a call-back request. It does not count as confirmation of a call-out. Requests involving safety must follow the instructions approved by the business; the assistant must not improvise a remote diagnosis to make up for the team's absence.
Public holidays and time off
Opening hours change on public holidays, during the summer break or for an annual closure. An assistant that announces "reply tomorrow" on 24 December creates a disappointed expectation. Keep a calendar of closures up to date and give it to the assistant, with the date the team returns. Also think about absences in the team: if the only person who speaks Dutch is on leave, the assistant must know it or not promise a reply in that language.
Which requests can you leave to the assistant?
Leave to the assistant the requests covered by reliable information whose answer does not involve a decision reserved for the team. This grid helps set the scope before launch:
| Situation | Assistant's role | Reason for handover |
|---|---|---|
| Opening hours, address, published procedure | Answer and cite the source | Information missing or contradictory |
| Preparing a sales request | Collect the useful need | Negotiation or tailored commitment |
| Question about a personal invoice | Point to the right procedure | File needs checking |
| Complaint about a service | Acknowledge receipt and pass on the context | Decision or disagreement to handle |
| Availability of a call-out | Explain how it normally works | Confirmation impossible with the information available |
| Request for a human contact | Hand over | The visitor's explicit choice |
In a fictitious example of an accounting firm in Liège, explaining how to submit a document can be the assistant's job. Interpreting a client's tax situation requires the firm to examine the file. The grid must reflect the real responsibilities of your trade.
The case of sales requests
Prospects often ask questions the assistant can partly answer: services offered, area covered, public prices, usual lead times. What comes next needs a person: a quote, a visit, a negotiation. The assistant's role is then to prepare the request so that the first human contact is useful, which is called lead qualification.
Plan three or four questions at most, suited to your trade: the type of need, the location, the desired timing, a way to get in touch. A form disguised as a conversation, with ten questions in a row, drives visitors away. The assistant then passes on the request with this information, and the person who calls back already knows what it is about.
Which information should you pass on without asking for too much data?
Pass on only the information the person taking over needs: the need, the useful context, the answers already given and a way to get in touch if necessary. Do not turn the handover into an exhaustive form.
In a fictitious example of a shop in Brussels, a question about opening hours does not require the visitor's identity. A question about an order may require a useful reference, depending on the team's procedure. Explain why you are asking for this information and avoid requesting sensitive documents in a general conversation.
Contact memory must stay separate from the context needed for the current request. Keeping preferences for future exchanges requires explained consent. Asking for a call-back is not an invitation to keep every detail of the conversation to personalize the service.
Who takes over what in the team?
In an SME, the same person often takes over everything. As soon as the team has three or four people, a simple split avoids duplicates and forgotten requests. Three criteria are usually enough:
- The topic: sales questions go to the person who writes the quotes, technical questions to the technical lead, complaints to the manager
- The language: a conversation in Dutch goes to the person who speaks it, if only one person does
- Urgency: requests involving safety or an existing customer in difficulty come first
Write this split in a note the whole team can see and in the assistant's handover instructions. A request classified correctly from the start goes straight to the right person, without internal transfers.
What can you learn from conversations taken over by the team?
Conversations taken over show missing information, ambiguous rules and decisions that must remain human. An unanswered question can become a knowledge suggestion to be approved by a person in charge.
If customers often ask how to prepare for an appointment, a written answer can reduce repetitive exchanges. If the requests concern commercial exceptions, passing them on may well remain the right way to work. The goal is therefore not to eliminate every handover.
This review also helps limit made-up answers. Before adding knowledge, check that it is general, current and shareable. The answer given to settle one particular file does not automatically become a rule for all customers.
The figures to track
A few simple figures are enough to manage handovers:
- The share of conversations taken over, and its breakdown by reason: missing information, decision, explicit request, complaint
- The time to the first human reply, during and outside opening hours
- Conversations left unanswered for more than one working day
- Handovers that could have been avoided with a document, spotted during review
A handover share that falls thanks to better documents is progress. A share that falls because the assistant no longer offers a handover is a problem. The resolution rate is never read alone: it is read with the quality of the answers and the satisfaction of visitors who were taken over.
How do you keep a conversation from going unanswered?
Avoid forgotten requests by clearly assigning responsibility for the inbox and reviewing conversations that are waiting for action. Plan a stand-in for absences and notes precise enough for a colleague to carry on.
In a fictitious example of a coliving house in Ghent, a question about a special arrival may involve both reception and the manager. Name the person responsible for replying to the resident, even if they need to consult a colleague. This reduces the risk that everyone thinks someone else is dealing with it.
An event can also notify another tool when a request needs following up. A webhook is an automatic message sent to that tool after an event. A CRM, customer relationship management software, can thus receive the information useful for follow-up. Check the recipient and limit the data sent; sending a notification does not prove that a person has picked up the request.
A handover done well, from first message to reply
Take a fictitious electrician in Mons, with a team of four. On a Thursday at 9 pm, a visitor writes: "My circuit breaker trips as soon as I turn on the oven, can you come round?"
The assistant first answers with the safety steps published by the business: do not keep resetting the breaker, unplug the appliance concerned, call 112 if there is a smell of burning or smoke. It then explains that the team schedules call-outs during opening hours, from 8 am to 5 pm, and offers to pass on the request. The visitor agrees and gives their name, municipality and number.
On Friday at 8 am, the request appears in the inbox with a clear handover: "Breaker trips when the oven is switched on, since last night. Visitor in Jemappes. Safety steps given. Asks for a visit. Conversation in French." The person in charge of scheduling picks up the conversation, offers two slots in the same window and confirms by phone. The assistant promised nothing; it prepared a request that the team handled in five minutes instead of an exploratory call.
The following Monday, reviewing the week's handovers, the manager notices three requests of the same kind. She adds a page "What to do if your circuit breaker trips" to the documents, reviewed by a technician. The next visitors get a fuller explanation before the handover even happens. The situations an electrician faces lend themselves well to this kind of preparation.
Giving control back to the assistant after the handover
Once a person has taken over the conversation, the assistant must stay silent. Two voices answering at the same time, one human and one automatic, create confusion and contradictions. The rule is simple: when a colleague has picked up the conversation, the assistant no longer replies in it.
After it is closed, if the visitor comes back with a new question, the assistant can resume its normal role. It must then take into account what the team said, without repeating or contradicting its commitments. A summary of the handover in the conversation history helps keep this consistency.
Prepared replies for the team
The people who take over conversations often answer the same kinds of request: confirming an appointment, asking for a missing document, explaining a lead time, acknowledging a complaint. Prepared replies, written once and adapted to each case, save time and keep a consistent tone across the team.
Write them in each language of the service, with clearly marked fields to fill in: the first name, the date, the reference. Review them when your terms change, just as you review the assistant's documents. A prepared reply that quotes an old rate does as much damage as an outdated document. Start with five or six replies, the ones the team types most often, and add to the list over the weeks.
How many people do you need behind the assistant?
The assistant reduces repetitive questions, but it does not remove the need for available people. To estimate the workload, start from your current figures: the number of requests received per day, the share the assistant should settle alone after a few weeks and the average time of a handover.
Fictitious example: 40 conversations a day, half of them settled by the assistant. That leaves 20 handovers, at five minutes each if the handover is well prepared, so less than two hours a day spread across the team. The real figure will be different for you, but this calculation lets you decide who watches the inbox and when, rather than finding out after launch.
Handover and data protection
A handover moves personal data around: a name, a number, the description of a situation. A few simple rules limit the risks. Only the people who take over conversations should have access to them. Internal notes should not contain personal judgements about the visitor. Conversations are not copied into personal messaging apps. And the retention period also applies to conversations taken over. The article on AI assistants and the GDPR covers these points for the assistant as a whole.
Common mistakes in organizing handover
- Hiding the contact button to keep visitors with the assistant: they leave, often for a competitor
- Promising a response time the team does not meet: "reply within the hour" becomes a source of complaints
- Handing over without context: the team has to ask everything again, the visitor repeats themselves, the handover loses its point
- Asking for too much information before handing over: the visitor gives up before the end
- Leaving the inbox without an owner: everyone assumes someone else is dealing with it
- Never reviewing handovers: the same questions keep coming back, for lack of a document
How do you prepare a human handover that works from launch?
Prepare the reasons for handover, the hours, the responsibilities and the holding messages before publishing the assistant. Test a common request, a missing piece of information and a complaint to check that what follows is clear.
A simple test is to play the visitor for half an hour, with a colleague on the other side. Ask a covered question, a question absent from the documents, a complaint, a quote request and a request to speak to someone, in English and then in French or Dutch. Each time, check what the visitor sees, what the team receives and how long it takes to reply. This half hour usually reveals two or three settings to fix before launch.
KernChat, KERN-IT's Belgian platform in Brussels, starts with a one-hour audit to define how this works with your team. Its handover features bring together a shared inbox, internal notes, prepared replies, opening hours and a target time; the monthly review then helps improve the documents and the instructions.