SupportCandy - Productivity Suite

Support does not jam from volume: it jams from not knowing where anything is

When a support desk goes badly, the explanation offered is always the same: too many tickets coming in. It is almost never true. What drowns a small team is not the number, it is the fog.

It is the same customer who has written three times about one thing and now there are three open threads, each holding half the information. It is the ticket that needs five steps and nobody remembers whether the third one was done. It is the important matter that sank down the list because it arrived on Tuesday and today is Friday.

None of those problems is fixed by replying faster. They are fixed by organising the work you already have, and that is exactly what this bundle brings: six small tools, none of them spectacular, aimed at precisely those three holes.

What it includes

• Merge tickets: combines several tickets from the same user into one, leaving a note on both so it is clear what happened.
• Checklists: the administrator defines steps and the agent ticks them off as they go.
• Ticket templates: predefined values so cases always come in with the same information.
• To-do list: each agent organises their own steps inside a particular ticket.
• Pin tickets: the important ones stay at the top whatever the sorting does.
• Close silently: close without notifying the customer, for the cases where a notification is pointless.

Merging and checklists are the two that change the day

Merging looks administrative and is the opposite. Three threads about the same problem means three agents possibly working in parallel without knowing it, and a customer receiving answers that contradict each other. Joining them does not save typing: it saves embarrassment.

The checklist solves the other expensive failure, which is the ticket with steps. A migration, a return, an onboarding with verification. When those steps live in the head of whoever started, any handover breaks them. When they live in the ticket, anyone can carry on.

The other four are convenience, and there is nothing wrong with that. Pinning and closing silently are noticeable from day one but they do not change how you work.

The limitation worth knowing beforehand

Only tickets from the same user can be merged. Tickets from different people cannot be joined, and that restriction makes sense: mixing two customers' conversations would mean showing one of them what the other wrote.

But it leaves out a real and frequent case: two people from the same company opening the same issue from different email addresses. There you will still have two threads, and the practical fix is unifying accounts by company rather than expecting the plugin to solve it.

It is worth knowing because that is precisely the scenario where merging is needed most.

Requirements and what it does not do

It is a SupportCandy add-on, not a complete ticket system: without the base plugin there is nothing to extend. It asks for WordPress 5.6 or higher and PHP 7.4 or higher.

It brings no communication channels. It does not receive email, does not handle chat and does not connect to social networks or phone systems: everything it does happens inside tickets that already exist.

It also gives no reports or metrics. If what you want is knowing how long you take to reply or which agent resolves more, this does not measure it.

Alternatives in the catalogue

The other add-ons in the same family cover what this one leaves out: the incoming email one turns emails into tickets, and the knowledge base reduces the tickets that arrive, which is the most effective way to lower the load.

If you are weighing up the whole system rather than an add-on, Fluent Support is the most serious alternative within WordPress. And if you would rather support came with its theme and knowledge base already built, TotalDesk or KnowBase.

Frequently asked questions

Does it work without SupportCandy?
No. It is an add-on and needs the base plugin installed.

Can I merge tickets from two different people?
No. Same user only, so different customers' conversations do not get mixed.

Does the customer find out their tickets were merged?
A note is left on both tickets, so the trail is visible.

What is closing silently for?
For closing duplicates, tests or spam without sending anyone a pointless notification.

Are checklists per ticket or general?
The administrator defines them and they are assigned to tickets; the agent ticks them off as they go.

Does it give team statistics?
No. It organises the work, it does not measure it.