What Panelbot can and cannot do
An honest look at what Panelbot handles automatically, what needs your approval, and the limits it will not cross, so you know exactly what to expect.
Honest expectations, on purpose
The quickest way to lose an operator’s trust is to overclaim. So this page is deliberately plain about both sides: the real work Panelbot does, and the lines it will not cross. Knowing the limits is what makes the capabilities believable.
What Panelbot can do
Recognize and diagnose common hosting problems. Panelbot understands the everyday issues that fill a support queue across many categories: email that will not send or is landing in spam, mailbox and login trouble, WordPress errors and white screens, certificates and DNS, sites returning errors or going down, disk and quota problems, blocked access, and more. It reads the customer’s message, matches it to a known type of issue, and investigates the right account on the right server.
Run read-only checks automatically. The investigation stage is safe by design. Diagnostic checks look at the state of things without changing anything, so Panelbot can gather the facts a technician would gather first, immediately and without waiting for anyone’s approval. Most of the value is here: the customer gets a real answer about what is wrong, right away.
Apply low-risk, reversible fixes when you enable them. For a set of small, reversible changes scoped to a single account, you can choose to let Panelbot apply the fix directly. This is your decision to turn on, off by default, and you control it. If you would rather every change wait for a person, you can keep it that way.
Guide the customer. When the right next step is something the customer does themselves, Panelbot explains it clearly, in plain language, without jargon or log dumps.
Escalate to your team. When Panelbot is not confident, when a change carries real risk, when the issue is outside what it handles, or when the customer asks for a person, it hands the conversation to your staff with the context it gathered. Escalation is a normal, expected outcome, not a failure.
You also stay in control of the range itself: you choose which problem areas the assistant handles at all, area by area, and when you switch one off nothing from it runs. You can change that at any time.
Work within the credential you granted. Panelbot reaches a server over the panel API with the credential you connected it with. A reseller credential reaches the account-level checks and fixes; a root or admin credential reaches more. When a server connects, Panelbot shows you the exact list of what that credential can and cannot do on that machine, and it only ever offers what is on the list. Anything outside it goes to your team. If you need more reach, widen the credential or, for the narrow set of jobs no credential reaches, install the optional agent.
What Panelbot cannot do
It cannot invent actions. Panelbot works from a fixed set of pre-approved operations. It cannot make up a new one, and it cannot run anything that is not on that list.
It cannot run arbitrary commands. There is no “run this for me” back door, not for the customer, not for the AI, not even for debugging. If an operation was not approved in advance, it does not run.
It cannot touch a service the customer does not own. Ownership is confirmed in code against your billing records before anything happens. A customer cannot get Panelbot to act on a domain that is not theirs, no matter how they phrase the request.
It cannot make risky changes on its own. Higher-impact changes, the kind that affect more than a single account or could disrupt a service, require explicit human approval by default, and that is not something the AI can decide to skip. One optional setting you control can let a narrow, clearly scoped class of destructive actions, such as deleting a database or removing an addon domain, complete in chat after the customer passes a strong confirmation; it is off by default, fully logged, and the most dangerous operations, such as terminating an account or restoring an entire account from backup, stay off limits regardless.
It cannot guarantee that every problem is solved. Panelbot targets common, well understood issues. Some problems are unusual, ambiguous, or simply outside its scope, and for those it investigates as far as it safely can and then brings in a person. Some categories are diagnostic only on purpose: it will explain what is happening but leave the change to your team.
The AI’s role is narrow, by design
It helps to be clear about what the AI itself does. Its job is to understand the customer’s message, pull out the relevant details, and put replies into plain words. That is all. It does not choose which operation to run, it does not pick which server to touch, and it never decides whether a customer is allowed to do something. Those decisions live in code, driven by your settings and your billing records.
This is the opposite of a chatbot that has been handed a terminal. Because the AI’s authority is limited to reading and writing language, a cleverly worded message has nothing to exploit. There is nowhere for it to go.
Setting the right expectation with your customers
The honest promise to make to your customers is this: Panelbot answers right away, solves the common problems, guides them when the fix is in their hands, and gets a real person involved when it should. That is a strong promise precisely because it is true, and because it does not pretend the assistant is something it is not.
Where to go next
- Safety and permissions explains how operations are approved and gated.
- When a human takes over covers escalation in detail.
- How Panelbot works end to end shows how identity and ownership are checked before any action.