# WHMCS Live Chat Integration

> Tidio, Intercom, Crisp, Tawk.to or LiveChat in your WHMCS client area, with logged-in customers identified for agents.

Live chat for WHMCS: widget loaded through a hook, page rules, verified customer identity, account summary for agents and chat-to-ticket handoff. One-time price from $149.

- **Price:** Starting at $149
- **Billing:** One-time, fixed scope
- **Category:** Modules & integrations
- **Quote turnaround:** Fixed-price quote within 24 hours
- **Start a project:** https://whmcspilot.com/start-project
- **Details:** https://whmcspilot.com/services/whmcs-live-chat
- **Last updated:** 2026-11-05

## Overview

WHMCS live chat integration adds a chat widget from Tidio, Intercom, Crisp, Tawk.to, LiveChat or a similar provider to your client area and order pages, and tells the agent who they are talking to when the visitor is logged in. It is for providers who want to answer pre-sales and account questions in real time instead of waiting on tickets, and the basic setup is a one-time $149. Ticket queues in Zendesk, Freshdesk or Help Scout are handled on the [helpdesk integration](/services/whmcs-helpdesk-integration) page, and sales pipeline sync is [CRM integration](/services/whmcs-crm-integration).

## Why a hook instead of pasting code into the theme

Most chat providers tell you to paste a script into your site header. In WHMCS that usually means editing header.tpl or footer.tpl, and the change disappears the next time the theme is updated or replaced. We load the widget from a small file in /includes/hooks/ using the ClientAreaFooterOutput hook point, which places it just before the closing body tag on every client area page. Because the hook knows which page is being shown, it can also follow rules such as:

- Show the sales team on cart and product pages, and support inside the logged-in client area
- Hide the widget on pages where it gets in the way, such as invoice view or checkout payment steps
- Open the widget in the language the customer chose in WHMCS

## Telling the agent who is chatting

Since WHMCS 8.0, the CurrentUser class reports whether a visitor is signed in and which client account is active. The hook uses it to pass the customer's details to the widget:

- Name, email and WHMCS client ID
- Client group, such as reseller or VIP
- A short account summary: number of active services, the next due date and any unpaid invoice total
- A direct URL to that customer's record in your WHMCS admin

When an admin uses Login as Owner to view the client area, CurrentUser reports a masquerading admin, and the hook stops sending that customer's identity, so staff testing pages never appear in the chat history as the customer.

## Verified identity

A widget that accepts any name and email typed into the browser lets a visitor pretend to be someone else. Where the provider supports it, such as Intercom identity verification, Crisp's signed user email or Tawk.to Secure Mode, the hook computes a server-side signature with a secret that never reaches the browser. Agents can then trust that the account summary belongs to the person chatting.

## When nobody is online

Out of hours, the chat can still collect the question. We set the provider's offline form or transcript emails to arrive in a WHMCS support department mailbox, or, for providers with webhooks, open a ticket directly with the OpenTicket API action, so nothing asked after hours is lost.

## AI assistants alongside human chat

Some providers add AI answers on top of live agents. If you want an assistant that answers from your own WHMCS knowledge base and account data, options include MagizAI for WHMCS (see our [WHMCS AI chatbot guide](/whmcs-ai-chatbot)), our own [AI Chatbot Module](/modules/ai-chatbot-module), or the AI features built into chat platforms such as Intercom and Tidio. Training and guardrails for any of them are a separate job, [AI support agent setup](/services/whmcs-ai-support-agent-setup).

## Speed and privacy

Chat scripts are among the heaviest things on a client area page. We load the widget after the page has rendered, and, if you use a cookie consent banner, only after the visitor accepts. The privacy note we hand over lists which customer fields are sent to the chat provider, for your privacy policy. Wider page speed problems are covered by [speed optimization](/services/whmcs-speed-optimization).

## Versions

Any current WHMCS theme works, on self-hosted 8.13 (PHP 8.1+) or 9.x (PHP 8.2+).

## Before we start

- An account with your chat provider and the widget ID or script it gives you
- The identity verification secret, if your plan includes that feature
- Which pages should show the widget and which team covers each

## Price guide

ScopeOne-time priceOne provider loaded through a hook, page rules, and name, email and client ID passed for logged-in customersFrom $149Adds verified identity, the account summary for agents and sales or support routingDepends on the provider's identity featuresAdds offline chat to ticket handoff through a support mailbox or the OpenTicket APIQuoted per provider webhook support

The hook file comes with a README showing where each setting lives. During the first 14 days, any page rule that misfires is put right free.

## Not included

- The chat provider's subscription
- Staffing or answering chats
- A custom-built chat interface

Name the chat provider you already pay for, or the two you are choosing between, and the quote will reflect what that provider supports.

## What's included

- Tidio, Intercom, Crisp, Tawk.to, LiveChat or similar widget added to WHMCS
- Widget loaded through the ClientAreaFooterOutput hook, so theme updates do not remove it
- Page rules for cart, product, client area and invoice pages
- Logged-in customer name, email and client ID passed to the widget
- Account summary for agents: active services, next due date and unpaid total
- Server-side identity verification where the provider supports it
- Identity withheld when an admin uses Login as Owner
- Widget language matched to the customer's WHMCS language
- Offline messages routed to a WHMCS support mailbox or opened as tickets
- Consent-aware, deferred loading and a privacy note listing shared fields

## Business outcomes

- Agents know who they are talking to without asking for an account email
- Pre-sales questions on cart pages reach the sales team, not support
- The widget survives theme updates and theme changes
- Visitors cannot pose as another customer in chat
- Questions sent after hours still end up in your ticket queue

## Frequently asked questions

### Which live chat providers work with WHMCS?

Any provider that gives you an embed script, including Tidio, Intercom, Crisp, Tawk.to and LiveChat. What varies is how much customer data each widget accepts and whether it supports identity verification.

### Can the chat agent see the customer's WHMCS account?

Yes, for logged-in visitors. The hook passes their name, email, client ID and a short summary of services and unpaid invoices to the widget, plus a link to their WHMCS profile.

### Does a chat widget affect page speed?

It adds some weight, so we load the widget after the page renders and only where you want it. That keeps the effect on first load small.

### Can I use an AI chatbot instead of live agents?

You can use both. MagizAI for WHMCS, our AI Chatbot Module and the AI features in Intercom or Tidio are all options, and AI setup is quoted as a separate service.

### What happens to chats when no one is online?

The offline form or transcript goes to a WHMCS support department, or opens a ticket through the API, so the customer gets an answer in your normal queue.

### When do I pay?

The first 50% is due when you accept the quote, the second once the widget is live on your site. Stripe, PayPal and NOWPayments all work.
