25 WordPress plugins for customer support, tickets and chat

Choose where the team will handle enquiries

Follow an enquiry from arrival to closure. Who receives it, where do you reply and how does a colleague find the exchange if they must take over? A ticket portal installed in WordPress suits a team wanting to manage enquiries in site administration. With a chat or shared-inbox connector, handling generally happens in the associated service. Compare both routes with the same enquiry and record where history is retained.

The twenty-five offerings include local extensions, connectors and specialised solutions. Free and Pro editions of the same tool appear in one entry. To estimate the budget, distinguish a free extension, a free connector that may require a subscription and a trial whose access expires. Amounts and terms correspond to the November 3, 2026 record. Check the price applicable to your account before subscribing. The procedures below are tests to perform.

• Describe the typical enquiry, the person handling it and the response time.
• Shortlist two solutions and compare handling of the same enquiry.

Prepare a test site and separate access

Use an authorised test site and record initial settings. Install directory extensions through Plugins → Add New and activate only one solution at a time. For a commercial product, use the installation file and licence you have. If the connector requests an external account, choose a workspace authorised for trials. Without that access, prepare pages and local settings, then defer verification of the service's widget, messages and permissions.

Create two fictional customer accounts and one agent account. Prepare an open enquiry, then have another agent take over if your team works in shifts. Record the ticket ID, status and next action. Check what each account sees and open direct ticket and attachment addresses in a logged-out session. Also try an attachment address with the other customer. A hidden link may remain accessible to anyone knowing its address.

Use fictional data and a system intercepting outgoing emails. You can read notification recipients, text and links without contacting a real customer. To check external delivery or incoming reply collection, arrange separate trials with an authorised mailbox and corresponding feature. Adapt steps to the installed edition, then remove only tickets, files and accounts created for the test.

• Record starting settings and prepare test accounts.
• Check ticket and file access, then separately test outgoing and incoming messages.

Cost the service and plan its removal

For a local extension, count the licence, email-collection modules and hosting maintenance. For an external service, record seat count, billed unit and history-retention duration. A displayed monthly price may correspond to an annually paid commitment. Specify currency, taxes, renewal and amount due for the chosen edition.

Locate portal pages, access rules and script locations. Remove one insertion at a time and check that replacement contact works, both logged in and out. Handle open conversations and any service cancellation separately. Record the owner and next action of every enquiry in the original inbox, then export necessary data if the offering permits. To undo removal, restore the page or script and settings. A complete database restoration could erase enquiries arriving since the backup.

• Compare costs of the licences, seats, modules and volumes you need.
• Remove the widget or portal and check replacement contact.

Fluent Support

For a small team primarily receiving written enquiries, start with the customer portal and ticket handling in WordPress. Tracking must remain understandable when another agent takes over. Open a ticket through the portal, reply in administration and check that the customer finds the message and case status. If your team wants to receive replies by email, assess that feature separately in the edition offering it.

In Fluent Support → Settings, locate the customer portal page. The [fluent_support_portal] shortcode displays this portal on a test page. Keep registration closed and use prepared accounts. The registration form depends on the WordPress setting. Give the second customer the direct address of the first customer's fictional ticket to check access denial.

• Submit a ticket and find it in administration.
• Reply as an agent, then reopen the portal with the customer account.
• Check both customers' permissions before assessing incoming collection.

SupportCandy

SupportCandy suits a team defining its own fields and statuses. Add an internal reference field and two statuses corresponding to concrete actions, such as an enquiry awaiting handling and one awaiting the customer. Assign the same ticket to two agents successively. The second must find the exchange and understand who should act next. Check the customer-side result. If replies must also arrive by email, reserve a mailbox for this trial and check which edition covers incoming collection.

• Configure the field and two statuses in the test portal.
• Have another agent take over the enquiry and check what the customer sees.
• Check incoming-collection scope before connecting a mailbox.

Awesome Support

If you want to add automations gradually, start with submission and reply. Keep one open and one closed ticket to compare their display before and after a theme change. This shows whether form presentation changes while history stays accessible. Also check the message received by the requester when the agent replies.

Installation creates the My Tickets and Submit ticket pages. Add their links to the test-site menu and submit an enquiry with the customer account. Then compare My Tickets access with another customer's access. The commercial public-ticket module serves a different use from this private portal.

