Choosing an AI chatbot for WordPress involves two decisions: which conversation service fits your business, and how that service will run on your particular website. A plugin can make installation easier. It does not, by itself, prove answer quality, compatibility, or a successful handover to your team.
Start with a visitor task you want to improve. That might be explaining a service, helping someone find the right guide, qualifying an inquiry, or answering a product question. Then evaluate the tools against that task on your actual theme, hosting setup, and mobile layout.
Editorial correction, October 4, 2026: The earlier version claimed hands-on tests without supporting evidence and included unsupported prices, feature comparisons, and performance guarantees. We replaced those claims with a sourced shortlist and a practical evaluation process. This is not a ranked benchmark. LoopReply publishes this guide and is included as an option.
A shortlist organized by the existing workflow
| Option | Documented WordPress approach | Reason to include it in your evaluation |
|---|---|---|
| Tidio | Official WordPress plugin | You want to evaluate live chat and its advertised Lyro AI features together |
| HubSpot | Official WordPress plugin | Your lead collection and customer records already depend on HubSpot |
| Crisp | Official WordPress plugin | You want to assess the chat experience and operator workflow |
| LoopReply | Embeddable website widget | You want to configure an Agent around approved knowledge and conversation workflows |
Tidio's official plugin listing describes live chat, AI, and WordPress installation. Confirm the AI allowance and features available in the account you will use. A plugin download and a paid service subscription are different decisions.
HubSpot's official plugin listing includes forms, live chat, and chatbot-related functionality alongside its CRM connection. If your team already uses HubSpot, evaluate how the conversation fits the existing customer record. Confirm which AI and automation capabilities require a particular HubSpot subscription.
Crisp's official plugin listing provides a WordPress installation route for its chat service. Include the operator experience in your trial, then verify the specific automation and AI features of the selected plan.
LoopReply adds a website widget through its installation snippet. An Agent can use supplied knowledge, configured conversation workflows, and human handover. There is no claim here that LoopReply has a native WordPress or WooCommerce plugin. Commerce-specific data access needs the relevant API configuration and authorization checks.
This shortlist is a starting point. Prefer two well-scoped trials to opening accounts with ten tools and testing each with one easy question.
Check what your WordPress installation permits
Before choosing an installation method, identify who controls scripts on the site. Your hosting service, WordPress permissions, security tools, and deployment process can affect what is allowed.
WordPress's Custom HTML documentation explains that users without the required capability have disallowed markup, including scripts, removed when content is saved. Pasting a widget into a page block may therefore be unsuitable for your role or setup.
Use a vendor's maintained plugin where appropriate, or an approved site-wide script insertion method managed by the person responsible for the site. Avoid editing a parent theme's PHP files simply to insert a chat snippet. Record where the code was added so the next administrator can find and remove it.
Check that the widget is installed once. A snippet in both the theme and a plugin can cause confusing behavior and unnecessary requests. Test in a private browsing window while signed out of WordPress; an administrator's preview may not show what visitors receive.
Define the knowledge the Agent may use
Begin with a small source pack. For a service business, this could contain a current service overview, working hours, delivery process, and an explanation of how to request a quote. Each answer should have an owner and an approved source.
Ask questions that require clarification. For example, a visitor asking about cost may need to provide the service type or project size. The Agent should follow your approved response instead of inventing a quote because the source is incomplete.
Then test changes. Update one policy, remove one outdated page, and ask the affected questions again after processing completes. Check what the service shows when a source fails to refresh. A system that retains the previous version should make its freshness understandable to the operator.
LoopReply supports documents, website sources, CSV and Excel files, and configured database sources. Those capabilities still require readable input, appropriate scope, and verification of the resulting answers. Our spreadsheet checklist gives a concrete way to check structured data before relying on it.
Verify layout and loading on your site
Do not accept a blanket claim that a widget has no effect on performance. A script can load asynchronously and still add network requests, processing, or visual movement. Compare representative pages with the widget enabled and disabled using the same test conditions.
Include a landing page, a long article, a contact form, and any important conversion page. On mobile, open the keyboard and send a message. Check that the conversation remains usable and the close control stays reachable.
Use keyboard navigation to open and close the widget. Check visible focus, readable text, and whether the interface interferes with page navigation. Test alongside cookie controls, sticky navigation, and other floating buttons. Overlapping controls can make an otherwise functional widget frustrating.
Run these checks with caching and optimization settings enabled. If a setting delays or combines scripts, verify the actual visitor experience after deployment, not only the uncached editor preview.
Treat human handover as a complete workflow
Ask to speak with a person during a conversation and follow the request through to the receiving inbox. Confirm that the assigned operator can read the context and reply from the intended account.
Now test outside your team's working hours. Decide whether the visitor should leave contact details, return later, or use another support route. The wording should match the support you can provide. Do not promise an immediate reply when nobody is scheduled to respond.
Include a question the Agent cannot answer from its sources. A useful failure response identifies the limit and offers an appropriate next step. Count an unsupported but confident answer as a failure, even if it sounds polished.
Compare the full cost of running it
Create one workload estimate and use it for every vendor. Include expected conversations, AI usage, operators, websites, integrations, and the support features you actually need. Check how each plan defines its allowance and what happens after the allowance is reached.
Also include your own effort. Someone must keep the content current, review unanswered questions, maintain integrations, and verify the site after plugin or theme changes. A lower subscription price may involve more implementation work; a larger suite may include features you do not use.
Use the current LoopReply pricing page and each vendor's current offer for a dated quote. Keep a copy of the applicable terms with the evaluation. This guide avoids a fixed ranking based on starting prices that may cover different workloads.
Launch with a measurable scope
Keep the first release focused on a manageable set of questions. Record a baseline of the inquiries your team receives and the time needed to resolve them. After launch, review actual conversations and classify the result: answered appropriately, clarified, handed over, or failed.
Inspect the failures before expanding the Agent's scope. They may reveal missing content, an unclear instruction, an integration problem, or a support process that needs an owner. Each cause calls for a different fix.
For WooCommerce-specific work, use our storefront evaluation guide to separate public product answers from private order access. For a general WordPress site, choose the service that fits your workflow and passes the installation, knowledge, and handover checks on your own pages.
Install the generated script on a test page
In LoopReply, open the selected Agent's Website Embed page and copy the generated script. In WordPress, use your site's established footer-code tool, save, and clear the page cache. Open the public page in a signed-out browser so an administrator-only preview cannot hide a failed installation. WordPress.com's code guide explains its plan-dependent script permissions.
The image shows LoopReply's actual installation interface with example identifiers, not a WordPress administration screen. Use your own generated values. Verify one launcher, a working composer, and a source-backed reply on desktop and a phone. Repeat on the busiest template, with consent and optimization plugins active. We have not established compatibility with every WordPress theme or plugin.
The full installation tutorial includes the HTML and failure checks. For a store, continue with the WooCommerce guide; for an alternative installation route, examine Tidio's current offer.