SupportCandy Agentgroup Addon

The SupportCandy Agentgroup Addon is a plugin that allows you to organize support agents into structured groups within WordPress, assigning tickets in a segmented and controlled manner. It's ideal for operations with multiple departments, teams, or distinct workflows. It requires the SupportCandy plugin to be active as a functional base. The main technical benefit is centralizing assignment management without relying on manual processes or scattered configurations.

Introduction to the SupportCandy Agentgroup Addon

When a support operation grows and tickets start arriving from different channels or products, managing who handles what becomes a real bottleneck that slows down responses, creates confusion among agents, and directly affects the end customer's experience in any WordPress or WooCommerce environment.

This module introduces a layer of structural organization on top of the existing ticketing system. Instead of manually assigning each request or relying on informal team conventions, the tool allows you to define agent groups with clear criteria, so assignments are based on real operational logic rather than on current availability.

Imagine a store manager with three distinct product lines and a shared support team. Before implementing this add-on, any new ticket could end up in the wrong hands. With the extension active, groups are configured by business area, and each ticket flows directly to the person with the necessary context to resolve it.

Product overview

Managing support in scaling stores requires a structure that avoids dependence on individual criteria: when service flows lack a defined group logic, the impact is felt in the customer's UX, in the unequal workload among agents, and in the difficulty of generating reliable operational traceability.

Without a solution like this, the support back office operates with ad hoc assignments. A ticket arrives, someone takes it, or it goes unattended, and tracking down who should have handled it is nearly impossible. With the integrated plugin, groups act as intelligent filters within the ticket workflow.

• Without the add-on: Tickets accumulate in a single queue, agents take what they see first, and there is no logic of specialization or balanced workload between departments.
• With the active add-on: Differentiated groups are created by area, product or priority, and tickets are assigned or filtered according to each agent's membership in their corresponding group.
• Observable result: Fewer assignment errors, more consistent response times, and clear traceability of which group handled each request, facilitating internal audits and reporting.

Requirements and compatibility

Before incorporating this extension into the work environment, it is advisable to verify that the SupportCandy plugin is correctly configured and operational, since this add-on depends on its base structure to function: without that active dependency, the group functions have nowhere to anchor themselves or how to interact with the ticketing system.

• Primary dependency: SupportCandy must be installed and have ticket flows running before this module can operate correctly.
• Relevant compatibility in areas of user roles, agent permissions, back-office views, and any assignment automation already configured in the base system.
• Before activating it in production, it is advisable to test it in a staging environment, especially if there are existing automatic assignment rules that could interact with the new group logic.

Key benefits for your operation

• Structured allocation without constant manual intervention: In teams that handle dozens of tickets daily, deciding who handles each one is time-consuming and leads to inconsistencies. This module allows assignment to follow a predefined group logic, freeing the administrator from a repetitive task prone to human error.
• Equitable distribution of the burden among agents: When all the tickets fall to the same active agents, operational burnout is only a matter of time. The tool allows for segmentation by groups so that the workload is distributed more evenly, improving the team's long-term sustainability.
• Clear traceability by department or specialty: Knowing which group handled which type of request is essential for audits, reports, and process improvements. This extension provides that layer of traceability without the need for external solutions or parallel spreadsheets.
• Reduction of errors due to incorrect assignment: When a technical ticket reaches a billing agent, resolution is delayed, and the customer notices. With well-defined teams, this type of diversion is minimized, and the team's expertise is truly leveraged.
• Scalability without manual reorganization: As the team grows, adding a new agent to an existing group is sufficient to integrate them into the already configured workflows. There's no need to reconfigure rules or review each existing assignment.
• Better back-office control for the administrator: Having visibility into which groups exist, how many tickets they manage, and how they behave over time allows for making operational decisions based on real data, not on subjective perceptions of the team.

Key features of the SupportCandy Agentgroup Addon

• Creation and management of agent groups: It allows you to define sets of agents with specific names, criteria, and members. In a store with separate technical and sales support, this means that each area operates with its own logic without interfering with the other.
• Ticket allocation by group: Tickets can be assigned directly to a group instead of an individual, which provides flexibility when the responsible agent is unavailable and prevents the request from being left in limbo waiting for a specific person.
• Filtering and segmented views by group: From the back office, each agent can only see the tickets corresponding to their group, which reduces visual noise and improves concentration on what they are actually responsible for managing.
• Compatible with SupportCandy's automatic allocation rules: By integrating with the base system, groups can participate in already configured allocation automations, extending their reach without disrupting existing flows.
• Access control by group: Agents in one group do not necessarily see tickets from other groups, which adds a relevant layer of operational privacy in environments where different clients or projects require information separation.
• Centralized management from the administration panel: All group, member, and permission settings are managed from a single point in the back office, without needing to access scattered configurations or tools external to the WordPress ecosystem.

Who is this product for?

This add-on is designed for operations that have already moved beyond the stage where a single agent can reasonably manage all support. As the team grows and the types of requests diversify, the lack of a team structure creates friction that no amount of good intentions from the team can compensate for.

• Administrators or technicians who need to control who accesses which tickets and ensure that operational traceability is auditable at any time.
• Teams that manage multiple product lines, clients, or projects from the same facility and need each area to function consistently without depending on the individual judgment of each agent.
• Those responsible for operations or automations who need support assignment to be part of a broader, more consistent and predictable flow, without manual intervention on each ticket.

Real-world use cases

• Store with separate technical support and billing support: A software store with two very different types of requests was facing the problem of technical tickets being sent to billing agents and vice versa, causing delays and incorrect responses. With this module, two separate groups were created, and assignment was no longer random. The result was a significant reduction in first response time and a noticeable improvement in customer satisfaction.
• Agency that manages support for multiple clients from a single installation: Keeping tickets from different clients separate, without agents from one client seeing the requests of another, was a constant challenge. The extension made it possible to create a group per client, with restricted access, allowing each team to operate in its own context without interference or information leaks.
• Store with seasonal peaks and temporarily reinforced equipment: During high-volume campaigns, adding temporary agents to existing teams allowed them to be integrated into workflows without requiring any reconfiguration. Tickets continued to be distributed using the same logic, only with more available capacity in the corresponding team.
• Operation with internal quality support audit: The quality manager needed to know which group had handled which type of ticket to identify error patterns or areas for improvement. With the groups configured, internal reports went from being estimates to structured data, and training decisions became much more precise and justifiable.

Frequently Asked Questions about the SupportCandy Agentgroup Addon

Short description

Organize your support team into structured groups within SupportCandy, assign tickets with defined logic, and eliminate the operational confusion that slows down responses and clutters your store's back office.