How to use Zendesk groups and organizations: A complete guide

If you're managing a growing support team, you've probably hit this wall: tickets are coming in faster than you can route them, agents are stepping on each other's toes, and customers are getting bounced between departments. Zendesk groups and organizations exist to solve exactly these problems.

Think of organizations as buckets for your customers and groups as buckets for your agents. When you connect the two, you create an automated pipeline that sends the right tickets to the right people without anyone manually triaging every request.

In this guide, you'll learn how to set up both features, connect them for automated routing, and avoid the common mistakes that trip up most teams. Whether you're just getting started with Zendesk or looking to optimize an existing setup, these steps will help you build a support workflow that scales.

What are Zendesk organizations?

Organizations are collections of your end users (customers). They're optional, but once you start using them, you'll wonder how you managed without them.

Here's how they work: you create an organization (say, "Acme Corp"), add their employees to it, and suddenly you can track every ticket from that company in one place. You can also set up automation so that any new ticket from an Acme Corp employee automatically gets tagged, prioritized, or assigned to a specific team.

Plan limitations to know:

• Team plan: Users can belong to only 1 organization
• Professional and Enterprise: Users can belong to up to 300 organizations

Common use cases for organizations

• B2B support: Create an organization for each client company to track their ticket volume, identify trends, and report on their support experience
• Service level agreements (SLAs): Group customers by their support tier (Basic, Professional, Enterprise) and route tickets accordingly
• Location and language: Organize customers by region so tickets go to agents who speak their language and work in their timezone
• Email domain automation: Set up automatic organization assignment based on email domain (anyone with @acmecorp.com gets added to the Acme Corp organization)

What are Zendesk groups?

While organizations hold your customers, groups hold your agents. Every agent in Zendesk must belong to at least one group, and they can be members of multiple groups.

Groups are how you organize your team internally. You might have a "Level 1 Support" group for frontline agents, a "Level 2 Support" group for technical specialists, and a "Billing" group for financial questions. When a ticket comes in, Zendesk uses these groups to determine who should handle it.

Key characteristics:

• Groups can only contain team members (agents), never end users
• All agents must belong to at least one group
• You can designate a default group for new agents
• Enterprise plans support private groups for sensitive tickets

Common use cases for groups

• Tiered support: Route simple questions to Level 1 and escalate complex issues to Level 2 or 3
• Product specialization: Create groups for different product lines (Software, Hardware, Services)
• Department-based routing: Send billing questions to Finance, technical issues to Engineering Support
• Private groups (Enterprise): Restrict access to tickets containing sensitive information like security issues or HR matters

How organizations and groups work together

Here's where it gets interesting. When you connect organizations to groups, you create an automatic routing system.

Let's say you have a client called "TechStart Inc." You create an organization for them and map it to your "Premium Support" group. Now, every time someone from TechStart submits a ticket, it automatically lands in the Premium Support group's queue. No manual sorting. No risk of it getting lost in the general inbox.

This connection happens through two key features:

1. Group mapping: Assign an organization to a specific group so their tickets go directly to that team
2. Business rules: Use triggers and automations to route, tag, or prioritize tickets based on organization or group

The result is a workflow where tickets flow from customer to the right agent with minimal manual intervention.

Step 1: Create your first organization

Let's walk through setting up an organization from scratch.

Prerequisites: You need admin access to Zendesk Support. On Enterprise plans, agents in custom roles with the right permissions can also manage organizations.

1. Navigate to the Organizations page. In Zendesk Support, click Organizations in the sidebar.

2. Click Add organization. You'll see a form where you can enter the organization details.

3. Enter a unique name. This is how you'll identify the organization in reports and ticket views. Avoid using pipe characters (|) in the name.

4. Set up user mapping (optional but recommended). In the Domains field, enter the email domains associated with this organization (for example, "acmecorp.com"). When someone with that domain submits their first ticket, Zendesk automatically adds them to this organization.

5. Configure group mapping. Select a Group from the dropdown. Now, any ticket from users in this organization will automatically be assigned to that group.

