Chatbots vs human handoff: what to automate and when to step in

The real question is rarely "bot or human?". It is which parts of a conversation a bot handles well, and how quickly and cleanly it gets out of the way when a person is needed. Get that split right and visitors get faster answers while your team spends its time on conversations that need judgment. Get it wrong and you build a maze that frustrates the people you most want to help.

What chatbots do well

Bots are good at short, predictable steps where the visitor knows the answer and you need it in a particular form.

• Qualifying. "Are you a current customer or looking to buy?" One tap tells you which team should answer.
• Routing. Topic buttons such as Billing, Technical help and Sales send the conversation to the right people from the start.
• Collecting details. Email, name, phone number, order number: asking for these up front saves a round trip later, and the email lets you follow up if the visitor leaves.
• Suggesting help articles. Many questions already have a written answer. Showing the right article immediately is faster than any human reply.
• After-hours intake. When nobody is online, a bot can gather the question and contact details so the morning shift starts with everything it needs.

What people do better

Hand anything that needs judgment, empathy or an exception to a person: an upset customer, a refund outside your usual policy, a bug report that needs follow-up questions, a large sales opportunity, or a question your help center does not cover. Bots are also poor at noticing when a visitor is getting frustrated, which is exactly when a person should step in.

Design flows with buttons

Buttons beat free text for the bot part of a conversation. They show visitors what you can help with, they cannot be misunderstood, and they make reporting simple because every answer falls into a known bucket. In TalkingDot, a chatbot flow is a series of steps: show buttons, collect an email, name, phone number or free-text answer, hand off to your team, or end the conversation.

A simple flow for a software business might look like this:

1. A greeting with three buttons: Pricing question, Help with my account and Something else.
2. Pricing question: ask for an email address, then hand off to the sales team.
3. Help with my account: ask the visitor to describe the problem in a sentence, then hand off to support. The description means the teammate who picks it up can answer straight away.
4. Something else: hand off straight to the general team. Never make people guess which category they belong in.

Alongside your flows, TalkingDot's answer bot suggests relevant help-center articles when a visitor asks a question, so many simple questions are answered before anyone needs to reply.

Avoid dead ends

A dead end is any point where the visitor cannot move forward: a bot that repeats "Sorry, I didn't understand", a branch that stops without an answer or a handoff, or a menu with no option that fits. These rules prevent most of them:

• Every branch ends in an answer, a handoff or a clear close. Walk every path yourself before you switch a flow on.
• Always offer a human. Put a "Talk to a person" or "Something else" button on every menu. Visitors who want a person and cannot find one leave annoyed, or come back angrier.
• Keep flows short. Two or three taps before a person or an answer is plenty. If a flow needs more, it is probably doing work a person should do.
• Treat typing as a signal. A visitor who ignores the buttons and types a question is usually asking for a human. Let a person pick it up.
• Be honest about hours. If the handoff happens after hours, say so and say when someone will reply, rather than implying a person is about to answer.

When to hand off

Hand off immediately when a visitor:

• asks for a person, in any words;
• has been through the same branch twice, or says an article did not help;
• mentions money going the wrong way, such as refunds, double charges or cancellations;
• is on a high-intent page such as pricing or checkout, where a fast human answer is worth the most;
• is an existing customer with an account problem that a help article cannot solve.

In TalkingDot, the handoff step passes the conversation to your team, and routing rules take it from there. A rule can look at the message, page, country, language, device or contact, then assign a team or teammate, add a tag, set the priority, send a reply or close the conversation. A good first rule: messages that mention "refund" or "charged twice" get high priority and go to whoever handles billing.

Make the handoff seamless

The worst handoff is the one where the visitor has to repeat everything. Whatever the bot collected should be in front of the person who picks up the conversation. In TalkingDot, the bot's questions and the visitor's answers sit in the conversation itself, and the contact sidebar adds location, local time, current page, page history, past conversations and custom attributes. The teammate can open with a real answer instead of "How can I help?".

Keep the first human message personal and specific. "Thanks, I can see you're asking about your March invoice; let me check that now" tells the visitor the handoff worked.

Measure whether it works

• CSAT. TalkingDot asks visitors to rate the conversation on a five-emoji scale when it closes. Tag conversations that went through a flow and compare their ratings with the rest.
• Handoffs by topic. If teammates tag conversations by topic, the tags report shows which topics keep reaching people. A branch where almost everyone asks for a person is not saving anyone time; replace it with a direct handoff or a better article.
• Unanswered conversations and first response time. A bot should never make these worse. If they rise after launch, handoffs are not reaching people quickly enough.
• Transcripts. Ten minutes a week reading bot conversations shows you where people hesitate, type instead of tapping, or give up.

To build your first flow, follow the chatbot guide, or see what else TalkingDot can automate on the automation features page. Workspaces are free, so you can try it with your own visitors.