SupportCandy Usergroup Addon
$39.00 Original price was: $39.00.$4.99Current price is: $4.99.
The SupportCandy Usergroup Addon is an extension for the SupportCandy support system that allows you to segment agents and customers into user groups with different permissions and visibility levels. Ideal for multi-team or multi-departmental operations, it eliminates cross-exposure of tickets and centralizes access control from the WordPress back office without repetitive manual configurations.
Introduction to the SupportCandy Usergroup Addon
When a WooCommerce store grows and the support team is divided into departments —pre-sales, after-sales, technical, financial— managing which agent sees which ticket becomes a real confidentiality and operational efficiency problem that no native SupportCandy configuration can solve on its own.
This add-on introduces a layer of structural segmentation on top of the existing ticket flow. It doesn't alter the core of the support system, but rather adds grouping logic that filters visibility, assignment, and access based on the group each user belongs to. This reduces assignment errors and prevents sensitive customer information from reaching agents who shouldn't handle it.
Imagine a back-office technician who receives renewal tickets, technical issues, and billing inquiries all mixed together in their inbox every week. With this tool, the administrator defines separate groups, assigns each agent to their area, and tickets flow only to the appropriate person, without manual intervention in each case.
Product overview
Managing support in high-volume stores requires access structures that preserve operational consistency, avoid allocation bottlenecks, and ensure that each team works only on the cases that belong to them, without noise or unnecessary exposure of customer data.
Without this extension, all agents have access to a shared ticket pool. The administrator wastes time manually redirecting tickets, agents work with irrelevant information, and customers may receive responses from people with no context about their case. With the add-on active, the structure changes permanently.
- Without the add-on: Support tickets accumulate in a shared inbox without segmentation, resulting in incorrect assignments, delayed responses, and data exposure between departments.
- With the active add-on: The administrator configures user groups with visibility and assignment rules, so that each agent only sees and manages the tickets that correspond to their group.
- Observable result: Response times decrease because each agent works in their area, assignment errors disappear, and ticket traceability is clean from the first contact to closure.
Requirements and compatibility
Before incorporating this module into your environment, it is essential to verify that the main SupportCandy plugin is present and active, as this extension operates exclusively as a complementary layer on top of its data structure and ticket flows, without functioning independently.
- Direct functional dependency on SupportCandy base: without it, this add-on has no operational context or tables to act on.
- Compatible with WordPress environments that use custom roles, multiple user management, and ticket flows segmented by category or department.
- In stores with complex WooCommerce automations—such as product type assignment, routing rules, or CRM integrations—it's advisable to validate the behavior in a staging environment before applying changes to production.
Key benefits for your operation
- Noise reduction in shared trays: When all agents see all tickets, no one knows for sure what to address first. This module segments visibility by group, so each agent works on a clean and relevant inbox. The result is less wasted time and faster actual response times.
- Granular access control without continuous intervention: The administrator defines the group rules once, and the tool automatically applies them to each new ticket. There's no need to manually reassign tickets or check other people's inboxes. This frees up operational time that was previously spent on internal coordination.
- Clear traceability by department: When a ticket escalates or is audited, knowing which group handled it and which agent was involved at each stage is critical. This extension maintains that traceability, facilitating internal reviews and improving accountability within the team.
- Reduction of confidentiality errors: In stores that handle customers' financial, medical, or legal data, cross-exposure of tickets between departments is a real risk. The add-on acts as a functional barrier, ensuring that only authorized agents access each type of case.
- Scalability without added complexity: As the team grows, adding new agents to an existing group is seamless. There's no need to reconfigure rules or create new structures. The established logic naturally extends to new members, keeping operations organized even if the team doubles in size.
- Better experience for the end customer: When a ticket consistently reaches the correct agent from the outset, the customer receives a faster and more relevant response. This consistency builds trust and reduces the re-contact rate due to unresolved issues—something every store operator wants to see decrease.
Featured Features of SupportCandy Usergroup Addon
- Creation and management of user groups: The administrator can define independent groups that group agents by department, specialty, or access level. Each group operates as a separate functional unit within the ticketing system, allowing for complex support structures without sacrificing operational clarity.
- Ticket visibility restricted by group: Agents only see tickets assigned to or accessible within their group. This restriction is not merely visual: it prevents direct access to external ticket data, thus strengthening internal security and preventing unwanted intervention in ongoing cases.
- Automatic group-based assignment: When a ticket enters the system and meets certain conditions, it can be directly assigned to the corresponding group without administrator intervention. This reduces the latency between ticket receipt and the first response, a factor that directly impacts customer satisfaction.
- WordPress role compatibility: The tool works with the existing role structure in WordPress, making it easy to integrate into environments with a defined user hierarchy. It doesn't require rebuilding the permissions architecture from scratch; instead, it leverages what's already been configured.
- Filters and views differentiated by group: Each group can access custom filters and views within the support dashboard. Agents in a group see metrics and statuses relevant to their area, without information from other departments that could cause confusion or distract them.
- Centralized control from the back office: All rules, groups, and assignments are managed from a single panel in the WordPress back office. There are no external consoles or scattered configurations. The administrator maintains a unified view of the support structure and can modify groups without affecting the active ticket flow.
Who is this product for?
This add-on is designed for operations where the support team no longer fits within a single shared inbox. If you have multiple departments responding to tickets, or if your customer information requires real access control, this extension addresses that exact need.
- Administrators or technicians who need to control which agent accesses which tickets and maintain traceability by department without constant manual monitoring processes.
- Teams that manage multiple product lines, brands, or stores under the same WordPress and need the support for each one to operate in an isolated and consistent manner.
- Operations managers or UX professionals who have noticed that response times are suffering due to incorrect assignments and want a structural solution, not an internal coordination patch.
Real-world use cases
- Store with separate technical and commercial support: A software store sells licenses and provides after-sales technical support. Sales agents shouldn't have to see bug tickets, and technicians shouldn't need to be involved in price negotiations. With this module, each team operates in its own lane, tickets reach the correct department from the start, and customers don't have to wait through internal routing that delays resolution.
- Marketplace with independent sellers: A platform with multiple vendors requires that each vendor's support team handle only the tickets for their own customers. Without segmentation, an agent from one vendor could access another vendor's issues, leading to confidentiality conflicts. This extension creates groups for each vendor, isolates their tickets, and allows the platform administrator to monitor everything from a global view.
- Ecommerce operation with a growing team: A store that has grown from two to ten agents in twelve months needs to structure its support without having to reconfigure everything from scratch. The add-on allows you to create new groups as departments are added, assign new agents without altering existing rules, and keep operations organized even as the team continues to grow. The administrator gains scale without losing control.
- Business dealing with sensitive customer data: A clinic or practice using WooCommerce to manage services needs to ensure that each client's data is only accessible to the team directly serving them. Cross-exposure isn't just an operational issue; it's a legal risk. This module guarantees that agent groups only access their own clients' tickets, transforming a compliance requirement into a manageable feature from the back office.
Frequently Asked Questions about the SupportCandy Usergroup Addon
Do I need to have any other plugins installed for this to work correctly?
Yes, this extension requires the SupportCandy base plugin to be active on your WordPress site. Without it, there's no ticket structure to work with, and the module lacks functional context. If you already use SupportCandy to manage your support, this add-on integrates directly with that base without requiring any additional tools. It's important to ensure both are up-to-date and properly configured before applying changes to your production environment.
How does this affect the customer experience when opening a ticket?
From the customer's perspective, the ticket opening experience doesn't visually change. What does change is that their request reaches the correct agent from the very beginning, without internal redirects or reassignment waits. This translates into faster, more contextualized responses, which the customer perceives as better service quality even if they don't see the internal logic behind it.
Can I set up automatic rules so that tickets are automatically routed to the appropriate group?
Yes. One of the core features of this module is precisely automatic group-based assignment. The administrator defines the conditions under which a ticket should be assigned to a specific group—by category, request type, customer origin—and the tool automatically applies that logic to every incoming ticket. This eliminates continuous manual intervention and ensures consistent routing, even during peak periods.
Does it have any effect on payment reminders or tickets generated by failed renewals?
If your system automatically generates tickets for failed payments or pending renewals, this module allows those tickets to go directly to the finance or billing team, bypassing general technical support. This avoids confusion, speeds up collections management, and ensures the customer receives a response from the relevant department with accurate context regarding their payment status.
Does it affect the management of coupons, taxes, or shipping within the tickets?
It doesn't directly affect WooCommerce's coupon, tax, or shipping logic. Its function is to segment ticket access and visibility. However, if your team handles issues related to these elements—such as a customer reporting an unapplied discount or a problem with the shipping calculation—this plugin ensures that the ticket reaches the agent with specific knowledge in that area, improving the quality and speed of resolution.
How does the system behave under a high volume of tickets and concurrent users?
The extension operates on the SupportCandy database and logic, so its performance is closely tied to that of the main plugin and the hosting environment. Under high-volume conditions, grouping can lighten the perceived load for each agent by reducing the number of tickets visible in their inbox. However, in very high-traffic environments, it's advisable to monitor overall database performance and evaluate caching configurations compatible with the ticketing system.
Does it work well on WordPress installations with multiple stores or sites?
In multisite environments, behavior depends on the network configuration and whether SupportCandy operates at the individual site or network level. In installations where each store has its own instance of the plugin, this module can be configured independently at each site, allowing for different support structures for each store without interference. For more complex networks, it's advisable to validate the behavior in a staging environment before applying it globally.
How can I verify that group segmentation is working as expected?
There are clear signs that the module is working correctly: agents in a group only see tickets from their area when they log in, new tickets are assigned to the correct group without manual intervention, and the administrator can verify from the back office which group is handling each active ticket. A practical checklist includes: creating a test ticket for each configured category, logging in with a user from each group to confirm restricted visibility, and reviewing the assignment history to validate that automatic routing is working according to the defined rules.
Short description
Segment agents and customers into groups with differentiated visibility and access within SupportCandy. Ideal for multi-departmental teams that need automated ticket routing and real access control without constant manual management.
Written and reviewed by the PrimeGPL Team
At PrimeGPL, we ensure that every piece of published content is verified and reviewed by our team. We analyze features, compatibility, and performance to provide you with clear, up-to-date, and truly useful information for each product listed in our store.
Get your questions answered here
We answer your questions so you can buy in an informed and confident manner.
Does my purchase include updates?
Yes. Every product purchase includes lifetime updates, so you won't have to pay extra under any circumstances.
Is there a daily download limit?
No, not at all. After your purchase, you can download it as many times as you need, without any problem.
On how many websites can I use the products?
You can use your purchases on as many domains (websites) as you want, without any problems.
Does it include technical support?
Yes. We offer technical support Monday through Friday, during business hours UTC -3. This support includes assistance with issues related to download problems, installation problems, or errors with the purchased product.
Furthermore, support does not include configurations, customizations, tutorials, or services associated with the author.
Does my purchase have a warranty?
Yes, of course. If you have any problem that we can't solve, or if there's an external issue that doesn't have a general solution related to our service, you'll receive support and, if necessary, a full refund.
How do I access support?
After your purchase, from your user account, you can access the support section, where you can open a ticket and our team will assist you with whatever you need.
Download Previous Versions
If you have purchased this product, or have an active membership, you can download previous versions without any limits or restrictions.
| Product Name | Version | Size | Date | Download |
|---|---|---|---|---|
| No hay versiones anteriores registradas. | ||||
Related Products
Below we show you different products that share the same category.
