Zendesk skill by channel: Complete routing setup guide

Getting tickets to the right agent quickly is one of the most impactful things you can do for customer satisfaction. When a billing question sits in a general queue for hours because no one realized it needed a specialist, everyone loses. The customer waits longer than necessary. Your agents waste time routing tickets manually. And your metrics take a hit.

Skills-based routing solves this by matching tickets to agents based on qualifications rather than just who's available. Instead of round-robin assignment that treats every agent as interchangeable, you can route French-speaking customers to bilingual agents, technical issues to your product specialists, and VIP requests to your most experienced team members.

This guide walks through setting up Zendesk skills by channel. We'll cover how to configure routing for email, phone, chat, and messaging, then explore how eesel AI can simplify the process by learning your team's expertise automatically.

What is Zendesk skills-based routing?

Skills-based routing is a ticket assignment strategy that directs customer requests to agents with the most relevant qualifications. Rather than sending every ticket to the next available agent, the system considers what skills are needed to resolve the issue and matches accordingly.

Here's how it works in practice. A customer submits a ticket about a complex integration issue. Your trigger detects keywords like "API" and "webhook," adds a "Technical" skill tag to the ticket, and routes it to agents who have that skill assigned. If no technical agents are currently available, the ticket can either wait for one (if marked as Required) or route to any available agent after a timeout period (if marked as Optional).

The benefits are straightforward. Customers reach qualified agents faster, which typically means faster resolution times and higher satisfaction scores. Agents spend more time solving problems in their areas of expertise and less time escalating or transferring tickets. And your team can handle more volume without adding headcount because the routing itself happens automatically.

Most teams organize skills around a few common categories:

• Language for multilingual support teams
• Product knowledge for companies with multiple product lines
• Technical expertise for complex troubleshooting
• Compliance certifications for regulated industries
• Experience level for tiered support structures

Zendesk offers two approaches to skills-based routing. Standalone skills-based routing uses specialized views where agents manually identify and assign tickets matching their skills. Omnichannel skills-based routing automatically assigns tickets based on skills, availability, and capacity. The latter is more sophisticated and better for high-volume teams.

What you'll need to get started

Before you start configuring skills-based routing, make sure you have the necessary access and plan level. Zendesk restricts this feature to specific tiers, and you'll need administrative privileges to set it up.

Plan requirements:

Access requirements:

• Admin access to the Zendesk Admin Center
• Permission to modify business rules (triggers, automations)
• Ability to edit agent profiles for skill assignment

Preparation:

• Document your team's skill structure before configuring (which agents speak which languages, who handles technical issues, etc.)
• Identify the ticket conditions that indicate each skill is needed (keywords, form selections, custom field values)
• Decide whether to use Required or Optional skills for each category

If you're on a lower-tier plan or want to avoid the complexity of manual skill configuration, eesel AI works with any Zendesk plan and doesn't require Enterprise-level access. Our AI learns routing patterns from your existing tickets without needing predefined skill labels.

Setting up skills for email and web form tickets

Email is the most common channel for skills-based routing, and it's also the most straightforward to configure. Here's how to set it up.

Step 1: Create skill types

Navigate to Admin Center > Objects and rules > Business rules > Skills. This is where you'll create and manage all skills for your account.

Start by creating skill types, which are categories for organizing related skills. You can create up to 10 skill types per account. Common types include:

• Language (French, Spanish, German, etc.)
• Product (Product A, Product B, specific modules)
• Expertise Level (Junior, Senior, Specialist)
• Department (Billing, Sales, Technical)

To create a skill type, click the New skill type button, enter a unique name (max 96 characters), and press Enter to save.

Step 2: Add individual skills

Within each skill type, you can add up to 30 individual skills. For example, under a "Language" type you might add French, Spanish, and German. Under a "Product" type you might add your different product lines or modules.

Keep your initial setup simple. Start with 3-5 core skill types that cover your most common routing scenarios. You can always add more later as you refine your process.

