AI help desk with human handoff: what it should do, and when to pass to a person
An AI help desk for a small business has one job beyond answering: making sure nothing a customer asks gets lost. It answers what your own content covers, does the simple next step in the chat, and passes everything else to a person with the conversation attached. This guide covers what that looks like, what to check before you trust one, and how CAAC Go does it.
The short answer
- Answer only from your own content. If the answer isn't there, it should say so, not guess.
- Do the next step in the chat. When a visitor leaves their details, save the lead. When they ask for a time, take the booking request.
- Hand off at the right moments: the answer isn't in your content, the visitor asks for a person, or they're upset.
- Tell both sides what happens next. The visitor hears that the team will follow up; your team gets the exact question.
- Learn from each handoff, so the same question doesn't need you twice.
Every conversation ends one of four ways
| What the visitor needs | What the AI should do | What your team sees |
|---|---|---|
| A question your content answers | Answer in a few sentences | Nothing to do: the chat is "Resolved" |
| A quote, a callback or an appointment | Save the lead or the booking request in the chat | A "Lead" entry and an email |
| Something your content doesn't cover | Say the team will check, and ask how to reach them | A "Follow up" badge and an email with the exact question |
| A person, or help with a complaint | Bring in your team | A flagged conversation in Inbox |
Off-topic requests ("write my essay") get a polite no. They are not handed off, so your team only sees conversations about your business.
When should an AI hand off to a human?
Three moments, every time:
- The answer is not in your content. A good help desk never fills the gap with a guess about prices, hours or policies.
- The visitor asks for a person. Arguing with someone who wants a human costs more than it saves.
- The visitor is upset. Complaints, refunds and anything sensitive belong with your team.
Some topics should go to a person even when the AI could say something: medical advice, special pricing, legal questions. Write those rules into the AI's instructions.
Five things to check before you trust one
- It says "I don't know". Ask something your site doesn't cover. It should hand off, not invent an answer.
- It saves the lead when the details are already there. Put your name and email in your first message. It should save them, not ask for them again.
- The handoff reaches someone who will see it. An email, a badge in an inbox, ideally both.
- A person can take over and the AI stops talking. Two voices in one chat confuse customers.
- Each handoff becomes something you can teach, so next time the AI answers it.
How much the AI model matters
In the CAAC Go Agent Benchmark (November 2026), we sent the same 24 "please contact me" and "book me in" messages, each with a name and contact details already in it, through the same website agent running eight leading AI models. Claude Fable 5.2 and Claude Opus 5.5 saved all 24. GPT-6 Astra and GPT-6.1 Sol saved 7: they kept asking for a second way to reach the visitor first. Same agent, same instructions; only the model changed. Handing off at the right moment is tested the same way.
How CAAC Go does it
- Answers from your content. Train it on your website, text, Q&A pairs and files. It answers in the visitor's language. See how to train your AI agent.
- 🎯 Capture lead and 📅 Request appointment save the visitor's details and booking requests, and email you. Both are on by default on every plan. See how to capture leads and booking requests.
- 🤝 Bring in your team flags the chat when a visitor asks for a person or is upset, and collects their contact details. When the AI can't answer from your content, it hands off on its own and emails you "Your AI got stumped — here's the exact question".
- One inbox for your team. Click Take over to reply yourself; the AI pauses until you click ✨ Hand back to AI. See how AI to human handoff works.
- Teach it from the handoffs. Every handed-off question appears under Data sources → Suggestions, where Add to knowledge turns your answer into content.
- Send it to your own systems. On paid plans, a custom API action lets the agent call any HTTP API you define, for example to create a ticket in your help desk or look up an order.
Good fit and watch-outs
Good fit
- Small teams that answer the same questions every day.
- Service businesses that take enquiries and bookings through their website.
- Teams that can reply to a handed-off chat within a working day.
Watch-outs
- There is no business-hours setting. The AI answers 24/7, and handed-off chats wait until someone on your team replies.
- Booking requests are requests. Your team confirms the time; CAAC Go doesn't write to a calendar.
- Order status, tracking and tickets in another tool need a custom API action on a paid plan.
Common questions
Is an AI help desk the same as a chatbot?
Not quite. A chatbot answers. An AI help desk also does the next step and passes the rest to a person. See chatbot vs AI agent.
What does the visitor see when the AI hands off?
The AI tells them your team will check and asks for their name and a way to reach them. Your team gets the conversation and the exact question.
Can it create a ticket in my help desk tool?
Yes, with a custom API action on a paid plan: you define the call to your help desk's API, and the agent decides when to use it. Without one, handed-off chats stay in the CAAC Go Inbox and arrive in your email.
Which plans include handoff?
All of them, including Free: 🤝 Bring in your team, the Inbox with Take over and ✨ Hand back to AI, and the handoff emails.
Try CAAC Go on your website, no signup. Related: how AI to human handoff works and how to capture leads and booking requests.
Try it on your website
Paste your link and ask your own AI agent anything. Free, no signup.
Keep reading
Last updated 2026-11-16