Best Chatbot for WordPress: The Plugin Is Free, the Service Is Not

That distinction decides more about your three-year cost than any feature comparison, so this page starts there. Then the published prices, the hosting question WordPress users specifically need to answer, and the five checks worth doing before you activate anything.

Two kinds of WordPress chatbot plugin

Both appear in the same plugin directory, both install in the same three clicks, and they are completely different purchases.

Neither is better in the abstract. A connector gives you a maintained platform and no server load. A self-hosted plugin gives you a predictable cost and your data in your own database, at the price of adding work to a site you already have to keep patched.

What they cost

We make Asyntai, so read that row as a disclosure, and note that it is a connector like most of this list. The WPBot figures come from published 2026 roundups rather than a first-party price table, so confirm them on the vendor's own site.

Three years, not one month

Subscription and licence pricing look similar in month one and diverge sharply after that. Here is the same small business site on two paths.

State the trade honestly. The $1,255 buys you a maintained platform, someone else's uptime, and answer quality that improves without you doing anything. Whether that is worth it depends on how much your own hours are worth and how much you enjoy debugging a plugin conflict on a Sunday.

For a site with real revenue, the subscription usually wins. For a hobby site or a small brochure site, the licence often does.

The plugin is free in both cases. Nothing else about them is comparable.

The WordPress-specific things to check

Page speed

WordPress sites are frequently slow already, and a chat widget is one of the heaviest third-party scripts you can add. Measure a real page before and after installing, on mobile, and write both numbers down.

Two things help. Load the widget after the page rather than before it, which good plugins do by default. And check whether your caching plugin needs to exclude the chat script, because a cached widget state is a common and confusing bug.

Plugin conflicts

The average WordPress site runs twenty or more plugins. Chat widgets commonly collide with cookie consent banners, sticky headers, back-to-top buttons and page builders, all of which want the same corner of the screen or the same JavaScript events.

Install on a staging copy if you have one. If you do not, install at a quiet hour and check your key pages immediately: home, a post, a product page and the contact page.

Updates and abandonment

Check the plugin's last update date and its support forum before you install. WordPress plugins get abandoned, and an unmaintained plugin with a security issue is a genuine risk to a site rather than merely a dead feature. A plugin not updated in over a year deserves a hard look.

GDPR and your cookie banner

If you serve visitors in the EU or UK, a chat widget almost certainly sets cookies and processes personal data. You need to know which cookies, for what, and whether the widget still loads when someone declines non-essential cookies. Ask the vendor directly, because it is rarely on the pricing page and your cookie notice needs the answer.

The question that actually decides it

Most WordPress sites belong to a small business, a freelancer or a small team. Nobody is watching a chat window all day.

So run this test before comparing anything: look at your analytics and find when your visitors arrive. If a meaningful share come in the evening or at weekends, a human-staffed widget is offline for your second busiest window. It will show as offline, which reads worse than having no chat at all, or it will collect messages you answer the next day, which is a contact form with extra steps.

That single observation eliminates half this market for most WordPress sites, in one direction or the other, and everything after it is easier.

WooCommerce changes the requirements

A WordPress brochure site and a WooCommerce store want different things from a chatbot, and the plugin directory does not distinguish them.

If you run WooCommerce, ask two questions no brochure site needs to: can it read live product and stock data, and can it look up an order without the customer logging in. A chatbot that cannot do the second is deflecting nothing that matters on a store.

Multilingual WordPress sites

WordPress runs a large share of the multilingual web, usually through a translation plugin. That creates a specific problem chat vendors rarely address.

Your site exists in several languages. Your chatbot needs to answer in the language the visitor is using, from the content in that language. Ask three things:

• Does it detect the language automatically, or does it need a setting per page?
• Does it read all your translated content, or only the default language version?
• Does each language cost extra? Some tools price languages as an add-on, which changes the sum considerably.

Check your analytics before you assume this does not apply to you. Sites that never planned to be international routinely find a quarter of sessions in another language.

Installing it, and the order to do things in

Three clicks to install, but the order of the next steps prevents most of the problems people report afterwards.

1. Take a backup first. Not because chat plugins are dangerous, but because every plugin install on a live site should start this way and this is the one you will regret skipping.
2. Install and activate, then do nothing else. Load your homepage, a post, a product page and the contact page in a private window. Confirm nothing has broken before you configure anything.
3. Measure page speed now. Mobile, on a real page. Compare it to the number you took before installing. This is your one chance to know the cost.
4. Connect the content. Whether that is your site URL, your pages, or a set of answers you write. This is where connectors and self-hosted plugins differ most in effort.
5. Ask it five real customer questions. From your own site, in a private window. If it cannot answer those, stop and try a different plugin before you spend an afternoon on settings.
6. Then style it. Colour, position, greeting. Last, not first, because it is the part that feels like progress and changes nothing.

If you have a staging site, do steps one to five there instead. If you do not have one and your site earns money, that is worth fixing before your next plugin install regardless of what it is.

Five checks before you activate

1. Is this a connector or self-hosted? Decide which model you want before you read a feature list, because it sets your three-year cost.
2. What is metered, and what is the next tier? Conversations, messages, seats and resolutions are all in use. Find yours and price triple your current volume.
3. When was the plugin last updated? Check the directory listing and the support forum, not the marketing page.
4. What does it do to your page speed? Measure it yourself on mobile. No vendor publishes this.
5. Can it answer from your existing content? If you have to write the answers first, budget that afternoon, and budget it again every time your prices change.

What the free tiers actually cap

Four of the plugins above have a free tier, and each one ends in a different place. Knowing which limit you will hit first saves you migrating twice.

The pattern worth noticing: a free tier capped on contacts or conversations ends quietly, when a busy week uses it up and visitors stop getting answers without anyone telling you. A free tier capped on branding never ends, it just looks like someone else's advert on your site.

Neither is a trick. But decide which trade you prefer before you install, because switching plugins after you have visitors talking to one is more disruptive than choosing carefully on day one.

Pick the free tier whose limit you can live inside for a year, not the one with the biggest number on the pricing page.

Picking, in one paragraph

If your budget is zero and branding on your widget does not bother you, tawk.to. If you want a flat bill and chat is your main channel, Crisp. If your volume is genuinely low and predictable, Tidio's conversation tiers. If you have staff at desks during working hours, LiveChat. If you want a one-time cost and are comfortable maintaining it yourself, a self-hosted plugin like WPBot. If nobody is watching the widget and you want visitors answered from the content you have already written, that is the case for an answering system rather than a chat inbox.

Whatever you choose, install it on a quiet afternoon, check four page types straight away, and measure your page speed before and after. Those three habits prevent nearly every problem people report weeks later.