• Locate submission and tracking pages in the installed version.
• Compare viewing the same ticket with both customer accounts and while logged out.
• Read the intercepted notification and check display with the theme used.

JS Help Desk

JS Help Desk suits enquiries distributed between several departments. Create two fictional departments, for example registrations and billing, and assign agents. Submit an enquiry to the wrong department to check rerouting and permissions after transfer. If you accept enquiries without an account, check how requesters find their conversation and what information is requested.

Open Help Desk to complete page, sending-address and agent settings. The [jssupportticket_addticket] shortcode handles entry and [jssupportticket_mytickets] tracking. [jssupportticket] brings the portal together. Reserve these calls for test pages to identify which screen is involved if access fails.

• Configure two departments and check their agents' permissions.
• Submit an enquiry to the wrong department, then reassign it.
• Check tracking according to the selected guest or logged-in mode.

WSDesk

For store-related support, start with the free edition and an enquiry citing a fictional order. Check which order data the agent can view from the ticket. Mailbox connection and automatic rules depend on the offering. Finish the web-form test first. If incoming collection is needed, then check the corresponding module and test mailbox. The form and email reply must produce outcomes you can check separately.

• Create a ticket from the store's web form.
• Record order information visible to the agent.
• Check the required edition before testing email collection.

Support Genix

Support Genix may suit a team wanting to manage tickets and reference answers in one place. Create a help article on a fictional subject, then open a ticket on that subject. Check that the agent finds the enquiry and can reply with the article link. Use this human workflow as a comparison point for deciding whether an AI feature adds value to the service.

The Support Genix menu lets you find created tickets. If considering an AI feature, record the required provider, consumption terms and licence coverage. The banner's “AI” label does not provide that information.

• Prepare a help article and submit an enquiry related to its subject.
• Reply as an agent with the link and verify receipt.
• Separately price the licence, integrations and any AI-provider use.

tawk.to

For a support shift ending at noon, check the transition from chat to the offline form. Choose the timezone and a short window. Leave a message after closing and find it in the operator interface. A contact link must remain accessible if the widget is unavailable. The November 3, 2026 record distinguishes 39 dollars per month and 348 dollars per year for branding removal, per property.

In Settings → Tawk.to, select the test property and widget, set their visibility, then save with Save Changes. Widget hours and content are configured in the service dashboard. If a message appears missing, compare the displayed ID with the selected property's ID.

• Connect the test property and check that only one widget appears.
• Schedule a break and open the offline form without an administrator login.
• Pick up the message on reopening and check the reply address.

Tidio

Tidio merits a trial if you need to budget for conversations of varying duration. Connect an authorised workspace, then simulate a short human conversation, an interrupted exchange and resumption the following day. Compare what the service counts in each case. Flows and Lyro quotas concern different uses. Check their units in the intended plan and retain human handling as a reference for later assessing the value of an automated flow.

• Open the widget from the contact page.
• Handle a message, interrupt the exchange, then resume the following day.
• Reconcile observed counters with units billed in the offering.

Crisp

Crisp suits a team where two people cover different shifts. Connect the test workspace and schedule availability using the offering's options. Observe the widget when only one operator remains, then when the whole team is absent. Compare hiding the widget with the journey allowing visitors to leave a message. Before choosing the latter, check how the reply address is collected and which seats or modules are required for handover.

• Test availability with one operator, then with the entire team offline.
• Leave a message and check that the operator can reply after the browser closes.
• Check cost per workspace and the offering required for an advanced absence flow.

Chatra

Chatra may suit an operator alternating live coverage and deferred replies. Compare information given to visitors when the operator is available or absent. Then leave two messages, one with a reply address and one without. Check when the team can continue the exchange after the page closes. The November 3, 2026 record distinguishes the WordPress listing from the Messenger grid. For budgeting, check the latter's price for the selected agent count and payment schedule.

In the service, open Chat Widget and copy the authorised workspace's code. Paste it into Settings → Chatra chat, then save. Disable the old insertion if the theme or a tag manager already adds the widget. You can then attribute observed behaviour to the correct connector.

• Connect the widget to the authorised workspace and check insertion.
• Compare resuming a message with and without a reply address.
• Record agent count and monthly or annual billing.

Smartsupp

