Over the years I have worked with a lot of website owners, some as my own clients and some in my role as Web Manager at BloomHouse Marketing. They all have one thing in common: sooner or later, they ask for live chat.
It is a reasonable request. A visitor with a question is the warmest lead a website will ever get. If they can ask it and get an answer while they are still on the page, they buy, book or call. If they cannot, they go back to Google and click the next result.
So for years I did what everyone does. I picked a live chat tool, installed it and moved on. Then I picked another one. And another. This post is the honest story of why none of them worked for me, why pricing and control were the two things that broke it, and why I ended up building live chat into WPCentrify myself.
In this post
- Live chat for WordPress is easy for one website and messy for many
- The live chat pricing problem
- The bigger problem: I had very little say
- Why building my own live chat finally made sense
- What I built, and the frustration behind each decision
Live chat for WordPress is easy for one website and messy for many
Here is the part nobody tells you when you compare live chat tools: almost all of them are designed around one business with one website.
That is fine if you run a single online store. It is a problem when you look after dozens of sites for dozens of different businesses. Every tool I tried pushed me into one of two bad setups:
- One account per website. Separate logins, separate settings, separate bills. To see whether anyone was waiting, I had to check account after account.
- One account for everything. Every site shared the same settings and the same inbox, so a dental practice and a law firm ended up with the same welcome message, the same hours and the same team answering.
Neither one scales. The first wastes your day. The second embarrasses you in front of clients.
The live chat pricing problem
I want to be fair here. Running a live chat service costs real money, and I do not expect anyone to give it away. My problem was never that chat tools charge. It was how they charge, and what happens to that bill when you manage more than a handful of websites.
Every person who answers is another monthly fee
Most tools use per seat pricing, meaning a fee for every person who answers chats. On its own, that is understandable. But many of my clients want their own receptionist or sales team answering, because only they know whether Tuesday at three is free. Every one of those people becomes another seat, on a bill somebody has to justify every month.
Every website multiplies the bill
Then comes the per-site or per-workspace part. When a tool charges for each website or workspace, a price that looks small on the pricing page gets multiplied by every client you manage. Across a portfolio of client sites, “small” stops being small very quickly.
Paying to remove someone else's logo
Many tools, including some of the free ones, show their own branding in the chat window. Removing it is often a paid add-on, and in some cases it is charged per website. So I was paying extra, site by site, just to stop my clients’ websites from advertising somebody else’s product.
The feature you need is always on the next plan
This one frustrated me the most. The basics are cheap, but the things that make live chat work for a business are usually one tier up: routing chats to the right person, business hours per site, reporting, removing branding, more conversations per month. You sign up for one price and end up paying another.
The "free" plan is a trial with extra steps
Free plans got me started more than once. Then I hit a cap on conversations, a limit on history, or a feature that switched off after a few weeks. By then the chat was already live on a client’s site, so switching away cost more time than just paying.
Put all of that together and you get a bill that grows with every site, every person and every feature, while the value to each client stays exactly the same.
What the bill grew with
What I actually wanted to pay for
Every person who answers
The people who answer, once
Every website or workspace
Chat as part of the sites I already manage
Removing another company’s logo
My clients’ brand, by default
Features locked on higher tiers
The features a business needs, from the start
The bigger problem: I had very little say
If pricing was the headache, lack of control was the reason I stopped looking for a better tool and started thinking about building one.
I could not decide who sees what
When a client’s own team answers their chats, those conversations are their business. Customers share phone numbers, addresses and sometimes very personal problems. With most tools, either I could see everything or I could see nothing. There was no clean way for the client to decide what their agency is allowed to read, and no record of who changed what.
I did not know where visitor data was going
As someone with a background in cyber security, this bothered me more than most people. Visitor IP addresses sent to outside location services. Conversations passed to third-party AI tools for summaries. Settings I could not switch off. When a client asked me where their customers’ data went, I did not always have a confident answer. I hate not having that answer.
Another plugin, another script, another thing to break
Every chat tool meant another WordPress plugin to install and keep updated, or another script loaded on every page. I also do SEO for a living, and I have watched chat widgets drag down page speed on sites that were otherwise fast. I have watched caching and optimization plugins quietly hide a chat widget too, and found out only when the client asked why nobody had used it for a month.
The roadmap was never mine
When something did not work the way my clients needed, the answer was always the same: submit a feature request. I understand why. These products serve thousands of businesses, and agencies managing many WordPress sites are a small part of that. But it meant the things I needed most were never going to be anybody’s priority.
Pricing tells you who a product was built for. If the bill grows faster than the value you get from it, you are probably not the customer it was designed around.
Why building my own live chat finally made sense
I did not set out to build a live chat product. What changed was WPCentrify.
WPCentrify is the WordPress management platform I built to handle updates, backups, security and uptime across all my sites from one dashboard. Every site I manage already runs its small connector plugin. One day it clicked: the hardest part of rolling out live chat across every client site, getting something installed and trusted on each one, was already done.
Live chat could simply be part of the tool I already open every morning. No new plugin on client sites. No new account per client. No separate bill per website.
So I built it, and every decision came straight from a frustration above.
What I built, and the frustration behind each decision
One desk for every website
Chats from every site arrive in one agent desk, each labeled with the website it came from. I can see who is waiting, who is talking to whom, and which chat needs attention first.
Every site keeps its own settings
Color, position, logo, light or dark theme, welcome message, business hours, time zone, holidays and team are all set per website. The dental practice and the law firm never share a chat window again.
The client decides what I can see
A client can have their own receptionists answer from a simpler client desk. The client’s owner chooses whether my team can read their transcripts and see their team’s ratings, and every change to those switches is logged. Even when they let us read, we can read but never reply.
Visitor data stays put
Location comes from a database on our own servers, and the visitor’s IP address is never sent to an outside service or stored. Chat summaries are written by our own AI model, so conversations are not handed to a third-party AI service.
Built to stay out of the way
Only a tiny loader for the chat button loads with the page. The chat itself loads when someone opens it, inside its own sealed box so the theme cannot break it. And a Check the live page button confirms the widget really appears to visitors, even behind caching plugins.
Every chat becomes a lead
While a conversation happens, a lead card fills itself in with the visitor’s email, phone number and what they need. One click saves it next to the site’s contact form inquiries, so chat leads get followed up like every other lead.
People and AI working together
Live chat works on its own, or behind the WPCentrify AI chatbot. When the assistant hands a visitor to a person, that person gets the whole conversation, the page the visitor is on and a short summary. Nobody has to ask the same question twice.
No dead queues
Outside business hours, visitors leave their details and a message instead of waiting for someone who is not coming. During hours, new chats keep ringing and the waiting timer changes color, so nobody is left hanging. If you want to know what a good reply time actually is, I wrote about live chat response time with sourced benchmarks.
You can see the full list of features on the WPCentrify live chat page.
So how does live chat pricing work now?
I would be a hypocrite if I complained about pricing and then hid how mine works, so here it is.
Live chat is free while WPCentrify is in early access. After that, it is switched on per website within the number of websites your plan already covers. There is no separate live chat bill for each site.
I will be honest about one thing: every person who answers chats does use an agent seat in WPCentrify too. People cost money to support, and I think that is a fair thing to charge for. What I refused to do was stack a seat price on top of a per-site price, on top of a branding fee, on top of a tier upgrade. One seat per person who answers. That is it.
The only paid extra is the white label add-on, for agencies who want to remove the “Powered by WPCentrify” line from the chat window entirely.
What it does not do yet
I would rather you hear this from me than find out halfway through a rollout. Right now, visitors cannot send file attachments in the chat, the chat window does not open itself automatically based on rules, and there is no WhatsApp or social media inbox alongside the website chat. If one of those is essential for you today, other tools will serve you better for now, and I would genuinely like to hear about it.
What building my own live chat taught me
A few lessons that apply well beyond live chat:
1
Pricing tells you who a product was built for
If the bill grows faster than the value you get from it, you are probably not the customer it was designed around.
2
Control is a feature
Being able to say exactly who can see what, and where data goes, is worth as much as any button in the interface.
3
Build on what is already installed
The best tool is the one your clients never have to install. That is why chat lives inside the connector plugin my sites already run.
4
Be honest about the gaps
Every product has them. Saying so up front builds more trust than any feature list.
Frequently asked questions
Why not just use a popular live chat tool?
For a single website, many established tools are a great choice. My problem was running chat across many WordPress sites for different clients, where per-seat, per-site and add-on pricing multiplied quickly and I had little control over data, access and settings for each client.
Is WPCentrify live chat free?
Yes, during early access. After that it is included per website within your WPCentrify plan, and each person who answers chats uses an agent seat.
Do I need to install another plugin on my WordPress site?
No. If the site is connected to WPCentrify, the connector plugin it already runs adds the chat window. A site without it can paste a small snippet into the footer.
Can my client's own staff answer chats?
Yes. They answer from a separate client desk, and the client decides whether the agency can read their conversations.
Does the chat widget slow down my WordPress site?
Only a tiny loader for the chat button loads with the page. The chat itself loads when a visitor opens it, inside its own sealed container, so it stays out of the way of page speed and the theme.
Written by Usman Naim
Usman Naim is a WordPress, SEO and automation specialist and the founder of WPCentrify. He has managed WordPress sites for more than six years and currently looks after more than 80 of them, holds an MSc in Cyber Security and is a Certified Ethical Hacker (CEH).
If you manage WordPress websites and any of this sounds familiar, live chat is free to try during early access. You can see how it works here, or get in touch with me if you want a hand setting it up for your own sites or your clients’ sites.
I built it because I needed it. I suspect I am not the only one.