Building a Support Chatbot Flow with Handoff to an Agent or a Ticket

A good support bot doesn't replace your agents; it takes over repetitive work and delivers the important work to an agent intact. The worst case is a bot that traps the customer in an endless menu. In this guide we build a flow that either solves the problem or hands the customer over to an agent, or as a ticket, without making them repeat their story.

For the basics of building a bot, see also Build a chatbot without coding. Here we focus on handoff and measurement.

Step 1: List the most frequent questions

From the past month of conversations, write down the 5 to 8 most frequent questions: order tracking, working hours, return policy, forgotten password. Each becomes a "topic" in the main menu. More than 8 options in the first menu confuses customers.

Step 2: Write a short answer for each topic

End each answer with the question "Did this help?" If the answer is yes, the flow ends; if not, the flow moves to the next step, the handoff. This same question later shows in the report which answers actually help.

Step 3: Collect the required information before the handoff

Use the "collect information" step to get an email, order number, or date, so the agent (or the ticket) has everything from the start. Turn on format validation so an invalid email can't be entered.

Step 4: A working-hours condition

Use the "condition" step to split the flow based on working hours:

• During working hours: connect to an agent or the right team.
• Outside working hours: create a ticket, since you can't promise an instant reply.

Step 5: Handoff to an agent or a ticket

• To an agent: when someone is online and the issue is urgent; connect to one agent or a team.
• As a ticket: when the request needs investigation or nobody is online. The "action" step can create a ticket, add a tag, or set a priority; for example, a "payment problem" request with high priority. About tickets

A simple rule: no flow should be a dead end. Every branch that can't answer must reach a handoff. The editor flags incomplete steps before you publish.

Step 6: Test in the simulator

Before publishing, walk through the flow like a customer: every branch, every wrong option, and outside working hours. Keep versions so you can roll back to the previous one if something goes wrong.

Step 7: Publish and improve with analytics

After publishing, check the following in the bot flow analytics:

• Funnel: what percentage of customers reach each step.
• Drop-off at each step: where do they give up? That step is probably unclear or too long.
• Resolved-in-flow rate vs. handoff rate to an agent: if handoffs are high, add the unanswered questions to the flow.
• Handoff reason: for example "the answer didn't help" or "outside working hours".

Fix one step each week and measure again.

Common mistakes

• Long menus and long answers.
• No way out to a human. A customer who is unhappy with the bot gets even more unhappy.
• Handoff without information. The agent has to ask everything again.
• Publishing without testing and having no previous version to go back to.

Checklist

1. 5 to 8 frequent questions; one topic for each.
2. A short answer plus the "Did this help?" question.
3. Collect an email or order number before the handoff.
4. A working-hours branch: agent or ticket.
5. Simulator, then publish.
6. Weekly review of the funnel and drop-off.

To see all the features, check out the chatbot flow builder, and use the demo form to ask us to build your flow together.

Frequently asked questions