Step 3: Define skill conditions

For each skill, you'll define ticket conditions that determine when that skill should be added automatically. These conditions work similarly to Zendesk triggers, checking ticket properties like:

• Requester language
• Ticket subject or description keywords
• Custom field values
• Ticket form selection
• Channel (email, chat, web form)

You'll also choose whether each skill is Required or Optional. Required skills mean a ticket will only route to agents who have ALL the required skills assigned. Optional skills allow tickets to route to any agent, but the system prefers agents with matching skills.

Step 4: Configure email-specific triggers

Create triggers that automatically add skills to incoming email tickets based on your conditions. For example, you might create a trigger that adds the "French Language" skill when the requester's language is set to French.

Go to Admin Center > Objects and rules > Business rules > Triggers to create these. The trigger conditions should match your skill conditions, and the action should be "Add skills" or "Set skills."

Configuring skills for phone and call routing

Phone routing works differently than email because of how tickets are created. Understanding this difference is key to getting call routing right.

How phone routing differs

When you use omnichannel routing, a ticket is created for the call as soon as it enters the queue. That means you can run triggers on incoming calls before the call is answered. If you choose not to use omnichannel routing, tickets are created for calls after the call is answered by an agent, and triggers can't be run against the incoming calls until the ticket is created.

This means omnichannel routing is the only way you can use triggers to influence call routing.

Step 1: Enable omnichannel routing for calls

Before configuring skills for phone routing, ensure omnichannel routing is turned on. Go to Admin Center > Objects and rules > Omnichannel routing > Routing configuration and click Set up omnichannel routing.

Step 2: Create customer-specific tags

For account-based routing (where specific customers always route to specific agents), add a tag to all user profiles associated with a single customer account. You'll use that tag to identify all tickets from the customer and route them accordingly.

Open the user profile and add a tag like "Customer1" to the end user's profile. Use unique tags for each customer account.

Step 3: Set up call routing triggers

Create triggers that add skills to incoming calls. Under Conditions, specify:

• Ticket > Channel > Is > Phone call (incoming)
• Ticket > Tag > CustomerName (the tag you created)

Under Actions, select Add skills or Set skills and choose the appropriate skill.

Step 4: Configure skills timeout

For each skill you select, specify a priority: Required or Optional (Low, Medium, or High priority). Optional skills are subject to the skills timeout defined in your omnichannel routing configuration. When a skills timeout occurs, omnichannel routing ignores optional skills in order of priority (low to high) when looking for available agents.

Setting up skills for chat and messaging

Chat and messaging use the same omnichannel routing infrastructure as phone calls, but with some additional considerations for real-time conversations.

How omnichannel handles chat skills

Omnichannel routing considers three factors when assigning chat or messaging conversations:

1. Skills - Does the agent have the required skills?
2. Availability - Is the agent online and available?
3. Capacity - Does the agent have bandwidth for another conversation?

This means a ticket might have matching skills, but if the qualified agents are at capacity, it will route to an available agent with fewer matching skills.

Step 1: Configure agent statuses and capacity

Before setting up chat skills, ensure your agents have proper status management. Go to Admin Center > Objects and rules > Omnichannel routing > Agent statuses to configure Online, Away, and Offline states.

Set capacity rules to define how many tickets each agent can handle simultaneously. This is especially important for chat, where agents often handle multiple conversations at once.

Step 2: Set up chat-specific skill conditions

Create triggers that add skills to chat and messaging tickets. The conditions might include:

• Chat widget used (if you have different widgets for different products)
• Pre-chat form responses
• Customer tags or organization
• Keywords in the initial message

Step 3: Balance skills with real-time constraints

For real-time channels like chat, you may want to use more Optional skills than Required ones. If a chat request requires "French" and "Technical" skills but no agent has both, a Required setup would leave the customer waiting. Using Optional skills ensures the chat gets picked up quickly while still preferring the most qualified agent.

