The three main ticket routing methods are round-robin (tickets rotate evenly through a list of agents), skills-based (tickets go to the agent whose skills match the ticket), and load-balanced (tickets go to the agent with the most availability). Use round-robin for small teams handling similar tickets, skills-based when tickets need specialist knowledge, and load-balanced when ticket effort varies a lot. Most mature help desk setups end up combining two of them.
What is ticket routing (and why the method matters)?
Ticket routing is the set of rules that decides which agent or team gets a new ticket, without someone sorting the inbox by hand. Pick the right method and tickets land with someone who is free and able to help. Pick the wrong one and you might run into issues like:
- One agent drowning while another has an empty queue
- Tickets bouncing between people because they reached the wrong specialist
- Customers waiting on an agent who is out for the day
The good news: you only have three core methods to understand. Everything else (team queues, VIP routing, keyword rules) is just a variation or a filter on top.
Round-robin vs. skills-based vs. load-balanced: comparison table
Here’s how the three ticket routing methods work, compared side by side.
| Round-robin | Skills-based | Load-balanced | |
|---|---|---|---|
| How it picks the agent | Next person in a fixed rotation | Agent whose skills (language, product, tier) match the ticket | Agent with the most availability right now |
| Optimizes for | Fairness in ticket count | Accuracy (right expert, first time) | Fairness in workload and speed |
| Best team size | 2–15 agents | 10+ agents or any team with specialists | 5+ agents with uneven ticket effort |
| Ticket mix | Similar, low-complexity tickets | Varied topics, languages or tiers | Mixed: some 2-minute fixes, some 2-hour ones |
| Setup effort | Low (pick a group) | High (tag skills on agents and tickets) | Medium |
| Main risk | Slow agents pile up a backlog | Specialist bottlenecks; unmatched tickets wait | Fast agents get punished with more work |
| Common default | Rotate by oldest last assignment | Fall back to any agent if no match | Count only open tickets; skip agents at capacity |
A quick rule of thumb: round-robin shares tickets, load-balancing shares work, skills-based shares expertise.
How each routing method works
Round-robin routing
Round-robin hands out tickets in turn: agent A, then B, then C, then back to A. Most tools rotate by “oldest last assignment,” so whoever waited longest for a ticket gets the next one.
- Great for: small teams, a general support inbox, and new help desks that want something live today.
- Watch out for: round-robin counts tickets, not effort. Ten password resets and ten server outages look the same to it.
- Pro tip: pair it with an availability check so agents who are offline or on vacation are skipped.
Skills-based routing
Skills-based routing tags each agent with skills (for example French, Billing, Tier 2, Product X) and sends each ticket to an agent whose skills match. It’s an accurate method, but only as good as your skill tags.
- Great for: multilingual support, multiple products, and tiered support.
- Watch out for: if only one agent has a skill, that person becomes a bottleneck. Always define a fallback for tickets nobody matches.
- Pro tip: keep it to 5–10 skills to start. Twenty overlapping skills is a maintenance headache.
Load-balanced routing
Load-balanced (or capacity-based) routing sends each new ticket to the agent with the most spare room. Tools usually measure this as either open tickets per agent against a cap you set or based on time-based availability.
- Great for: teams where ticket effort varies widely, or where speed matters more than specialization.
- Watch out for: your fastest closers get the most tickets. Keep an eye on burnout and set a sensible cap (many email teams start around 10–25 open tickets per agent).
When to use each method: the 3V Routing Test
Not sure which to pick? Run your help desk through the 3V Routing Test: Volume, Variety and Variance. Answer these in order and stop at the first “yes.”
- Variety: do tickets need different expertise? If tickets need a specific language, product or support tier to solve, start with skills-based routing.
- Variance: does ticket effort swing a lot? If some tickets take 2 minutes and others take 2 hours, use load-balanced routing so busy agents aren’t buried.
- Volume: is it a steady stream of similar tickets? If tickets are alike and the team is small, round-robin is simple, fair and fast to set up.
- Still unsure? Start with round-robin, measure for 30 days, then revisit. Your reports will tell you whether you have a variety or variance problem.
Quick scenarios
| Your situation | Recommended routing |
|---|---|
| 4-person IT help desk, mostly password resets and access requests | Round-robin |
| SaaS support in English, French and Spanish | Skills-based (by language) |
| MSP with Tier 1 and Tier 2 technicians | Skills-based, then round-robin within each tier |
| E-commerce team with a mix of “Where’s my order?” and complex refunds | Load-balanced |
| Enterprise accounts with a named account manager | Customer-based (direct assignment) |
| 30+ agents, multiple products, uneven ticket effort | Hybrid: skills-based to the right group, load-balanced inside it |
The hybrid pattern: “Filter, then share”
Most growing teams land on a two-layer setup we call Filter, then share:
- Filter each ticket to the right group using rules (skill, product, language, customer, priority).
- Share tickets inside that group with round-robin or load balancing.
You get accuracy from the first layer and fairness from the second.
How popular help desks handle ticket routing
Every major help desk supports some mix of these methods, but the names and plan requirements differ. Here’s a snapshot based on each vendor’s own documentation.
| Help desk | Round-robin | Skills-based | Load-balanced | Plan needed for advanced routing |
|---|---|---|---|---|
| OneDesk | Yes (“Assign by round-robin” action) | Via rule filters (ticket type, priority, keyword, tag, inbox, customer) to team / agent | Yes (load-based auto-assign to the user with the lowest workload) | Automations included in all plans |
| Zendesk | Yes (omnichannel routing mode) | Yes | Yes (“Standard” mode: most spare capacity) | Suite Team or higher |
| Freshdesk | Yes (Omniroute) | Yes | Yes (load-based) | Pro or Enterprise |
| HubSpot Service Hub | Yes | Yes | Yes (“Load Balanced”) | Professional or Enterprise |
Where OneDesk fits
OneDesk combines help desk and project management in one app, so routing doesn’t stop at the support queue. A few things that make its approach practical:
- Round-robin per group: create several round-robin automations, each with its own group of agents, so billing tickets rotate through billing staff and bugs rotate through developers.
- Load-based auto-assign: send each new ticket to the user with the lowest current workload, so busy agents aren’t buried while others sit idle.
- Rule-based “Filter, then share”: filter by priority, ticket type or keywords, then round-robin or load-balance within the right team or project.
- Customer-based routing: set an “add assignee” routing action on a customer organization, so every ticket from that client reaches their named agent. Email domain matching is on by default, so even new contacts from that company route correctly.
- Team queues: assign to a team, and agents pull tickets into their own queue when they’re ready.
- Escalation rules: reassign tickets that sit untouched, or send 5-star priority tickets straight to a manager.
- Tickets to projects: route a ticket to a project, then round-robin among that project’s members — handy for IT and software teams where support work becomes project work.
- Workload views: see each team’s and user’s load at a glance to spot imbalances and tune your rules.
How to set up round-robin routing in OneDesk (5 steps)
You can have round-robin running in about 5 minutes.
- Open Automations. Go to Administration > Automations and create a new automation.
- Add your filters. Pick which tickets this rule applies to, such as a ticket type, priority, inbox or keyword. Leave filters empty to cover all new tickets.
- Choose the action. Set the action to Assign by round-robin.
- Pick the group. Select the team or individual agents to rotate through.
- Save and repeat. Create one automation per group (Billing, IT, Tier 2) to build your own “Filter, then share” setup.
Prefer load balancing? Follow the same steps, but in step 3 choose ‘Assign by availability’. OneDesk then gives each new ticket to the agent in the group with the lowest workload in the selected date period (today, next 7 days, next 30 days, etc).
Bonus: create a saved view of unassigned tickets as a safety net, so nothing slips through while you fine-tune your rules.
FAQ
There’s no single best method. Round-robin suits small teams with similar tickets, skills-based suits teams with specialists, and load-balanced suits teams with uneven ticket effort. Many teams combine skills-based filtering with round-robin or load balancing inside each group.
Round-robin gives each agent the same number of tickets in turn. Load-balanced routing gives the next ticket to whoever has the fewest open tickets, so it accounts for agents who are still busy with older work.
Yes. OneDesk workflow automations can assign tickets by round-robin, by load (to the user with the lowest workload), to a specific agent or team, or by customer organization. Rules can filter on ticket type, priority, keywords and more.