Design a Website Chatbot Handoff That Keeps Enquiries Human
A chatbot flow framework for answering common questions and passing relevant enquiries to a person.
A website chatbot can help visitors find information, but it should not trap someone in a menu when they need a person. A good flow answers common questions, makes its limits clear and transfers context to a human when necessary. Amar Ajnalkar, digital marketing trainer and consultant, recommends designing the handoff before writing the first chatbot prompt.
Start with a small set of intents
Identify frequent questions the business can answer accurately, such as course details, service coverage, opening hours or how to contact support. Avoid automating complex advice or decisions that require personal context or specialist judgment.
Ask for the minimum needed
- Let visitors explore answers without sharing contact details where possible.
- Explain why information is requested before asking for it.
- Separate optional marketing consent from handling a support request.
- Do not request sensitive information in a general chat window.
- Provide a privacy notice and a way to leave the conversation.
Make the handoff reliable
Route unresolved questions to a named inbox or team, include relevant conversation context and confirm receipt to the visitor. Set realistic response expectations and provide another contact option if the team is offline.
Test and maintain the flow
Try common questions, typos, unsupported requests and handoff failures. Review unanswered questions for new FAQ ideas. Update answers when services or policies change, and make it easy to disable a broken flow.
Related guides: the FAQ planning article and the message-routing process.
A helpful chatbot reduces friction when it is transparent, limited to suitable tasks and connected to a real response owner.