Who Panelbot is for

Panelbot fits shared, reseller, VPS, and dedicated hosting providers on cPanel or DirectAdmin who want to clear repetitive tier-one support faster.

Built for hosting providers with a support queue

Panelbot is for companies that sell web hosting and answer their own support. If your customers open tickets about email, WordPress, certificates, and sites being down, and your team answers most of them by hand, this is built for you.

It works with the panels and billing systems hosting providers already run, so adopting it does not mean changing how you operate. You keep your portal, your servers, and your team. Panelbot handles the first response and the routine investigation.

The businesses it fits

Shared hosting providers

If you run shared servers with many accounts, most of your tickets are individual customers hitting individual problems. Panelbot recognizes the common ones, checks the specific account involved, and either resolves it or brings your team a clear diagnosis. The customer gets an answer in the moment instead of waiting for the queue to clear.

Resellers and reseller-heavy providers

Reseller setups add a layer: a reseller owns accounts, and those accounts belong to end customers. Panelbot understands that structure and keeps every customer scoped to exactly what they own. A reseller’s customer is helped with the reseller’s accounts, and nobody sees or touches anything outside their own set.

This includes you when you are the reseller. If your business runs on a reseller account at an upstream host and you have no root anywhere, Panelbot still connects: it uses your reseller credential over the panel API, works within what that credential allows, and shows you exactly what that covers. No agent, no root, nothing to ask your upstream host for.

VPS and dedicated providers

For customers on their own VPS or dedicated servers, Panelbot supports server-level support alongside account-level support, while still respecting who owns what. The same safety model applies: only pre-approved operations, only on servers the customer owns, with higher-impact changes gated behind your approval.

Teams drowning in repetitive tickets

The clearest sign that Panelbot will help is a support queue full of the same questions. “My email is not sending.” “My site shows an error.” “Why is my certificate expired.” “I cannot log in from my office.” These are tier-one tickets: routine to answer, but relentless in volume, and they interrupt the deeper work only your senior people can do.

Panelbot is aimed squarely at that layer. It takes the first pass so your technicians spend their time on the tickets that genuinely need a human, not on password resets and cache clears.

What you need to use it

Panelbot connects to the tools you already have:

  • Control panels: cPanel/WHM and DirectAdmin, connected over the panel API with a credential you grant. A reseller credential is enough; no agent is installed and no root is required. Panelbot detects which panel a server runs and adapts to it.
  • Billing portals: WHMCS and Blesta. Panelbot connects to your portal so it knows who a customer is and which services they own, which is the foundation of every ownership check it makes. The same PanelBot integration that adds the chat widget, one hook file for WHMCS or one plugin for Blesta, also connects your servers in a few clicks.

You add the chat widget to your portal, connect at least one server, and you are running. You can do all of it on the Free plan without a card: see Start free on WHMCS or Blesta, or the onboarding checklist for each step in the dashboard’s own order.

What a good fit looks like

Panelbot is likely a strong fit if:

  • You run cPanel or DirectAdmin and bill through WHMCS or Blesta.
  • A large share of your tickets are common, well understood hosting issues.
  • You want faster first responses without hiring more tier-one staff.
  • You want to stay in control of what an automated system is allowed to change, and to see a record of everything it does.

What it is not

Panelbot is honest about its edges, because that is what earns trust from operators who have seen tools overpromise.

It is not a replacement for your support team. It handles the common cases and does the first investigation, but real people remain essential. When the assistant is not confident, when a change is risky, or when an issue falls outside what it understands, it escalates to your staff rather than guessing.

It is not a tool that resolves every possible problem. It targets common, well understood issues and is upfront when something is beyond its scope. Some categories are diagnostic only, meaning it will investigate and explain but leave the change to a human on purpose.

And it is not an autonomous operator loose on your servers. It cannot invent actions or run arbitrary commands. Every operation comes from a fixed, pre-approved list, and the AI never chooses to run anything on its own.

Where to go next