AI Chat vs Human Support: When to Hand Off
An AI chat should hand the customer to a person when the topic is risky, the customer is upset, the AI is unsure, or the customer asks for a human. Here are clear triggers and a simple setup.
An AI chat should hand over to a human in four cases: the customer asks for a person, the customer is upset, the topic carries legal or financial risk, or the AI is not sure of its answer. A good handoff also passes on the full conversation, so the customer does not repeat anything. Set these triggers before launch, and review them every month.
Why the handoff matters
An AI chat is fast and always available. A person is better at judgment, empathy and exceptions. Most good support setups use both.
The handoff is the point where these two parts meet. If it works well, the customer barely notices. If it fails, the customer is stuck in a loop with a bot. That is the moment people remember.
Trigger 1: The customer asks for a human
This is the simplest rule. If a customer writes "agent", "human", "person" or a similar request, hand over. Do not argue and do not ask the customer to try the bot first.
Make the option easy to find. A visible button such as "Talk to a person" is better than a hidden phrase. Also add a rule to the AI: it must never refuse this request.
Trigger 2: The customer is upset
Signs of strong emotion include:
- Angry words, insults or many exclamation marks.
- The same question asked three times in different words.
- Words such as "complaint", "lawyer", "fraud" or "scam".
- A very long message that describes a bad experience.
An AI can detect these signs with simple rules or with a classifier. When it finds them, it should say a short, calm sentence and hand over. A long apology from a bot often makes things worse.
Trigger 3: Risky topics
Some topics must go to a person, even if the AI could write a reasonable answer. Define a list for your store. Common entries are:
- Refund disputes and chargebacks.
- Damaged, wrong or missing items with a claim for money.
- Legal questions, such as warranty rights or contract terms.
- Data requests under GDPR, such as access or deletion.
- Allergies, safety or health questions about a product.
- Business customers who ask for special terms or large orders.
- Any message that contains a threat or a safety concern.
For these topics, the AI can still help. It can collect the order number and a short description, then pass the case on. The decision stays with a person.
Trigger 4: The AI is not sure
The AI should not guess. Set a rule: if the answer is not clearly in the sources, say so and offer a handoff.
Practical checks:
- The search finds no relevant source for the question.
- The sources contradict each other.
- The question asks for a price, stock level or date that the AI cannot read from live data.
- The AI has failed to solve the problem after two or three tries.
A short rule like "After two failed answers, offer a person" prevents long frustrating chats.
Trigger 5: Account and order checks fail
If the customer cannot prove who they are, the AI must not show order details. Offer a handoff or a secure way to verify. This also protects you from people who try to get data about other customers.
How to build a good handoff
A trigger is only half of the work. The handoff itself needs care.
- Tell the customer what happens next. Say "I will pass you to a colleague" and state the expected wait.
- Send the full conversation to your team. The customer should not repeat the story.
- Add a short summary: who the customer is, the order number, the issue and what the AI already tried.
- Respect opening hours. If nobody is available, offer a contact form or email and a clear reply time that you can keep.
- Keep the chat open or send a confirmation email, so the customer knows the request arrived.
- Mark the case with the trigger that fired. You will use this data later.
Measure and improve
Look at the handoff data every month. Read a sample of chats that were handed over and chats that were not.
- Handoffs that happened too late show that a trigger is missing or too weak.
- Handoffs that happened too early show that the AI lacks a source. Add the missing content.
- Chats that ended without a handoff but with an unhappy customer need a closer look.
The goal is not the lowest handoff count. The goal is the right handoff at the right time.
Frequently asked questions
What share of chats should go to a human?
There is no correct number. It depends on your products, your content and your customers. Track your own rate over time and read the cases, instead of copying a target from another store.
Should the AI always offer a human at the start?
Not always, but the option must be easy to find in every chat. Many stores show a button for it in the chat window. This avoids the frustration of a bot that blocks the way.
What if no human is online?
Say so clearly. Offer a contact form or email, and give a reply time you can meet. Do not let the AI pretend to be a person or promise things it cannot do.
Can the AI approve refunds on its own?
You can allow it only with strict rules, limits and logs. For most small stores, it is safer to let the AI collect the facts and let a person decide. Review this choice with your team.
Automate the routine, keep the human touch
2folk builds commerce automation tools for Shopify and WooCommerce merchants in the EU.
See our products →