Smartsupp merits a trial if the team must find a conversation several days after closure. Create two recognisable exchanges, close one and ask the person on duty to find it. Compare plan retention duration with the usual follow-up interval. If available history is too short, plan other tracking or choose a suitable offering. Price Mira separately. Also check that the page's contact link remains accessible when the widget is closed.

• Identify the chosen plan's history duration.
• Find a closed exchange and examine resumption options.
• Compare the team's follow-up interval with terms in the November 3 record.

JivoChat

If your team already uses JivoChat, record how the widget is inserted and which connector version is active. The entry indicates the last update and WordPress version up to which the publisher declares testing. For a newer installation, confirm support before selecting the connector. Then check display, notifications and widget removal with the insertion method used. For a new site, examine this maintenance point before comparing per-agent prices.

• Identify connector version and widget insertion point.
• Open an exchange, check the notification, then verify widget removal.
• Confirm compatibility with the target version before choosing the tool.

LiveChat

The LiveChat connector may suit a team planning to handle enquiries in the Text platform. Connect the authorised workspace, have one user reply, then ask a colleague to take over the conversation. Count seats needed for this handover. Read the new-customer grid separately from terms for existing LiveChat accounts. Identify which applies to your workspace before calculating cost. If considering an AI feature, also record billed units and limits.

• Identify the contract attached to the workspace used.
• Have two users handle a conversation successively.
• Compare seats and quotas with the applicable offering.

Formilla

For single-person coverage, open then close an exchange and observe what visitors see when the operator leaves their station. If the team wants to send files, identify the offering covering this feature. Then test a fictional document and check who can open it. The equivalent monthly price in the entry corresponds to an annual term paid in full.

In the Formilla Chat menu, open Get Started. The operator's presence in the web dashboard makes chat online. Log them out to examine offline state. If the fifteen-day Premium trial is running, record which features remain in the permanent free plan before choosing.

• Observe chat with the operator logged in, then offline.
• Check access rights to the fictional document if file sharing is needed.
• Record total annual payment and features remaining after the trial.

Chatway

Chatway may support coverage by one person, then shared with a colleague. Identify the workspace shown in settings and check which account occupies the available seat. Ask the second agent to take over a conversation. The recorded Business plan provides two seats with annual or monthly billing. Compare this scope with the number of people needing to act simultaneously, including during cover, before comparing it with a per-agent rate.

• Connect the authorised workspace and check the account administering it.
• Have an enquiry handed over and record permissions needed by the second agent.
• Compare included seat count with coverage needs.

HelpCrunch

If the team wants to manage the inbox and documentation in the same service, prepare a help page with a chat link. Send an enquiry from that page and check what context arrives in the inbox. To estimate cost, count users, emails and AI conversations separately. Note the temporary trial's end date and the day the team will decide to continue or remove the widget.

In HelpCrunch, open Settings → Channels → Website Widgets. Record the widget name and workspace before changing display. If abandoning the trial, remove the WordPress connector and separately close the trial in the management workspace.

• Check the journey from help page to inbox.
• Record user count and billed volumes.
• Plan connector removal and trial closure if abandoning the offering.

ThriveDesk

To test the shared inbox, open an enquiry citing a fictional order and have a second agent take over. Record order information visible and actions offered to each. Limit verification to viewing permitted by the role. Read shared-inbox cost separately from connector cost. Check whether the agent taking over has context without searching for the order elsewhere.

In ThriveDesk → Overview, check the connected account. The Integrations tab distinguishes WooCommerce from other integrations. The portal can be placed with [thrivedesk_portal] on a test page. Compare this journey with the Support tab in WooCommerce My Account when enabled, then check that another customer cannot view the enquiry.

• Create an enquiry linked to a fictional order.
• Check commercial information accessible to each agent.
• Have the enquiry handed over in the shared inbox and count required seats.

LiveAgent

LiveAgent merits a trial if you want to handle several channels in one inbox. Start with a chat exchange and check where the service classifies it and whom it assigns. Add telephony only if your need and offering cover it. Associate every promotional price with its payment schedule. If an AI feature requires a provider key, identify that dependency and terms before deciding to activate it.

In the LiveAgent menu, choose the chat button and save. Agents reply in the external dashboard. On November 3, 2026, the WordPress FAQ mentioned a free plan with seven days' history, while the commercial grid presented a trial and paid offerings. Confirm the plan offered to a new account before relying on permanent free use.

