A chatbot human handoff is the moment a chat assistant stops being the only one answering and a person from the business takes over the conversation. In an online store, the handoff decides whether a shopper with a real problem gets help or leaves. A good handoff has five parts: a clear trigger, an honest wait, a useful context packet for the person, a fallback when nobody is free, and a clean return to the assistant.
This guide walks through each part with a concrete example. Runner AI turned on human help in its storefront shopper chat for every store owner on November 8, 2026. The example below describes that flow as it exists in Runner’s source code and interface text on that date.
Disclosure: Runner AI publishes this guide. The Runner details come from inspected source, tests, and interface text, not from customer results. Timing values and labels can change in later releases.
Key Takeaways
- Trigger a handoff when the shopper asks for a person in their own words, and also offer a visible button.
- Tell the shopper the truth about the wait. Never promise a reply time you cannot keep.
- Let the assistant keep answering simple questions while the shopper waits.
- Give the person who joins the cart, orders, and the reason for the request.
- Set a time limit, then move the reply to email instead of leaving the shopper waiting.
- Pause the assistant while a person is in the chat, and hand the chat back on purpose.
What is a chatbot human handoff?
A chatbot human handoff, also called a chatbot-to-human escalation, moves a conversation from an automated assistant to a member of the team. The conversation stays in the same chat window. The shopper should not need to repeat the question, open a new channel, or find a contact form.
In ecommerce, the common reasons are an order that went wrong, a refund or exchange that needs a decision, a product question the catalog cannot answer, and a shopper who simply wants to talk to someone. The ecommerce customer support playbook covers how to route those requests by risk. The handoff is the part of that routing that happens inside the chat itself.
When should the chatbot hand off?
Use two triggers, and keep both narrow.
The shopper asks in words. If the shopper writes “can I talk to a person” or “I need someone from the store,” the assistant should pass the request on once and say so. In Runner’s shopper chat, the assistant’s handoff tool is described to the model as one it may call “only when the shopper asks for a person, a human, staff, or the store team in their own words.” The assistant does not decide on its own that a shopper needs a person.
The shopper presses a button. A visible control removes guesswork. Runner’s storefront chat shows a “Talk to a person” chip under the conversation. The request is the same whether it comes from the button or from the shopper’s words.
Avoid triggers the shopper cannot see, such as a sentiment score or a count of failed answers. They hand off conversations the shopper never asked to escalate, and they leave the team with requests nobody can explain.
What should the shopper see while waiting?
The wait is where most handoffs fail. The shopper does not know whether anyone is coming, so they leave or ask the same question again.
Three rules keep the wait honest:
- Confirm the request in one line. Runner’s assistant replies “I’ve let the [store] team know. Someone will reply right here.” Its instructions tell it not to promise a time.
- Show the state in the chat header. Runner’s chat header changes from “AI assistant · A person can join” to “Waiting for a person · AI assistant can still help.”
- Keep helping. While the shopper waits, the assistant can still answer product, shipping, and policy questions. The request for a person stays open.
Ask for an email address during the wait, not before it. Runner asks “Where should we email the reply if you leave?” and lets the shopper skip it. The shopper can keep shopping, and the reply can still reach them.
If nobody on the team can reply in that chat yet, say so at once. Runner’s assistant answers “Nobody from the [store] team can join this chat yet, but I can keep helping you here.” It does not open a request that nobody can answer.
What does the team need when they join?
A person who joins a chat should not need to ask the shopper to repeat anything. Give them four things:
- The transcript. Every message, including the assistant’s answers.
- The reason. Runner’s handoff tool records one short line about what the shopper needs a person for. The merchant’s Customer chats page shows it as “Why [name] needs you.”
- The shopper’s context. Runner’s panel shows the shopper’s email, location, past orders, and this visit’s activity, such as items added to the cart, a started checkout, or a placed order.
- A way to share facts. The team can share a product or an order card into the chat, so the shopper sees the same price, stock, or delivery status the team sees.
The team also needs to know that a request exists. In Runner, a chat that asked for a person moves into a “Needs you” list in Customer chats and gets an “Asked for a person” tag. Team members can get an alert. The Runner AI app for iPhone, in beta on TestFlight at the time of writing, can send a ping when a shopper asks for a person.
Who is answering once a person joins?
Only one voice should answer at a time. If the assistant keeps replying after a person joins, the shopper gets two answers that may disagree.
In Runner, a merchant who sends a message joins the chat, and the assistant pauses. The merchant sees “Sending pauses Runner AI” before sending. The shopper sees a line such as “Sara from [store] joined,” and the chat header names the person who is there. The assistant’s history labels the team’s messages, so when it comes back, it does not repeat or contradict what the person said.
What happens when nobody replies?
Set a time limit. A shopper should never wait without an end.
Runner uses 15 minutes. If nobody from the team replies in that time, the assistant apologizes and moves the reply to email. With an email on file, it says the team will reply to that address. Without one, it asks the shopper to leave an email. The merchant’s timeline records “No one replied in 15 minutes · Runner AI promised an email reply.” The shopper is told the reply will also show in the chat if they come back.
The same rule applies when a store turns chat off. Shoppers who were still waiting stay in Customer chats, and the merchant’s replies reach them by email.
How does the chat return to the assistant?
Close the handoff on purpose. A chat that stays in “a person is here” state after the person has left is as confusing as a chat that never escalated.
Runner gives the merchant two actions:
- Hand back to AI. The person leaves, and the assistant answers again. The shopper sees “[Name] left the chat” and a note that the AI assistant is there if they need anything else.
- Resolve. The conversation is closed. If the shopper writes again, the assistant answers, and the merchant can reopen the chat.
After either action, the assistant knows that nobody from the team is in the chat and that no request is open. If the shopper asks whether someone is still coming, it answers no and offers to ask the team again.
A checklist for your own handoff
Test each case on your live chat before you rely on it:
- Ask for a person in words. Confirm the assistant passes the request on once and promises no time.
- Press the handoff button. Confirm the header changes to the waiting state.
- Ask a product question while waiting. Confirm the assistant still answers.
- Reply as the team. Confirm the assistant stops answering and the shopper sees who joined.
- Hand back and resolve. Confirm the assistant answers again and knows nobody is coming.
- Let a request go unanswered past the time limit. Confirm the shopper is told about email and the team can still reply.
- Leave the page before a reply arrives. Confirm the reply reaches the email address the shopper left.
For the broader question of where people should review AI work, see AI human in the loop. To see how Runner’s store assistant fits into a storefront, read the AI ecommerce chatbot feature page. The Customer chat switch itself is in Store → General, described in the store settings guide.
Related questions
What is the difference between a chatbot handoff and live chat?
Live chat means people answer every conversation. A chatbot human handoff means the assistant answers first and a person joins only when the shopper asks. The handoff lets a small team cover a store all day without staffing every chat.
Should a chatbot hand off automatically when it cannot answer?
Usually not. Let the assistant say what it does not know and offer the handoff button. An automatic handoff on every failed answer fills the team’s list with chats the shopper did not escalate.
How long should a shopper wait for a person?
Choose a limit your team can meet during open hours, show the waiting state the whole time, and move the reply to email when the limit passes. Runner uses 15 minutes. The right value for your store depends on your staffing.
Does the shopper need to give an email address?
Not to start the handoff. An email lets the reply reach the shopper after they leave the page or after the time limit. Ask for it during the wait and let the shopper skip it.
