How to add an AI chatbot to WHMCS

To add an AI chatbot to WHMCS, install a small addon module in your WHMCS, activate it, connect it to a chat service with a one-time code, and choose which actions it may run. Once connected, it answers clients from your knowledgebase and your prices, and for a signed-in client it reads their own account.

WHMCS runs the billing and client area for a lot of hosting companies, so the same questions arrive there every day. Where do I point my domain. Why is my site down. When does my service renew. An AI chatbot answers those from your own data, at any hour, and passes the rest to your team.

Does WHMCS come with an AI chatbot?

Not one that answers your clients. WHMCS 9.0 added AI domain-name suggestions to its domain search. WHMCS has also announced an AI Support Copilot addon that will suggest ticket replies to your staff: its 9.0 release highlights promise a technology preview and say "the full release of this addon module is coming in 2026" (checked on 19 October 2026). Neither is a chat for your clients. Our post on whether WHMCS has AI covers both.

WHMCS also sells a Live Chat addon, built with Chatstack, that connects a client to a human agent and saves the transcript as a ticket. Its documentation says WHMCS does not include it by default and that WHMCS Cloud does not currently support it, and neither the documentation nor its Marketplace listing mentions AI. Answering clients automatically means adding a separate module or chatbot that can read your WHMCS data.

What you need before you start

Three things. A WHMCS install you can upload files to, running version 8.0 or newer with PHP 7.4 or newer, and a System URL on https. A chat service that can read your WHMCS data and answer in your client area. And about an hour, though most of that is deciding what the chatbot may do, not installing anything.

The connection to WHMCS is the part that matters. A plain website chatbot that cannot see WHMCS will guess, and a wrong answer about an invoice is worse than no answer. So judge any option by what it can read from your account and what it is allowed to change, not by the chat window itself.

How to add an AI chatbot to WHMCS, step by step

These steps follow the free WHMCS AI chatbot module from MagizAI. Other vendors sell WHMCS chatbots too, and the shape is similar: a module inside WHMCS, a connection to the AI service, and a set of permissions you control.

1. Download the module and upload it to modules/addons/magizai in your WHMCS. The folder has to keep that name.
2. Activate it in WHMCS under System Settings, then Addon Modules.
3. Connect it with a code. Create a connection code in the chat service and paste it on the module's Setup tab, and the module fetches the settings it needs. The code works once, within 30 minutes.
4. Choose what it may do. Press Add WHMCS skills. Lookups work straight away, and anything that changes an account stays off until you switch it on.

That is the whole install, and it takes about ten minutes. There is no WHMCS admin API key to hand over, because the module adds a small signed endpoint inside your WHMCS and the chatbot can only call the actions you switched on.

What to train it on

A chatbot is only as good as what it reads. Point it at your public knowledgebase, your announcements and network status, your plans and prices, and the nameservers you give new clients. Those cover most of what people ask before they open a ticket. Many setups sync this overnight, so a knowledgebase article you change in WHMCS reaches the chatbot the next day, and an article you delete is dropped.

Client data is different. Services, domains, invoices and tickets are read live from WHMCS at the moment a signed-in client asks, and they stay inside WHMCS. The chatbot does not keep its own copy of anyone's account.

What the chatbot can answer

For any visitor it answers from your knowledgebase, your announcements, and your plans and prices, and it can check whether a domain name is free. For a signed-in client it reads that client's own services, domains, invoices, payments, orders and tickets, so it can explain why a site is suspended, say whether a payment arrived, or say when a service renews. It can also give the login username and a one-click sign-in to the control panel.

Once you allow them, it can take actions too, such as changing nameservers, renewing a service, opening a ticket or placing an order. Each action waits for the client to tap Confirm under a plain description of what it will do, and nothing runs on its own. Showing a service password in the chat takes more: a 6-digit code that WHMCS emails to the address on the account.

Keeping client accounts safe

An agent that can touch billing needs guardrails, and most of them come from WHMCS. Every lookup and every change runs under the signed-in client, so a client who asks about someone else's domain gets the same reply as for a domain that does not exist. A password is only ever shown after a code that WHMCS emails to the client. A change also needs a recent sign-in, 15 minutes on a new install, and a client can make at most 10 changes an hour through the chat. Each request is logged, and the client gets an email about any change. If that still feels like a lot, start with lookups only and turn actions on later. There is a fuller list in our guide on what to check before you let AI touch a customer account.

When it should hand off to a person

A sensible setup answers the routine questions and knows its limits. When the chatbot cannot help, or the client asks for a human, the chat moves to your team inbox with the whole conversation, and the chatbot stops replying as soon as an agent writes. From module 1.9.0 your WHMCS tickets show in that inbox too, where a reply is posted to the ticket and WHMCS emails it to the client. The AI posts nothing on a ticket until you choose private suggestions or replies. Since module 1.10.0 your staff also get a MagizAI bar on each ticket in the WHMCS admin area, to draft a reply, improve or translate their own text, or summarise the ticket, and nothing reaches the client until they send the reply themselves. If you want people on chat during office hours and the AI covering the night, that is the WHMCS live chat setup, with the AI answering first.

What it costs and how to start

The module itself is free to download. The chat behind it runs on a paid plan, and the options are on the pricing page; showing your hosting plans as cards in the chat needs a plan that includes product recommendations. If you would rather not set it up yourself, the team can install and connect it for you. For a wider look at running AI support on a hosting business, read AI live chat for web hosting companies.