PanelBot
Sign in Start free

Features

Every part of the L1 job, in one AI helpdesk

This page is the long version: what customers get in the chat, what your team gets behind it, and what it covers across your cPanel and DirectAdmin stack. 8 in 10 routine tickets end in the chat, and every capability on this page is included on the free plan.

In the chat

Live chat for WHMCS and Blesta, from your customers side

01

One hook file in WHMCS or Blesta

No migration, no new portal. PanelBot mounts inside the client area your customers already use, takes your brand, and knows who it is talking to from the first message, because the billing session says so. The same file connects your cPanel and DirectAdmin servers over the panel API, so they show up already connected.

  • Identity comes from the billing session, not a login form
  • Servers connect with a scoped panel credential, no agent to install
  • Three launcher styles, six accent colors, light, dark, or follow the OS
  • Nothing for customers to install or sign up for
portal.yourhost.com / clientarea

02

A first reply that checked before it spoke

Plain customer language in, real diagnosis out. The read-only checks run before the first reply, so the opening message is an answer, not a request for your cPanel password.

  • Hundreds of hosting checks and fixes built in
  • Asks for detail only when it actually needs it
  • Customers see plain language, never raw logs

Nothing changes without a yes

Read-only checks run on their own. Anything that changes the account is held until the customer agrees. Deleting something takes a second step, the exact name typed into a confirmation form, and both steps are logged. Nobody deletes half-awake.

It knows the account, not just the question

"Which plan am I on?" is a one-message conversation. Signed in through your portal means PanelBot already knows the services they own, the server each one lives on, and what is due.

Passwords never touch the chat

New credentials are generated by the system into a secure temporary field. Not stored anywhere, and destroyed from our records the moment the chat ends. The transcript has nothing to remember.

It answers in the customer’s language

A question in Hindi gets its answer in Hindi. Italian, Spanish, Arabic, the same. No setting to flip, no translator on staff. The customer just types.

Behind your desk

What your team gets

03

Live handoff that keeps the context

Every plan

When a case needs judgment, it lands in your Chat Dashboard as a claim, not a cold start. Whoever picks it up sees the transcript, the customer's services and server, and every check the AI already ran, with its result. If nobody is online, the same escalation files as a ticket in your portal instead. This is on every plan, Free included.

  • A claim queue with assignment, priority, and unread state
  • Customer context beside every chat: services, server, session
  • Every check the AI ran, listed with what it found
  • Canned responses with variables your team controls
  • The AI keeps answering until a teammate joins
app.panelbot.io

04

After hours, it still finishes the intake

When nobody is on shift, PanelBot keeps asking the questions a technician would, then files a structured ticket in WHMCS or Blesta: what was asked, what it collected, and what it suggests doing next. Your morning queue starts half done.

  • Intake collected overnight: domains, scope, timing
  • The diagnosis and full transcript ride along with the ticket
  • Tuned to your office hours
app.panelbot.io

05

A knowledge base your team owns

Publish the answers you want reused for billing, policies, and procedures. Draft first, publish when ready, and mark sections internal so staff see them and customers never do. Change wording without touching code.

  • Per-brand articles with categories
  • Internal-only sections for staff
  • Used alongside live server checks, not instead of them
app.panelbot.io

06

Every conversation, on the record

Every reply, check, escalation, and approval is logged with who, what, and when. Owners, admins, technicians, and viewers each see what their role allows.

  • Filter by action, actor, or date, then export to CSV
  • Conversation replay for 90 days, action history for 12 months
  • Role-scoped: owners, admins, technicians, viewers
  • Passwords are generated server-side and delivered out of band, never shown in the transcript
app.panelbot.io

You draw the lines

Per-brand policy for what runs in chat, what needs approval, whether high-impact actions may run in chat at all, and when the office is closed. The defaults are safe. The dials are yours.

Fleet-aware from the first check

Two servers or two hundred accounts, PanelBot knows which machine every service lives on, so checks land on the right box without asking the customer for an IP.

Coverage

cPanel and DirectAdmin support, category by category

If it makes a ticket, it is probably in here. These are the categories your queue is made of, and everything below is something PanelBot does today, in the chat.

SharedResellerVPSDedicated

All four, on cPanel and DirectAdmin, connected over the panel API. A reseller account connects without root. On VPS and dedicated, where your customer owns the whole machine, PanelBot can go further: restart the crashed service after a yes, not just find it.

Mail

Queue, auth records, blocklists, mailboxes. Releases stuck mail, publishes missing auth records, resets mailbox passwords, sets up forwarders and autoresponders.

DNS

Looks up records the way the internet sees them, then fixes the zone: a missing A record, a wrong MX, a typo in a TXT.

SSL

Reads why a certificate did not renew, what blocked the validation, and reruns issuance for the account in the chat.

Backups

Finds the right JetBackup snapshot and restores a single database, folder, or mailbox after a typed confirmation. Whole-account restores go to your team.

WordPress

The white-screen call. Deactivates the broken plugin, reinstalls corrupted core files, repairs the database, clears the maintenance flag. Even uninstalls, after a yes and the site name typed back to confirm.

Databases

Creates databases and users, sets privileges, repairs corrupted tables. Deletes them too, once the customer types the database name to confirm.

Security

Tells a locked-out customer why, and unblocks them. Runs malware scans and cleans infected files once the customer agrees.

Performance

Finds what is eating CPU, memory, or disk and shows the evidence. When the answer is a bigger plan, your team gets the sale, diagnosis attached.

CloudLinux

Explains LVE limit hits in plain language and repairs per-user environments without touching the rest of the box.

Domains

Creates subdomains, aliases, and pointers in the chat, and deletes them after the customer types the exact name. Suspensions stay with your team.

FTP

Adds and removes accounts, resets their passwords, sets quotas, and kills stuck sessions.

Cron & Node.js

Fixes or removes a broken cron line, restarts a customer Node app. The small parts that make the weird tickets.

Checks run on their own. Fixes wait for the customer’s yes. Deletions take two confirmations: a yes, then the exact name typed back, both logged. Only the critical few go to your team: terminations, suspensions, whole-account restores.

The fastest coverage check for your stack: pick last month’s noisiest ticket and put it to the free plan, 30 conversations a month with no card. Or read ten real tickets first.

More detail in the docs: What the assistant can do WordPress SSL, domains and DNS Email deliverability Your knowledge base Configure the widget Main and Sub servers Supported platforms

Reference and reach: For your customers Languages Troubleshooting setup Reliability Reference

Put it on your portal this week.

Start free on your own WHMCS or Blesta install. 30 conversations a month, no card, cancel anytime.

Start free, no card Book a 20 min review