Know when an answer is not enough
A chatbot can explain a policy without being able to approve an exception. It can point to troubleshooting steps without having access to a customer’s account. Those boundaries matter most when the customer is already frustrated.
Define escalation cases before launch. Account access, payment disputes, sensitive information, and repeated unsuccessful troubleshooting are good situations to review with your team. The right boundary depends on your product and the authority you give the agent.
Make the route to a person obvious
Let customers ask for a human directly. Do not require them to fail several automated steps first. A handoff message should explain what is happening and where the reply will appear.
Avoid promising an immediate human response if nobody is staffing the inbox. If your team follows business hours, make that expectation clear in your instructions and customer-facing copy. A candid next step is more useful than an invented response-time estimate.
Transfer context, not just a notification
Your teammate needs the original question, the answers already offered, and the reason the conversation needs attention. Asking the customer to repeat the entire problem creates unnecessary work for both sides.
Helpnest keeps the conversation in the shared inbox when it moves to a person. Team members can read the history and reply in the same thread. The AI pauses while a human handles the conversation. See the inbox and handoff guide for the available controls.
Decide who owns the next reply
A shared inbox still needs a working agreement. Decide who checks incoming handoffs, how urgent requests are recognized, and when a thread should be closed or returned to the AI. Try the full flow with a teammate before announcing the chatbot to customers.
Review how the greeting, AI instructions, and human replies fit together. The experience should feel coherent even though different people and systems are participating.
Use escalations to improve the knowledge base
Not every handoff is a failure. Some cases should always need judgment or account access. Separate those from questions that escalated because the documentation was incomplete.
For a repeated documentation gap, add or clarify a source and test the question again. For a case that needs a person, improve the routing instructions. Tracking both outcomes helps you improve support without trying to automate decisions that need human authority.
Build on what you know.
See the setup workflow in our docs, or join the Helpnest waitlist.
Read the quickstart →