Find your fit
Who it is for
It fits an organization that already runs WordPress and wants a support portal within that site. Teams can begin with web tickets and existing WordPress users as agents, then assess premium email intake, automation or SLA tools if their process needs them.
Because tickets live in the WordPress environment, a buyer should assign responsibility for site hosting, access, plugin updates, backups and mail delivery. A pilot should check the actual workload and mail path rather than assume the plugin alone supplies those operations.
The work it supports
Core capabilities
The support page can show the portal, new-ticket form, list and ticket details. Separate WordPress pages can expose only a new-ticket form or a ticket lookup page. This gives a site owner a choice between a full portal and a simpler submission path.
Support agents must first exist as WordPress users. Their SupportCandy roles determine whether they can see or act on unassigned, own and other agents’ tickets; permissions include replying, assigning and recording private notes. Start with a narrow role for each team member.
Agent queues include unassigned, mine, unresolved and closed filters. Customers have their own all, unresolved and closed views for tickets they created. Agent and customer list columns can be configured independently, so review each view before exposing new fields.
A ticket form can include configured ticket and customer fields, including required fields and fields that appear only under conditions. Create a custom ticket field first, then add it to the form; name and email remain mandatory form elements.
Ticket statuses can be tailored to a support process, including what happens after customer or agent replies. Customers cannot directly change a ticket’s status after creation. Agent-only fields can hold internal context, but administrators should review customer list settings and role access before recording sensitive information.
Email templates can react to ticket events and route messages to selected recipients. Notifications start disabled; the site needs a configured SMTP plugin and enabled notification rules. Send a test ticket and check each intended recipient before relying on the messages.
Premium Email Piping brings inbound support email and email replies into the ticket conversation. It is a separate extension, so test the mailbox connection, ticket creation and both sides of a reply before treating email as a working support channel.
Premium Workflows can act on ticket events through triggers, conditions and actions such as assigning an agent, changing status, adding a reply or making a private note. Premium SLA tooling adds response and resolution tracking. These are add-on capabilities; test automation with fictional tickets before using it on customer requests.
Understand the offer
Pricing and getting started
The core SupportCandy plugin does not need a licence key. The vendor says it does not cap the agents or tickets you can host. Premium extensions require valid licences, and the current pricing page offers site-count tiers. Check the actual extension bundle and site count at purchase; WordPress hosting and mail operations remain separate costs.
The vendor says add-on licences automatically renew yearly. If a licence expires, installed add-ons may still run, but updates and premium support stop. The vendor says there is no trial for add-ons and advertises a 14-day money-back guarantee; confirm the current refund and renewal terms before paying.
Look a little closer
Before you choose
Try the whole portal flow with fictional tickets: submit a form, inspect agent and customer lists, assign an agent, add a private note, reply and move the status. Confirm each role sees only the intended tickets and internal fields, and inspect the customer view after each change.
Before enabling email, configure SMTP and notifications separately and verify delivery. If email intake is required, budget for the premium Email Piping extension and test its mailbox connection. Likewise, buy Workflows or SLA only after the team has mapped an actual rule or response target to those extensions.
17 distinct sources behind this profile. Research observed Oct 19, 2026. Features and offers can change.
View sources and research →
