WordPress website chat: plugin, script, and post-launch configuration

Installing chat on WordPress is not the difficult part of this project. You can add the plugin in a few minutes, and the widget will appear on the website immediately. The real decisions come later: who answers conversations, what visitors see outside business hours, what data enters the system, and whether the additional script hurts performance scores. This guide covers both the technical implementation and that second, more important part.

Plugin or theme script—which should you choose?

There are two ways to add chat to a WordPress website. The first is a dedicated plugin installed from the admin dashboard. The second is to paste a code snippet into the theme, a ‘header and footer scripts’ plugin, or a tag manager. Both produce the same visual result, but they behave differently during updates and when the tool is disconnected. On Squarespace you paste a site-wide script into the Code Injection panel, which not every plan includes, as the guide on adding chat to Squarespace describes.

↔ Scroll the table sideways to see all columns.

For most business websites, a plugin is the more sensible choice because it survives theme updates and leaves you with one place to disconnect the integration. A tag manager script may be better when marketing manages every tool in one dashboard and already has an established change-publishing process.

Step-by-step installation

The sequence below applies to a plugin, but only steps two and three change when you use a script. Everything else remains the same because it concerns configuration in the chat tool, not WordPress.

1. Create an account with the chat provider.The widget needs to know which website it belongs to. Without an account and identifier, the plugin alone will display nothing.
2. Install and activate the plugin.Plugins → Add New → search for the tool’s name → Install → Activate. On multisite, install it at the individual site level if each site has a separate support team.
3. Connect the website.This usually requires a one-time pairing code or a key from the dashboard. Tie the connection to a specific host so a staging copy does not collect production conversations.
4. Check where the widget appears.Decide whether it should run across the entire website or only on selected paths. The cart, checkout, and customer portal usually require separate decisions.
5. Verify it across devices.Open the website on a phone and desktop. Make sure the launcher does not cover the ‘Buy now’ button, consent banner, or mobile menu.
6. Send a test message.Write from an incognito window and answer the message in the dashboard. This is the only reliable proof that the entire path works.

If you use page caching or a CDN, clear the cache after installation. Otherwise, you may keep seeing an old version of the website and search for a configuration error that is not there.

In Meetlead, WordPress is an installable application with a one-time pairing code and a connection tied to the exact host. Credentials are stored separately for each website, including in multisite installations. You can find a detailed list of transferred data and consent modes on the Meetlead for WordPress page. If you also want to take bookings on the same site, placing and testing the form is covered in our guide to a WordPress booking calendar.

Consent and cookie banners—where mistakes usually happen

Chat and behavior tracking are two different things, yet many implementations treat them as one. The ability to send a message may be considered a user-initiated function, while session recording or click maps require a separate decision and a separate description in the privacy policy.

• Launch modeDoes the widget launch immediately or only after the visitor accepts the banner? This setting affects both compliance and the number of conversations.
• Banner integrationIf you use a consent plugin, check whether the chat tool can integrate with it instead of operating alongside it.
• Data scopeA conversation, offline form, and session recording collect different data. Describe them separately, not in a single sentence about ‘analytics tools.’
• Form confirmationName, email, and phone fields in the chat window contain personal data. Associate them with a link to the privacy policy.

This guide is not a substitute for a legal analysis of your website. We discuss the questions worth asking before launch and the categories of data created during a conversation in a separate article on live chat and GDPR. If you also plan to record sessions, read our article on session recording and GDPR—it involves a different data scope and different decisions.

It is also worth considering how much screen space the banner occupies and how it conflicts with other elements fixed to the bottom of the page. We examine this in our article on consent banners and user behavior.

Will chat slow down the website?

Every additional script has a cost. The question is how much and when. A chat widget usually loads after the page content, so its effect on the initial render may be small, but it is not zero—especially on less powerful phones and slower connections.

• Measure the website before and after installation on the same device and connection.
• Check that the widget loads after the content instead of blocking rendering.
• Watch for layout shifts: the launcher should not jump after loading.
• Assess the mobile version separately, because that is where the difference is most apparent.
• If you use recording or heatmap features, measure them as a separate cost rather than grouping them with chat.
• Disable the widget on pages where it serves no purpose—for example, in the customer portal.

An honest caveat: a performance test score is useful, but it is not an end in itself. A website with a perfect score and no way to ask a question does not sell better than one with a slightly lower score and effective support. Monitor both at once instead of sacrificing one for the other.

The settings most often overlooked

Putting the widget on the website is only the beginning. The settings below determine whether a visitor receives an answer or sees a window nobody is monitoring.

1. Availability hours.Set the team’s real schedule instead of claiming ‘24/7’ availability. A visible promise you keep works better than a broad but empty one.
2. Offline mode.Decide what visitors see outside business hours: a form, a callback request, or simply a message. This is the setting most often overlooked.
3. Notifications.Check where new-conversation alerts are delivered. A missed chat is worse than having no chat at all.
4. Pre-chat.Decide whether to ask for details before the conversation. Every required field reduces the number of conversations started, so ask only for what you genuinely need.
5. Department routing.If sales and support are handled by different people, configure routing immediately. Otherwise, conversations will soon become mixed up.
6. Visibility across pages.Pricing and contact pages usually benefit from chat. Documentation or a customer area may be better without it.

We cover the broader process of selecting and implementing a tool, independently of WordPress, in our guide to live chat on a website. If you want chat to engage visitors in specific situations instead of waiting passively, read our article on live chat automation. If your store runs on Shopify, we cover where the code goes in the theme and how to test it in our guide to live chat on Shopify.

Actual Meetlead interface · demonstration data

Scroll the preview sideways or enlarge it to see the details.

WordPress implementation checklist

• One implementation method selected and recorded in the website documentation.
• Website connected to the account, with the staging environment excluded from production conversations.
• Widget visible on the right pages without covering key buttons.
• Test message sent from an incognito window and received in the dashboard.
• Launch mode and consent aligned with the banner and privacy policy.
• Availability schedule reflects the team’s actual working hours.
• Offline mode leads to a form, callback request, or clear message.
• Notifications reach the person who actually answers conversations.
• Performance measured before and after installation, separately on mobile.
• Cache and CDN cleared after configuration changes.

If you have fewer conversations than expected after two weeks, check these in order: widget visibility on the most frequently visited pages, the launch mode in relation to the consent banner, and the number of required pre-chat fields. The cause is most often found in that sequence.