Can clients buy hosting in a chat? How ordering from chat works with WHMCS

Yes. A chat can sell hosting when it creates the order and its invoice in WHMCS, at the price WHMCS holds at that moment, and then sends the client to pay that invoice on your own site. It should never ask for card details. The client pays your invoice with your gateway, exactly as they would from the cart.

That is the short version. The longer one is about the checks that run before anything is created, because an order placed from a chat is still a real invoice.

How far can a WHMCS sales chatbot go?

There are three levels, and each asks more of the chat than the one before.

1. Recommend a plan and link to it. The chat reads your plans, suggests one and links to its order form. Any chatbot trained on your product pages can do this.
2. Check a domain, then hand over to the cart. WHMCSBot for Telegram, at $82 on its Marketplace listing (version 1.6.0, 8 April 2026), lists "Open checkout for available domains": the client finds a free name in Telegram and finishes on your site.
3. Place the order in WHMCS. Of the WHMCS AI chat products we checked on 19 October 2026, two say on their own pages that they can place a new order from a conversation. Provonic's Clients MCP Server lists "New Orders With Options And Addons" through the client's own AI assistant, such as Claude or ChatGPT, and says "anything that costs money or cannot be undone needs the client's approval in the chat first". MagizAI's WHMCS AI chatbot module does it from the chat in your WHMCS client area, after one tap on Confirm.

What should be checked before an order is created?

A chat that places orders needs the same care as your cart, and a few checks the cart never needed because a person was clicking. These are the ones our module runs every time, and they are a fair list to ask any vendor about:

• The plan is on sale right now, at the price WHMCS holds right now, never a price quoted earlier in the conversation.
• A plan name that matches two products becomes a question back to the client, not a guess.
• A domain to be registered is actually free, so nobody is invoiced for a name someone else owns.
• A client who already owns their domain is not sold a registration they do not need.
• The invoice is raised against a payment method you have switched on.

The order is then created the way the cart would create it, so your welcome emails, provisioning and automation run as usual. Before the client confirms, the chat reads back the exact plan, term, price and domain.

Can a new client order without an account?

It depends on your own WHMCS settings, and a chat should never be looser than they are. WHMCS's Allow Client Registration setting decides "whether to require a product order before customers can sign up". With Enable TOS Acceptance on, WHMCS's documentation says "if the customer does not accept the TOS, the system will not create the order".

Our module follows both. It opens an account on its own only when client registration is allowed, and with an order only in the way your cart lets a new client register at checkout. It shows your terms when you require them, and refuses to open a second account for an email address WHMCS already has: that visitor is asked to sign in. WHMCS then sends its own welcome and password reset emails, so the client chooses a password that never appears in the chat. One account per conversation, and five an hour for the whole install unless you change it.

How does a brand-new client pay?

A new client has no password yet, so they cannot sign in to pay. WHMCS has a single sign-on token for this, and its API reference says the tokens "are valid for a maximum of 60 seconds" and are single use. So a pay link cannot be made in advance and left in a transcript. It has to be made at the moment the client taps it.

That is how the module's Pay now button works. Each tap asks WHMCS for a fresh sign-on into that invoice. It works only for the account that same conversation opened, from that visitor's own chat, for two hours and five taps at most. A link that logs someone straight into an account, kept in a chat history any agent can read, is the thing to avoid.

Can clients upgrade or renew from the chat?

Yes, and the same rule applies: WHMCS sets the price. An upgrade is quoted with WHMCS's own pro-rata figure, then priced again just before the order is placed, so the invoice matches what the client agreed to. A renewal never raises a second invoice when an unpaid one already covers it; the client gets that invoice's link instead. Renewing a service early needs WHMCS 8.8 or newer. Extras, such as a dedicated IP, are listed only when they apply to the client's plan.

Can the chat show plans as cards?

It can, so a client compares plans at a glance instead of reading a paragraph of prices. The module reads your plans from WHMCS and shows the monthly price first, what is billed and how often, the saving against monthly billing, the main features from the product description, and an Order now button that opens that term in your cart. Hidden and retired products never appear, and prices refresh daily. Cards need product recommendations, which the comparison on our pricing page shows on every plan except BYOK. The products guide explains the switch.

What about domain name ideas?

WHMCS 9.0 added AI suggestions to its own domain search: a client can type "a keyword or description" instead of an exact name. Our chat does something simpler. It checks the exact name the client asks for and suggests the same name with other extensions, with limits so a script cannot get your server throttled by the registries. For open-ended ideas, send the client to your WHMCS domain search.

What should you measure?

Three numbers: orders started in the chat, orders placed, and orders paid. The module's activity log records every change made from the chat, and WHMCS shows which invoices were paid. Accounts opened in the chat are recorded in their own table, and their client notes say they came through live chat.

Turn ordering on for one product group first and read every order conversation for a week. Our checklist for AI that touches a customer account covers what to look for, the WHMCS setup guide shows where the switches are, and other vendors' order features are set side by side in our AI chatbots for WHMCS comparison.