When should a chatbot hand the conversation to a person?

A chatbot should not try to close every conversation. Some requests require judgment, access to private data, or authority to make a decision. In those cases, the better outcome is to recognize the limit and make it easy to reach a person.

Signals that call for a handoff

An important signal is an inability to answer from reliable sources. If a shopper repeats a question, corrects the response several times, or points out conflicting information, continuing to generate text increases frustration.

Other common cases include payment disputes, refund requests, order changes, personal data, policy exceptions, and issues with possible safety consequences. An emotionally sensitive request, or a shopper who explicitly asks for a person, should also lead to a clear route.

Automatic handoff and simple routing

An automatic handoff transfers the conversation and its context to a support system or an available agent. Simpler routing displays the correct channel, such as email, a form, or a telephone number, and leaves the shopper to start the contact. These are different experiences and should not be described as equivalent.

Valen provides chat on desktop and mobile.

A note on the current scope

Automatic transfer of the conversation to a support agent is not presented here as an available capability. This guide describes the behavior a store should design when it combines a conversational assistant with its own support channels.

Where Valen fits

The limitation is the boundary between storefront assistance and human ownership. Before routing a shopper elsewhere, the experience needs to preserve the product and the unresolved question. Valen lets shoppers search the catalog and ask product questions during the conversation, as demonstrated on a demo store. It also lets shoppers move between a quick product preview and chat without losing the product they were viewing, as demonstrated on a demo store. Valen is therefore more than an isolated chat during discovery, but it does not claim automatic human handoff here: the merchant must provide the contact channel, escalation rules, and any transfer of context.

What context should be transferred

When a handoff exists, the person should not make the shopper start again. A summary can include the contact reason, steps already attempted, products discussed, and the last unresolved question. Personal information and order details should be transferred only when necessary and in line with store rules.

The summary should distinguish what the shopper wrote from what the chatbot inferred. The support agent can then verify information quickly without treating an assumption as fact.

Design the wait and set expectations

If nobody is available in real time, the chatbot should say so clearly. Showing the channel, the required information, and what happens next is more useful than implying an immediate reply. Preserve another route for shoppers who do not want to continue in chat.

Define what happens after a technical error as well. The message should not disappear, and the shopper should be able to copy the summary or reach the support channel directly.

Test escalation rules

Build scenarios that include an explicit request for an agent, repeatedly incorrect answers, order problems, and out-of-scope questions. Confirm that routing happens early enough without escalating every simple request. Check that the transferred context is understandable, minimal, and accurate.

Track how many conversations are routed, why they are routed, and whether the shopper completes the contact. These signals can improve both the chatbot and the store's documentation.

Book a demo to see how conversation can fit into your store journey while keeping its boundaries clear.