In growing organisations, the transition from a small, agile support unit to a structured and scalable function is a critical phase. This is where order is created in processes, and efficiency replaces randomness. Zendesk Groups is a fundamental tool for supporting this development. Groups act as a structural framework that helps ensure that the right task lands with the right team at the right time. A well-implemented group structure supports a consistent and high-quality customer experience.
What are Zendesk Groups?
Zendesk Groups are logical collections of agents who share a common area of responsibility, a set of skills or a specific work process. They can be compared to departments in an organised company, for example sales, engineering and accounting. In Zendesk, Groups are used as digital counterparts to organise the support and service effort.
Groups are typically used to:
- Route tickets automatically: Send enquiries directly to the teams best qualified to resolve them.
- Organise agents logically: Create a clear and intuitive structure that reflects the internal organisation.
- Define responsibility and access: Ensure that agents see and work with tickets that are relevant to their role.
- Measure and report on performance: Generate data for team performance, identify bottlenecks and optimise workflows.
Without Groups, Zendesk can develop into an unstructured inbox where everything is sent to everyone. With Groups, a more specialised and efficient setup is created.
The indispensable value: Why Groups are fundamental
Below, two scenarios are compared: before and after implementing Groups.
| Scenario | Without Groups | With Groups |
|---|---|---|
| Ticket routing | All new tickets land in one big, disorganised pile. All agents see everything. | Tickets are routed automatically to, for example, "Technical Support" or "Billing" based on topic, priority or customer type. |
| Specialisation | Agents are generalists who have to be able to do a bit of everything. In-depth expertise is hard to build. | Teams can specialise. "Technical Support" become experts in complex troubleshooting, while "Sales" master onboarding. |
| Workload balancing | Some agents take many easy cases, while others are left with the complex ones. The distribution is often unfair and inefficient. | Workload is distributed evenly within a team. Round-robin or manual task picking within a group supports balance. |
| Performance data | It is almost impossible to measure how quickly technical problems are solved vs. invoicing questions. Everything is gathered in one dataset. | Precise reports can be created for, for example, the "Billing Team's" average reply time or "Enterprise Support's" customer satisfaction. |
| Efficiency | Time is spent on manual forwarding to the right person. Customers experience unnecessary waiting times. | First Contact Resolution can be increased when the customer is more quickly put in contact with the correct team. |
Overall, Groups change Zendesk from a general inbox into a more intelligent and specialised structure.
Designing a group strategy: Models and considerations
There is no standard model that fits everyone. The most appropriate group structure depends on the company's size, products, customer base and internal processes. The most common models are described below.
Organising by function (function-based)
This model creates teams based on their primary function and suits organisations with clearly separated areas of work.
- Customer Support Team: Handles general enquiries, user guidance and first-line support.
- Technical Support Team: Handles complex technical problems, bug reports and integrations.
- Billing & Accounts Team: Handles questions about invoicing, payments, licences and subscription changes.
- Sales & Onboarding Team: Helps potential customers and guides new customers through the onboarding process.
Organising by product (product-based)
If the company offers several distinct products or services, this model can be effective.
- Product A Support: A dedicated team focused on Product A's functionality and typical challenges.
- Product B Support: A specialised team for Product B.
- Enterprise Platform Support: A team for the largest and most complex customers using the enterprise solution.
Organising by geography or language (geography-based)
For global organisations, this model can ensure the correct language, cultural understanding and coverage across time zones.
- Nordic Team: Covers Danish, Norwegian, Swedish and Finnish support.
- DACH Team: Handles German, Austrian and Swiss support in German.
- APAC Team: Covers the Asia-Pacific region in local time zones.
Organising by customer type (customer tier-based)
This model prioritises customers based on value or agreed service level.
- VIP / Premium Support: Dedicated agents for the most important customers with a guaranteed fast reply time.
- Standard Support: Covers the majority of customers.
- SMB Support: A team specialised in the needs of small and medium-sized businesses.
Hybrid models: Combine for maximum efficiency
In practice, models are often combined. Examples might be "Technical Support - Product A" and "Technical Support - Product B", or "VIP Support - English" and "VIP Support - Danish". The goal is a structure that reflects the concrete organisation and way of working.
Step-by-step: Creating and configuring Groups
Creating a group is a simple process, but it should be carried out consistently from the start.
- Navigate to the Admin Center: Go to the Admin Center (the cog icon) in the sidebar. Select People in the left-hand menu, and then select Groups.
- Create a new group: Select Add group in the top right.
- Name the group: Choose a clear, descriptive and consistent name. Avoid generic names such as "Team 1" and instead use, for example, "Technical Support - Enterprise". This makes it easier to choose the correct group in triggers and views.
- Add agents: Under "Add agents", the relevant agents can be searched for and added. An agent can be a member of multiple groups.
- Assign a group manager (optional, but recommended): A group manager has special rights to edit the group and view members' statistics. This can be relevant for team leads or department heads.
- Save the group: Select Add group to save the configuration.
Methods for group assignment
Once the groups have been created, the next step is to ensure that tickets are assigned correctly. The primary methods are described below.
1. Manual assignment
The simplest method, where an agent manually assigns a ticket to a group.
- When is it used? For escalations, when a first-level agent receives an enquiry that requires specialised knowledge.
- Advantages: High control and flexibility.
- Disadvantages: Time-consuming, can create delays and depends on the agent's judgement.
2. Automatic assignment via triggers
Triggers are "if-then" rules that automatically perform actions based on ticket data. This is the most widely used method.
Example: Automatic routing of technical tickets.
Condition: All
Ticket | Is | Created
AND
Ticket | Subject | Contains | "error", "bug", "downtime"
Action:
Ticket | Set | Group | Technical Support
3. Form-based assignment
This method uses ticket forms in Zendesk. When a customer fills out a specific form on the help page, a trigger can ensure correct group assignment.
Example: Routing based on an "Invoice question" form.
Condition: All
Ticket | Is | Created
AND
Ticket | Form | Is | Invoice question
Action:
Ticket | Set | Group | Billing & Accounts
4. Round-robin assignment
Round-robin distributes tickets evenly between available agents in a group and supports a more consistent distribution of work.
- First available agent: Assigns the ticket to the first agent in the group who switches their status to "Online".
- Round-robin: Rotates between agents in the group to ensure a roughly equal distribution.
Important to know: Round-robin works best with Zendesk Suite, where agents' online status and current workload are included in the distribution.
Best practices: Effective group management
Creating groups is simple, but a sustainably effective structure requires ongoing maintenance and consistency.
1. Use clear and consistent names
A good name is self-explanatory and reduces the risk of routing errors.
- Good examples: "Danish Support - L1", "Technical Escalations", "Customer Success - EMEA".
- Poor examples: "Team Alpha", "Support", "Group 2".
2. Keep an eye on the group's size
The group's size affects both performance and well-being.
- Too small (1-2 agents): Risk of delays during absence.
- Optimal (3-15 agents): Better coverage, the opportunity to spar, and a fairer distribution.
- Too large (15+ agents): Risk of anonymity and fluctuating quality. Consider splitting into smaller, more specialised groups.
3. Document areas of responsibility
An internal document should clarify:
- What each group is responsible for.
- When a ticket should be escalated to another group.
- Who is the group manager or primary point of contact.
This creates clarity for both new and experienced agents.
4. Make use of group managers
A group manager can be responsible for:
- Monitoring the team's performance via dashboards.
- Handling escalations and complex cases.
- Mentoring support and a focus on the team's well-being.
5. Review and adjust regularly
Companies change, and the group structure should keep up. A quarterly review can include:
- Whether the current structure is still the most effective.
- Whether new products or markets require new groups.
- Whether groups should be consolidated or split.
6. Synchronise Groups with views and SLAs
The group structure works best when it is integrated with the other Zendesk elements.
- Views: Create views per group, e.g. "Open tickets in my group" or "Unresolved tickets in Technical Support".
- SLAs: Define different service targets per group. "VIP Support" can have a reply time of 1 hour, while "Standard Support" has 24 hours.
Advanced concepts: Group vs. individual assignment
The difference between assignment to a group and to an individual agent is central.
| Property | Assignment to a group | Assignment to an individual |
|---|---|---|
| Visibility | All agents in the group can see the ticket. | Only the assigned agent can see the ticket. |
| Ownership | Ownership is shared; anyone in the group can take the ticket. | Ownership is clear and personal. |
| Work distribution | Supports collaboration and flexibility; well suited to round-robin. | Ensures that a specific person owns the task from start to finish. |
| Best for | General incoming support, where the first available agent can help. | Escalations, tasks with specific context, or when a specialist is needed. |
Troubleshooting: Common challenges and solutions
Even a good setup can create challenges. Below are typical problems and their solutions.
Problem: Tickets are routed to the wrong group.
- Possible causes: The trigger conditions are too broad, the group name is misspelled in an action, or several triggers are in conflict.
- Solution: Go to Admin Center → Objects and rules → Triggers. Find the relevant trigger and review the conditions and actions. Use the trigger order to prioritise if several triggers can apply to the same ticket.
Problem: An agent cannot see tickets in their group.
- Possible causes: The agent is not added to the group, or the agent's role lacks the necessary permissions.
- Solution: Check membership under Admin Center → People → Groups. Then verify the agent's role under Users to ensure access to tickets from the relevant group.
Problem: Tickets in a group are not being picked up.
- Possible causes: Agents are constantly set to "Away", there are too many tickets relative to the number of agents, or views are not being used correctly to find tasks.
- Solution: Clarify whether the team is overloaded and whether views are configured correctly. Consider adjusting the round-robin settings or adding more agents to the group.
Conclusion: A roadmap to an optimised Zendesk structure
A well-thought-out group structure is not a one-off setup, but an ongoing foundation for customer service. By organising agents into logical, specialised teams and automating routing with relevant triggers, a more efficient and scalable operation is supported, as well as a more consistent customer experience.
Working towards an optimised structure starts with identifying the relevant teams, creating them with clear names and establishing rules that govern the workflow. By continuously measuring, adjusting and improving the structure, Zendesk can continue to function as a precise tool that supports the business goals.