Short answer: a hosting company should automate the questions that have one correct answer, such as nameservers, DNS records, email setup, SSL and password resets, and keep everything about a client's own money, account or outage with a person. Put the chat inside the client area so the team sees who is writing, and publish a status page so an outage does not become fifty identical chats.
Why is hosting support different from other support?
A customer whose website is down is losing visitors and sales while they wait. They do not want a ticket number; they want to know what is wrong and when it will be fixed. At the same time, a large share of hosting questions repeat: how to point a domain at your servers, why an email will not send, where to find the control panel login.
That mix, urgent and repetitive, is what makes live chat a good fit for hosting. A real-time answer fixes the urgent case, and a knowledge base fixes the repetitive case, so the person on duty can spend their time on the problems that need judgement.
Which hosting questions can an AI assistant answer?
The safest questions for an assistant are the ones with a documented answer that is the same for every client. For a hosting company this usually means:
- how to change nameservers or add a DNS record
- how to set up an email account in a mail app
- how to install an SSL certificate or why a browser shows a warning
- how to reset a control panel password
- where to find the plans, limits and what each one includes
Frosvo's AI assistant answers only from the articles and pages you give it, shows which article it used, and hands the conversation to your team when it is not sure. That last part matters more than the answers: an assistant that guesses about a client's DNS can cause real damage, so the handover is the feature you are paying for. Note that the assistant is part of the paid plans; the chat widget and shared inbox are free.
Write the first ten articles from your last month of chats. Tag the reason for each conversation, and the ten most common reasons are your reading list. The knowledge base guide shows how to turn them into articles the assistant can use.
What should always go to a person?
Some conversations should never be left to automation, however good it is:
- Billing and refunds. Anything about a client's own invoices, charges or cancellations.
- Suspensions and abuse reports. These need a decision and a record.
- Security incidents. A hacked site or a leaked password needs a person who can act.
- Faults on the client's own server. Diagnosing it needs access and judgement.
Frosvo's assistant hands over billing and account questions by design, and you can add the others to the assistant's instructions. The handover carries the reason with it, so the person who picks up the chat does not start from the beginning.
How do you see the client's account while you chat?
The slowest part of a hosting chat is usually asking "what is your domain?". Frosvo's WHMCS integration removes it. When a signed-in client writes, the side panel shows their account status, their services and domains with due dates, and any unpaid invoices. From the same panel you can open the client in WHMCS, save their details to their Frosvo contact, and send the WHMCS payment reminder for an unpaid invoice.
Setting it up has two parts, both described step by step in the WHMCS setup guide. First install the free addon module so the chat appears in the client area and signed-in clients are recognised. Then create a WHMCS API credential with a role that can read clients, products, domains and invoices, and connect it in Frosvo. You can remove the credential in WHMCS at any time.
How do you handle an outage without drowning in chats?
When a server fails, the same message can arrive dozens of times. Tell customers before they write. A public status page with the current incident, and a short notice in the chat while the incident is open, turns many identical conversations into none, and customers trust a provider that says so first.
Keep a saved reply for the incident so the people on shift all say the same thing. The customer support canned responses include examples you can adapt, and saved replies and macros show how to keep them at hand in the reply box.
How many people do you need on chat?
It depends on how many chats arrive in the busy hour and how long each one takes. The live chat staffing calculator uses the Erlang C formula to estimate the number of agents for a target answer time. Once you are live, Frosvo's reports show first-response and resolution times, so you can see which hours are short of people. The guide on first response time explains which number to watch.
What about pre-sales questions on the main website?
People who are choosing a host ask different questions from people who already have one. Add the same chat to your marketing site as a second website in Frosvo, with its own greeting and office hours, and both kinds of conversation arrive in one inbox, labelled with the site they came from. A visitor who writes from the pricing page and a client who writes from the client area can be answered by the same team, with the right context for each.
What is the quickest way to start?
- Create a free Frosvo workspace and add your billing site.
- Install the WHMCS addon module and paste the site key.
- Add the chat to your marketing site too.
- Write articles for your ten most common questions.
- Turn on the assistant if you are on a paid plan, and check its first answers.
- Publish a status page and add an incident saved reply.
The free plan includes live chat on one website with no time limit, so you can try the client-area chat before deciding anything else. Start free, or read the web hosting page for how the pieces fit together.