DEV Community


Dialogflow Chatbot to Human Handoff

Devashish Datt Mamgain
Cofounder Building Human + Bot Hybrid Customer Support love building products and writes about technology
・3 min read

The chatbot to human hand-off plays an important role in customer support. It is useful when your chatbot is unable to understand the visitor query and fails to answer them.

Let say you visit a specific website that is empowered by chatbots. Assume that you ask a specific question to a chatbot but it fails to answer your question and keep on repeating the same response.

How does it feel? Don’t you get frustrated and leave the website immediately?

The same will applies to your website visitor also.

If your chatbot is unable to quickly handoff the unknown conversation to live agent and repeatedly saying the same thing then the visitor will get frustrated and may lead to less customer satisfaction and its bad reputation for your company which might affect your revenue as well.

So your chatbot should be brilliant enough to identify when it should hand off the conversation to a human agent and ensure that the end-user experiences a smooth transition.

When does human handoff should occur?

1. Tricky and tough situations

Usually, the chatbots are trained to help the users with answering their basic queries. If the end-users issue is complex and the chatbot is not able to provide any solution then it should involve a human agent to help the end-user with the complex issue.

In dialogflow, the action “input.unknown” used to handoff the conversation to a support agent. Whenever action “input.unknown” is detected in the response, Kommunicate automatically assigns a conversation to a support agent based on the configured conversation routing rules from the dashboard.

You can add an action “input.unknown” to any intent to handoff the conversation to a human agent.

The “input.unknown” action is built into Dialogflow and used with the default fallback intent. When none of the intents are matched, the default fallback intent is triggered and action associated with it is added in the response.

Dialogflow Default FAllback intent: input.unknown

2. Depending upon the User requirements

There are some scenarios the end-user doesn’t want to wait for the bot to help with his issue or query and will be looking for a human agent. In that time the user should be given an option to directly talk to a human agent. This can be done with the help of menu options or rich messages.

Here is an example, when the user clicked on the button “Talk to Human” the bot handoff the conversation to the agent.

Bot to human handoff example with Kommunicate

Below is the example for Dialogflow custom payload to add above shown menu option for transferring conversation to a human agent.

Below is the example for Dialogflow custom payload to add above shown menu option for transferring conversation to a human agent.

Custom Payload for human handoff

Here, talk_to_human is mentioned as a follow-up, and the payload is passed to it.

talk_to_human followup

3. Human handoff based on keyword trigger

There are some cases where the bot should be able to handoff conversation to a human agent based on the keywords trigger. For example, when the user types words like a human, support, agent, etc.

Here’s an example where the user typed “human” and the bot handover conversation to a human agent.

Example of user handoff by typing human

The corresponding Dialogflow intent and the custom payload are as follows.

Dialogflow Training phrases sample

If you’re using Kommunicate then there is a simple option to do the bot to human handoff. While integrating your bot in Kommunicate, you will be asked to enable the bot to human handoff in the last step.

Kommunicate ready to use Bot to Human handoff settinng

These are the possible scenarios where a chatbot should be able to handoff conversation to the human agent from Dialogflow after integrating with the Kommunicate.

This post is originally published in Kommunicate Chatbots Blog

Discussion (0)