Assigning skills to agents

With your skills and conditions defined, the next step is assigning those skills to the agents who have them.

How to assign skills

1. Go to the skill type in Admin Center
2. Click on the specific skill
3. Select Manage to add agents
4. Choose the agents who have this skill

You can assign multiple skills to each agent, and agents can have skills from multiple skill types. This flexibility lets you build complex routing scenarios. An agent might have both "French" and "Technical" skills, making them the ideal match for technical tickets from French-speaking customers.

Managing skill coverage

When planning assignments, consider skill coverage across your team. If only one agent has a particular skill combination, that creates a bottleneck. Make sure you have enough agents with common skill sets to handle expected volume.

Maintaining skills over time

When agents join, leave, or change roles, you'll need to update their skill assignments. This ongoing maintenance is often underestimated. Consider quarterly reviews of your skill structure to keep it current.

Common pitfalls and troubleshooting

Even with careful planning, teams often hit snags when implementing skills-based routing. Here are the most common issues and how to address them.

Skills not applying to tickets

If skills aren't being added to tickets as expected, check your trigger order. Triggers run in the order they appear in your trigger list. If a trigger that adds skills comes after a trigger that assigns the ticket, the skills may not be considered during routing.

Calls not routing to skilled agents

If phone calls aren't routing to agents with matching skills, verify that omnichannel routing is enabled. Without it, triggers can't influence call routing because tickets are created after the call is answered.

Agents seeing tickets they shouldn't

If agents see tickets in their views that don't match their skills, review your view conditions. Make sure you're using "Skills + Is + Current user skills" rather than just filtering by other criteria.

Skills timeout not working

If optional skills aren't timing out as expected, check that you've set skill priorities correctly. The timeout only drops skills marked as Optional, and it drops them in order of priority from low to high.

Testing before going live

Before rolling out skills-based routing to your entire team, test with a small group. Submit test tickets that should trigger different skills and verify they route to the expected agents. Check each channel (email, phone, chat) separately since they behave differently.

A simpler approach: intelligent routing with eesel AI

Setting up skills-based routing in Zendesk works well for teams with the right plan and resources to maintain it. But it's not the only way to get tickets to the right agents. If the manual configuration feels overwhelming, there's a simpler approach.

eesel AI learns your routing patterns automatically by analyzing your existing ticket history. Instead of manually defining every skill and condition, our AI recognizes who handles what based on actual past assignments. When a new ticket comes in, it routes intelligently without any predefined skill labels.

Here's how it differs from Zendesk's native approach:

Our AI Triage product handles the routing automatically, while AI Agent can resolve common tickets entirely without human intervention. Both integrate directly with Zendesk and learn from your existing data.

The key advantage is that you don't need to predict every skill combination upfront. As your team evolves and new types of tickets emerge, the AI adapts without manual reconfiguration. This is especially valuable for growing teams where skill structures change frequently.

Getting your Zendesk skill routing live

Setting up Zendesk skills by channel takes planning and ongoing maintenance, but the payoff is worth it for many teams. Customers reach qualified agents faster. Agents work on tickets that match their expertise. And you reduce the manual work of triaging and reassigning.

Here's a quick recap of what you need to do:

1. Confirm you're on an Enterprise plan with admin access
2. Document your team's skill structure before configuring
3. Create 3-5 core skill types with relevant skills
4. Define conditions for when each skill applies
5. Assign skills to agents based on their qualifications
6. Configure standalone or omnichannel routing rules
7. Test thoroughly before going live

Start simple and expand as you learn what works. You can always add more skill types later as your needs evolve.

If the setup complexity is holding you back, or if you're on a lower-tier Zendesk plan, try eesel AI for intelligent routing that learns from your existing tickets. It works with any Zendesk plan and gets you up and running in minutes instead of days.

Either way, the goal is the same: getting every ticket to the agent best equipped to resolve it. That's better for your customers, your agents, and your metrics.