# Smart Escalations: When an AI Agent Should Hand Over > When an AI agent should hand a conversation to a person: upset customers, questions it can't answer, sensitive topics and big buyers. How to set the rules Canonical: https://maxbound.ai/blog/knowing-when-to-pass-the-mic-smart-escalations-for-ai-agents Last updated: 2026-10-19 Published: 2026-02-25 Updated: 2026-10-19 Author: Baban Rashid Category: [AI Agents](https://maxbound.ai/blog/category/agents) Tags: Human Handoff, Escalation, AI Agents, Customer Experience An AI agent should hand a conversation to a person in four situations: the customer is upset, the question needs an answer it doesn't have, the topic is one a person must decide, or the person is a big buyer worth a human touch. Everything else, the routine questions with one right answer, it can handle on its own. How it hands over matters as much as when. A good handoff tells the customer a person is coming, gives that person the whole conversation and the reason it was passed on, and stops the agent replying in the meantime. A cold transfer, where the customer has to start again, is worse than no agent at all. ## The four reasons to hand over **They're upset.** Anger, frustration, sarcasm, "this is the third time I've asked". The agent can acknowledge it, but a person should reply. Upset customers want to be heard by someone who can do something. **It doesn't know.** The answer isn't in the client's facts, or the question is unusual enough that a guess would be risky. Saying "a person will confirm that" is always better than inventing an answer. **A person must decide.** Refunds, discounts, exceptions, anything legal or medical, press enquiries, anything about a member of staff. These aren't hard for an agent to answer; they're not the agent's to answer. **It's a big buyer.** A wholesale order, a corporate booking, a wedding for 200. The agent can gather the details, then a person should take it from there. ## Write the rules per client Each client draws these lines differently. A clinic sends anything about symptoms to a person; a restaurant sends large group bookings; a shop sends anything about a damaged order. Write the list with the client before the agent goes live, and test it on their real past messages to check every conversation that should reach a person does. How to run that test is in [how to test an AI agent before it answers customers](/blog/how-to-stress-test-ai-agents-before-go-live). ## A handoff, not a cold transfer Three things make the difference: 1. **The customer knows.** "I'm passing this to the team, someone will reply here shortly." Honest, short, and it stops them asking again. 2. **The person has everything.** The whole conversation, what the agent already said, and why it handed over. 3. **The agent steps back.** Once a person is on it, the agent should stay quiet in that conversation, or the customer gets two answers. See [avoid double replies](/blog/stop-stealing-your-ais-thunder-introducing-avoid-double-reply). Then someone has to actually reply. A handoff into an inbox nobody watches is the worst outcome: the customer was promised a person and got silence. Decide who picks up handoffs for each client, and how fast. If it's outside working hours, the holding message should say when to expect an answer. On Instagram and Messenger, a person can still reply up to seven days later through Meta's [human agent](https://developers.facebook.com/docs/features-reference/human-agent) permission, but the customer won't wait that long happily. ## Handing over in public comments A complaint under a post or an ad is different from one in a DM, because everyone reading the thread sees what happens next. The safest rule is that a person writes the public reply to a complaint, even if the agent handles everything else. One calm, specific line in public ("Sorry about this, we've messaged you to sort it out today"), then the details in a private message. The agent's job there is to spot the complaint quickly and get it in front of someone, not to answer it. ## Handing back to the agent Once a person has dealt with the issue, the conversation doesn't need to stay with them forever. If the same customer comes back next week asking about opening hours, the agent can answer. In Maxbound, the agent pauses in a conversation for an hour after a team member replies, then picks up again if the customer writes later. That keeps people on the hard part without making every past complaint a permanent manual case. ## Signs the rules need adjusting Rules that are too tight send routine questions to people: the team spends its day answering opening hours that the agent could have handled, and the time to reply to real handoffs grows. Rules that are too loose let the agent answer things it shouldn't: you'll see it in the weekly review as replies about refunds, discounts or complaints that a person should have written. Read twenty handoffs and twenty unescalated conversations each week for the first month; the pattern shows quickly. ## Set it up for a client **Set up escalation rules for a client's AI agent** 1. **List the topics a person decides** — Refunds, discounts, complaints, anything legal or medical, press, staff, and the client's own sensitive subjects. 2. **Define a big buyer** — What makes a conversation worth a human touch for this client: order size, group size, or a business enquiry. 3. **Write the holding message** — What the customer is told when a conversation is handed over, including when to expect a reply outside working hours. 4. **Name who picks up** — A person for each client, how fast they reply, and who covers when they're away. 5. **Test on real messages** — Replay past conversations and check every one that should reach a person does, and nothing else. 6. **Review handoffs weekly** — Look at why each conversation was handed over. A question that keeps escalating is often a fact missing from the agent's knowledge. ## Tune it over time Watch two numbers per client. The share of conversations handed over should fall slowly as the agent learns the client's facts, but never to zero: complaints and big decisions should always reach a person. And the time from handoff to a person's reply should stay short. If handoffs keep growing, read them: most are a missing fact, which is fixed by adding it to the knowledge, not by loosening the rules. [Sentiment analytics](/blog/sentiment-analytics-for-smarter-engagement) shows whether frustration is building in conversations nobody escalated. ## Where Maxbound fits Maxbound's AI agents hand conversations to your team in one [inbox](/platform/inbox) with the full thread, so a person picks up where the agent stopped. Conversations that need attention are easy to filter, the agent pauses once a team member replies, and replies can wait for approval when you want a person to check everything. The rules differ per client, and each client has its own workspace. For agencies running paid social, see [Maxbound for advertising agencies](/solutions/advertising-agencies), and for approval-first setups, [setting up a human-in-the-loop workflow](/blog/how-to-set-up-a-human-in-the-loop-ai-workflow). ## Frequently Asked Questions ### When should a chatbot hand over to a human? When the customer is upset, when it doesn't know the answer, when the topic is one a person must decide (refunds, discounts, legal or medical questions, complaints), and when the person is a big buyer worth a human touch. ### What makes a good chatbot-to-human handoff? The customer is told a person is coming, the person sees the whole conversation and why it was handed over, and the bot stops replying in that conversation. ### What should the customer be told during a handoff? A short, honest line that a person from the team will reply in the same chat, and when, especially outside working hours. ### How many conversations should an AI agent hand over? It depends on the client. The share should fall as the agent learns the client's facts, but never to zero, because complaints and decisions should always reach a person. ### What if nobody picks up the handoff? That's the worst outcome: a promise of a person followed by silence. Name who picks up handoffs for each client and how fast, and who covers when they're away. ## Related - [How to Answer Instagram DMs in Arabic for Clients](https://maxbound.ai/blog/how-to-answer-instagram-dms-in-arabic-for-clients) — A step-by-step playbook for agencies: connect, train and brief an agent for Arabic Instagram DM replies and comment-to-DM, dialects and spelling variants - [How to Test a Kurdish Sorani WhatsApp AI Chatbot](https://maxbound.ai/blog/how-to-test-a-kurdish-sorani-whatsapp-ai-chatbot) — A step-by-step walkthrough for agencies: connect a client's WhatsApp, train a Sorani agent, rehearse it on past chats, and launch with approval on. - [Comment Moderation Tool for Agencies: A Setup Playbook](https://maxbound.ai/blog/comment-moderation-tool-for-agencies-a-setup-playbook) — How agencies set up comment moderation for every client: a policy template, hide-vs-reply rules, approval settings and the mistakes that cost clients. - [WhatsApp Business API for Agencies: Who Owns What](https://maxbound.ai/blog/whatsapp-business-api-for-agencies-who-owns-what) — How agencies should set up the WhatsApp Business API for clients: who owns the number and billing, how templates get approved, and where AI agents fit. - [Busting the Myths of Instagram DM Automation Tools](https://maxbound.ai/blog/busting-the-myths-of-instagram-dm-automation-tools) — Four myths keep agencies answering Instagram DMs by hand: that customers hate automation, that it's all-or-nothing, that setup takes weeks, and that it gets - [All posts](https://maxbound.ai/blog) - [Platform overview](https://maxbound.ai/platform)