Add live chat to your WordPress site in 5 minutes

Most "add live chat to WordPress" guides end at pasting a script into your theme's footer — which breaks on the next theme update, ignores caching plugins, and leaves you with a chat box nobody is around to answer.

This one is the whole job: a plugin, a one-click connection, display rules, and an AI assistant that answers from your own content when you're not there. Five minutes of setup, and about the same again if you want the AI switched on the same day.

Before you start

You need two things: a WordPress site you can install plugins on (6.3 or newer, PHP 7.4+), and a free Leadiosa workspace. No card, no server to run — the chat service is hosted, the plugin is the client that connects your site to it.

If you don't have a workspace yet, create one first; the plugin's connect button can also start you off, and you'll land back in wp-admin either way.

Step 1 — Install the plugin

Download the plugin ZIP from your Leadiosa dashboard under Settings → Installation → WordPress, then in wp-admin go to Plugins → Add New → Upload Plugin, pick the file, install, activate. That's the whole install; there is nothing to configure in a file and nothing to paste into your theme.

The self-hosted build updates itself from leadiosa.com, so you'll get new versions through the normal WordPress updates screen.

Step 2 — Connect your site (one click)

Open the Leadiosa Chat menu that appears in wp-admin and press "Start free — connect my site" (or sign in if you already have a workspace). You'll bounce to Leadiosa, approve the connection, and come back with the site linked.

Under the hood the two sides exchange a short-lived, one-use code rather than a long-lived key, so nothing secret ends up in your browser history, your proxy logs, or a referrer header. If you'd rather do it by hand, the manual path still works: copy the Workspace ID from Settings → General in Leadiosa and paste it into the plugin.

At this point the widget is live. Open your site in a private window and you should see the launcher.

Step 3 — Decide where the widget appears

A chat widget on your checkout is useful. A chat widget on your legal pages usually isn't. The plugin's display rules cover the homepage, individual post types, archives, and an exclusion list — so you can run chat on the pages where buying decisions happen and keep it off the rest.

Press "Verify connection" when you're done; it checks that the widget configuration is actually reachable from your server, which catches the two classic failures early: an aggressive script-delay setting in a caching or optimization plugin, and a Content Security Policy that blocks third-party scripts. Both will block any chat widget, not just this one — better to find out now than from a customer.

Step 4 — Answer from your own content

An empty chat box is a promise you have to keep in person. The point of connecting an assistant is that the twenty questions you answer every day get answered while you're doing something else.

Two things make that useful rather than embarrassing:

• Grounding. Answers come from your knowledge base — your shipping policy, your prices, your opening hours. With nothing relevant to cite, the assistant says so and hands the conversation to you instead of inventing a plausible answer.
• Your rules. You set the tone and the non-negotiables ("never promise a refund", "never quote a delivery date that isn't in the policy"), and they hold even when a visitor pushes.

Filling the knowledge base is the part people expect to hate, and it takes about five minutes to get to a useful first version — see how to build a chatbot knowledge base in 5 minutes.

Step 5 — Choose how much rope the AI gets

You don't have to hand the conversation over on day one. In Copilot mode every AI answer arrives in your inbox as a draft you send, edit, or discard; in Autopilot it replies on its own. Most people run copilot for a week, watch how often they change anything, and then decide. The trade-offs are laid out in Copilot vs Autopilot.

Privacy, briefly

Two defaults worth knowing, because they're the ones a WordPress admin gets asked about:

• Logged-in user identity is off. The plugin can pass a logged-in user's name and email to Leadiosa so operators see who they're talking to, but only if an administrator turns it on. Update your privacy policy before you do.
• The visitor's side is consent-aware. The widget can ask for consent before storing a conversation, and the plugin registers with WordPress's Privacy Policy and Site Health screens, so what it does shows up where your auditors look.

If you run WooCommerce

The same plugin syncs your catalog in the background — product names, prices, stock, variations — so the assistant can answer "is this in stock?" from live data rather than a guess, and can pass what the visitor is currently looking at (and what's in their cart) into the conversation. That's a different article: AI chat for WooCommerce.

What "done" looks like

By the end of this you have: a chat widget on the pages you chose, real-time conversations landing in an operator inbox with browser push when you step away, an offline form that captures an email when nobody is around, and an assistant that answers the repetitive questions from your own words.

The full walkthrough with screenshots lives in the installation docs. If something doesn't appear where you expect, start with "Verify connection" — nine times out of ten it's a caching plugin holding the script back.