• Check classification of an exchange and deferred resumption if the offering permits.
• Find the owner and status in the service inbox.
• Separately price the plan, channels and any external-provider use.

WPHelpDesk

If WPHelpDesk is already installed, record version and active modules. Submit a fictional ticket and follow its reply, notification and closure. If your team must handle replies received by email, identify the module adding this feature to the commercial core. Maintenance information available on November 3, 2026 leaves compatibility with your environment to be confirmed. Before committing to a new installation or history migration, check supported versions and support terms.

• Record version and active modules.
• Have a ticket handled and closed, checking the outgoing notification.
• Confirm maintenance and identify the offering covering incoming collection.

Olark

If your team already uses Olark, start by locating how the widget loads. Check that only one insertion operates, then observe a human exchange, closure and resumption when the operator becomes available again. Compare versions declared in the entry with your installation. Price human-chat per-agent cost and the AI offering separately. Chat and its history suffice for an initial test.

In Settings → Olark Settings, check Site ID and chatbox activation. Compare the ID with the authorised workspace's and keep it out of public reports. If the theme already inserts a script, remove only that insertion from the test site before trying the connector.

• Locate the script or connector and check that it loads the widget only once.
• Test opening, closing and resuming an exchange.
• Check connector maintenance before comparing AI offerings.

Lime Connect — Userlike family

Lime Connect and Userlike designate the same family here. Check the displayed service name when connecting the connector to the existing workspace. Send a message from the site and track its channel and status after closing. If several channels are needed, check each path to the inbox and plan terms. Also confirm what the account allows after the trial ends.

In the service, retrieve Widget Secret under Install → Javascript widget code. Enter it in the authorised test-site settings and keep it out of the page and shared screenshots. The Userlike name may remain visible in this same connector's settings.

• Match the Userlike name with the Lime Connect account used.
• Send a message and check which channel it arrives through.
• Confirm the plan and channels available after the trial.

Help Scout — BoldGrid connector

The BoldGrid connector can display Beacon on a help page. Connect the authorised workspace and check that display first. Then test enquiry entry and arrival if you plan to use the form. According to the connector FAQ, this feature requires a plan granting service API access. Check this condition even if your account has a free plan and Beacon already appears.

The [hsd_form] form uses Application ID, App Secret and Mailbox ID in connector settings. Check API permission and the associated mailbox before test submission. Keep these identifiers in connector configuration, outside page content.

• Check Beacon display with the BoldGrid connector.
• Confirm API access intended for the form and destination mailbox.
• Send a fictional enquiry, find it in the inbox and check the reply link.

TotalDesk

TotalDesk may suit taking over an installation already combining tickets, chat and documentation. Identify the installed edition and licensing channel. Then check enquiry submission, reply and opening a documentation link. The WordPress version indicated and update date appear in the entry. Confirm maintenance and support for your target installation before deciding. The direct contract and CodeCanyon licence have different payment schedules to include in the budget.

• Identify the edition and contract already used.
• Test submission, reply and documentation link.
• Confirm compatibility and support for the target installation.

Support Board — WordPress

Identify the WordPress edition and licence before installing Support Board. The PHP-script edition follows another route. Start with human chat using the available WordPress version and follow an exchange from widget opening through pickup in the handling interface. Then list necessary channels, additional applications and any model providers. For every addition, check the required licence or service, then test the relevant channel.

• Identify the WordPress installation file and licence type.
• Handle a human exchange before adding other channels.
• Check applications, providers and terms needed for each extension of the journey.

WooCommerce Support Ticket System

This plugin targets stores wanting to attach an enquiry to an order. With the version already available, prepare a fictional order and have the customer open a ticket. The agent must find the link to the correct order and check where replies appear. Then try viewing the enquiry with another customer account. The recorded listing indicates the author provides no support for this item. Assess your ability to handle a conflict or WooCommerce update before selecting the tool.

• Check the licence and support condition in the entry.
• Create an enquiry linked to a test order and check the other customer's rights.
• Remove the module and check how ongoing enquiries remain accessible before deciding.

Further reading

• 25 WordPress form plugins to choose according to your needs
• 25 WordPress plugins for emails, newsletters and sending logs
• bbPress or wpForo for a public support forum?