6. Set ticket access permissions. Under Users, choose whether members can see only their own tickets or all tickets in the organization (shared organization). The shared option is useful for B2B scenarios where multiple people at a company want to track each other's support requests.

7. Add tags and details. Tags can trigger automations. Details and notes are for internal reference.

8. Click Save. Your organization is now live.

Step 2: Set up groups for your team

Now let's create the groups that will handle tickets from your organizations.

1. Open the Groups page. In Admin Center, click People in the sidebar, then select Team > Groups.

2. Click Add group. You'll need to provide a unique name for the group, an optional description, and the team members to add.

3. Add team members. Search for agents and add them to the group. Remember, every agent must belong to at least one group, so new agents should be added to a default group.

4. Set the default group (optional). If this should be the default group for new agents, click Set as default. This is different from your account's default group, which you set separately.

5. Make it private (Enterprise only). If this group will handle sensitive tickets, click Make it private. This restricts ticket visibility to only admins and agents in the group. Note: this cannot be undone.

6. Click Save. Your group is ready to receive tickets.

Step 3: Connect organizations to groups

With organizations and groups created, now you connect them for automatic routing.

1. Open the organization you want to configure. Go to Organizations in the sidebar and click on the organization name.

2. Select a group. In the organization details, find the Group dropdown and select the group that should handle this organization's tickets.

3. Save your changes. The mapping is now active. New tickets from users in this organization will automatically be assigned to the selected group.

4. Set up business rules for advanced routing. For more complex workflows, create triggers in Admin Center > Objects and rules > Triggers. For example, if Organization is "TechStart Inc" AND Priority is "Urgent", assign to "Premium Support" group AND notify manager. Or if Organization tag contains "enterprise", set priority to "High".

5. Test the workflow. Submit a test ticket from a user in the organization and verify it routes correctly to the assigned group.

Best practices for Zendesk groups and organizations

After setting up dozens of Zendesk instances, here are the patterns that work:

Naming conventions: Use consistent, descriptive names. "Support - Level 1" is better than "Group A." For organizations, use the actual company name your team recognizes.

When to use organizations vs tags: Organizations are for grouping users. Tags are for categorizing tickets. A user belongs to one organization (or a few), but their tickets can have many tags. Use organizations for routing and reporting by customer. Use tags for topic-based categorization.

Structure groups for growth: Start with broader groups ("Support," "Sales") and split them as you grow ("Support - Technical," "Support - Billing"). It's easier to split a group than merge them later.

Document your setup: Write down which organizations map to which groups and why. When your team grows, new admins will need this context.

Review permissions regularly: Especially for shared organizations where users can see each other's tickets. Make sure this is still appropriate as your customer relationships evolve.

Common mistakes to avoid

Overcomplicating group structures: Don't create a group for every possible scenario. Start simple. You can always add more groups later.

Misunderstanding shared organization permissions: When you enable "Can view all org tickets," every user in that organization can see every ticket. This is powerful for B2B support but can be a privacy issue if misapplied.

Forgetting to update mappings: When agents leave or teams reorganize, update your group memberships. Old mappings can send tickets to agents who no longer handle them.

Not testing business rules: A trigger that seems logical on paper might have unintended consequences. Always test with sample tickets before rolling out automation to production.

Taking your Zendesk workflow further with AI

Once you've organized your customers and agents with groups and organizations, you can add another layer of efficiency with AI. This is where eesel AI comes in.

While Zendesk's native features handle the routing and assignment, an AI teammate like eesel can handle the actual responses. Here's how they work together:

• Organizations ensure tickets reach the right team
• Groups organize your agents by expertise
• AI drafts responses based on your past tickets and help center articles

The result is a workflow where tickets not only reach the right people automatically but also get faster responses because AI handles the initial draft. Agents review, edit if needed, and send. It's like having a junior agent who learns your business instantly and never sleeps.

If you're already using Zendesk groups and organizations, adding AI is a natural next step. See how eesel AI integrates with Zendesk to learn more about automating your responses while keeping your existing routing structure. You can also explore eesel AI's AI Agent product for end-to-end ticket resolution, or check out customer support automation solutions to see what's possible.