Live chat
Last updated · A-Widget
| Decision | Tidio | LiveChat | tawk.to | Crisp |
|---|---|---|---|---|
| Best for | A WordPress owner comparing human chat with a later bot workflow | A team with an established human response process | A WordPress team that can own a human queue | A team that wants WordPress chat within a wider message workflow |
| Documented scope | Live chat and help desk; Lyro AI and Flows have distinct usage units; Published free tier has finite allowances | New trials use Text plans with chat, inbox and AI Agent; Essential and Growth charge per user with AI limits; Existing LiveChat plans remain on legacy pricing | Published free live chat service; Optional paid services are separate; Free software still needs staffing | Shared customer inbox; Website chat and plan-based automation; Seats and automation vary by package |
| Trade-off | The plugin does not remove separate usage limits | Service access is separate from plugin installation | Paid optional services remain separate | Package scope determines access and automation |
| Next step | Read Tidio analysis | Read LiveChat analysis | Read tawk.to analysis | Read Crisp analysis |
Choose the chat workflow first. Then confirm the official plugin owner, current listing and supported site versions. A familiar product name in a plugin title does not prove that the listing is maintained by that vendor.
Tidio
Our verdict:
Chat and automation
Best for A WordPress owner comparing human chat with a later bot workflow
Keep in mind: The plugin does not remove separate usage limits
Tidio is a candidate when the site needs a human chat entrance with an option to assess Lyro or Flows. Keep those products and usage units distinct. The WordPress connection is the installation route, not proof that every paid feature is included.
Use the official Tidio plugin listing and its help centre to confirm ownership and setup. Check the current listing's supported versions and update details at installation time. A dated review elsewhere is not a current compatibility record.
Before enabling automation, define the allowed knowledge and a no-answer route. A basic human queue may be the right first step. The bot's availability should not be confused with a person being ready to reply.
The main trade-off is the need to understand separate conversation, AI and flow allowances. See the Tidio pricing reference before treating the free plugin as a full free service.
LiveChat
Our verdict:
Staffed support
Best for A team with an established human response process
Keep in mind: Service access is separate from plugin installation
LiveChat is useful when staff will answer website questions in its support environment. The plugin connects the site to that account. The service's current seat and feature rules still apply after the plugin is active.
Check the current LiveChat WordPress listing and vendor help for the supported setup. Use the business's own account and verify the property identifier. Do not connect users to a developer's unrelated trial account.
Choose the service before the plugin. New trials use Text Essential, Growth or Enterprise, with plan-specific AI Agent allowances. An existing LiveChat subscription keeps its own plan. Check the matching WordPress setup; Text's AI is not the separate ChatBot subscription.
Set the hours and offline route in the service. A plugin can load all night even when the team is away. The greeting should tell the user whether they are starting a live exchange or leaving a message.
Consider another route if your only need is a short inquiry sent for later review. A staffed chat product can add work without improving that task. Match the service model before choosing the plugin.
tawk.to
Our verdict:
Free base chat
Best for A WordPress team that can own a human queue
Keep in mind: Paid optional services remain separate
tawk.to offers free base chat software. That makes it worth inspecting for a WordPress site with a modest human-support task. The business still needs staff coverage, access controls and a rule for private details.
Verify the official tawk.to WordPress listing and current vendor help. Review the optional services separately. A free base chat description does not prove that every branding or staffing option is included.
Check that the correct widget loads after a cache clear and on the live page. If an old manual snippet remains in the theme, enabling the plugin can create a duplicate route. Find and remove the known old installation rather than adding more code.
Choose this approach for the defined human-chat task, not merely because the starting price is appealing. If you need an exact CRM action or automation feature, compare that need against the current help.
Crisp
Our verdict:
Shared inbox
Best for A team that wants WordPress chat within a wider message workflow
Keep in mind: Package scope determines access and automation
Crisp is a candidate when the inbox process matters beyond the first message. Inspect the current package for staff access and any automation you need. Do not borrow a free-seat limit from an old comparison.
Use the official Crisp WordPress listing to confirm the connection route. Its help pages and current pricing establish the wider service scope. The plugin page alone is not enough to compare all paid features.
Decide how a message moves from the first reader to the person who can solve it. That process needs an owner and a visible completion state. A shared inbox can still contain unanswered work if the team has no rule for acting on it.
The trade-off is choosing a package that fits the real workflow. If the site's needs are simple, avoid adopting extra channels merely because the product can expose them. Start with the path staff will use consistently.
Identify whether the site is self-hosted or uses WordPress.com. Plugin and script permissions differ by hosting route and plan. Check WordPress.com support for that account rather than applying self-hosted instructions blindly.
On self-hosted WordPress, inspect the site's supported versions, backups and update process. The chat vendor can document its plugin, but it cannot prove the state of every theme and other plugin on your site. A safe preview helps isolate those site-exact factors.
Open the current WordPress.org listing and verify the author and links. Read update and compatibility details as current evidence. A similar name or a high rating is not a substitute for confirming the publisher.
Review the permissions the setup asks for. Use supported access for the person who owns the service. Keep the website's administrator access separate from routine staff access to conversations where the products allow that distinction.
List the task beside the current service plan. Include human chat, offline handling and any connected automation. The plugin's install button does not prove a free ongoing allowance or an included AI product.
Inspect vendor terms for message content, access and retention. Tell users to use a secure account or payment route for sensitive details. A plugin's presence does not make the surrounding website compliant with every data rule.
Know whether the script is loaded by the plugin, a theme snippet or another connection. Keep one source unless the vendor documents a reason for more. Duplicate loading can confuse both display and troubleshooting.
Check the site's real consent behavior with chat installed. Declining an optional service should not remove key contact details. Preserve a plain route to support if the external widget is blocked or fails.
Back up the site and record the old chat setup. Use a safe copy when possible. Install from the verified official route, connect the correct account and set the supported widget or site identifier.
Configure greeting, hours and message routing before publishing the launcher. Make clear which person handles the queue. A new site connection should not send questions to an old trial inbox no one watches.
Open the live page while signed out. Send a fictional question through the vendor's supported test path. Verify the staff record and a reply back to the user. Check offline handling separately.
On a phone, inspect the position of the launcher and the full open panel. The close control should remain visible. A message should not disappear behind another floating control or force sideways page scrolling.
Use the keyboard to open, enter and leave the widget. Confirm that focus returns to a useful place. A visually neat chat panel can still be difficult to use if it traps focus or hides the active field.
If the widget is missing, confirm the plugin is active and connected before changing cache settings. Then inspect whether an optimisation tool delays or alters the vendor's script. Follow the vendor's documented exclusions when needed.
Check the public page after each targeted change. An administrator's view may bypass the cache that users see. Avoid turning off every site protection just to make the launcher appear; find the exact conflict.
If the widget loads twice, inspect both plugin and theme installation. Remove the known duplicate. Repeatedly pasting a new snippet makes it harder to know which code serves the live widget.
Disable the plugin through WordPress's supported controls, then inspect the live page. If a launcher remains, check for a separate manual installation. Removing a plugin does not necessarily remove a snippet placed by another tool.
Handle the hosted account as a separate task. Conversation data, staff access and a paid plan may remain after the website connection is gone. Preserve open follow-up work before ending the old service.
Use the general installation guide for a full launch checklist. Return to the live chat comparison if the current service no longer fits the team's work.
A fictional site owner installs the plugin as an administrator, but daily chat belongs to a support role. Those are distinct jobs. The setup should work for the person who will read real messages, without giving them broad website access they do not need.
After connecting the service, use the planned staff role to inspect the queue. Send a short fictional question from the public page. Check that staff can read it, reply and mark the work as done under the current service rules.
If that person cannot act, inspect the service role rather than granting full WordPress access as a shortcut. Website editing and conversation handling may be separate permissions. Keep each tied to the job.
Next inspect a theme page where chat should not cover the main action. On a phone, open and close the panel near that action. The same plugin can be present across pages with very distinct layouts. One good homepage view does not prove every important page is usable.
Then check after a targeted cache change. The public user may see an old page while the owner sees the newest one. Note which view failed before changing a second setting. Do not add another snippet to solve a cache problem.
Keep the working plugin, account and placement in a short record. If the business changes chat services later, that record shows what to disable. It also helps prevent a second editor from loading the same service through a manual theme snippet.
Use a short fictional name and question for the setup check. Mark or remove that record through the supported service controls where needed. Staff should not mistake it for a real user waiting for help.
Keep the expected result in the site record too. A later editor can repeat the same useful check after a plugin or theme change without sending a long series of pointless test messages.
Record whether the plugin inserts chat itself or expects a theme setting. Before replacing a theme, keep the working configuration and removal step. After the change, check one complete exchange from a signed-out page. A launcher left in an old template can disappear even though the hosted chat account and staff inbox still work.
A documented public widget identifier can appear in a snippet; a private service API key cannot. If a setup field asks for a credential, confirm in the vendor’s current guide whether it belongs in server settings rather than browser-visible code.
No. A plugin can be free to install while connecting to a paid service. Check the current service plan, its usage unit and any separate automation product. The installation route and the ongoing support workflow need to be evaluated together before calling a setup free.
The official listing and vendor guide establish a supported route and current rules. They do not prove the condition of every site. Check your real theme, versions, cache and consent behavior on a safe copy or controlled change, then inspect the listed user path.
