Panelbotdocs
SearchStart free

How escalation works

How Panelbot hands a conversation to your team when the AI is unsure, a change is risky, the issue is out of scope, or the customer asks for a person.

Knowing when to step back

The most useful thing a support assistant can do is recognize the edge of what it should handle. Panelbot is built around that idea. It resolves the common, well understood problems on its own, and for everything else it hands the conversation to a real person on your team. Escalation is not a failure mode bolted on at the end. It is a core part of how the product earns trust: the AI knows its limits, and your staff stay in control of anything that matters.

This page explains what triggers a handoff, how the conversation reaches your team, and what your customer sees while it happens.

What triggers a handoff

Panelbot escalates in four situations. Each one is a case where continuing on its own would be worse for the customer than bringing in a person.

The AI is not sure. If Panelbot cannot confidently match the customer’s problem to something it knows how to handle, it does not guess. It stops and hands the conversation over rather than sending the customer down the wrong path.

A change carries real risk. Panelbot runs read-only checks freely, because looking never breaks anything. Making a change is different. Low risk, reversible fixes run only if you have chosen to allow them. Higher impact changes always wait for a person to approve them, every time, with no exception you can switch off. If resolving the issue would require one of those higher impact actions, the conversation goes to your team for a decision.

The issue is outside its scope. Panelbot covers a defined set of hosting problems. When a customer raises something that falls outside that set, or a conversation drifts into territory the assistant was not built for, it hands off instead of improvising.

The customer asks for a person. If someone simply wants to talk to a human, that is enough. Panelbot does not argue, stall, or loop them through the same questions. It brings your team in.

A conversation that runs unusually long or gets stuck is treated the same way. Rather than spinning in circles, Panelbot escalates so a person can pick up where it left off.

How an escalation reaches your team

Where a handoff lands depends on what the situation needs and on who is available.

When a fix needs sign off, Panelbot raises an approval request in your dashboard. Your team sees what the assistant wants to do and why, and the action runs only after someone approves it. Nothing risky happens on its own while that request sits waiting.

When the conversation itself needs a person, Panelbot routes it toward whoever can take it. The live Chat Dashboard is on every plan, so when a member of your team is online the chat can move to a live handoff where a staff member steps into the same conversation the customer is already in. If nobody is available right then, the conversation becomes a ticket so it is not lost, and your team picks it up from the support inbox. What your plan includes for escalations has the detail. You keep the full transcript and the context the assistant already gathered, so whoever takes over does not start from a blank page. The support inbox and live chat handoff page covers what that looks like from your side.

You set the escalation contact for your account when you connect your billing portal, so handoffs always have somewhere to go.

What the customer sees

From the customer’s point of view, a handoff should feel like being passed to the right person, not like hitting a wall. Panelbot tells them plainly that a member of the team has been brought in, and keeps them in the same chat window rather than making them start over somewhere else.

Customers never see technical errors, internal details, or anything about how the decision was made. If something goes wrong behind the scenes, the message stays simple and honest: someone on the team has been notified and will follow up. The conversation, and everything the assistant already worked out, carries straight through to the person who takes over.

Why this design matters

A support tool that tried to handle everything would eventually make a confident change it should not have. Panelbot is built the other way around. It does the routine work well, and it treats “hand this to a person” as the correct answer whenever confidence is low, a change is risky, or the request falls outside what it should touch. Your customers get quick help on the common problems, and your team keeps the final say on everything else.

To see how the decision to hand off fits into the wider safety model, read when a human takes over and safety and permissions.