How to Auto-Route Support Tickets to the Right Agent

Why manual routing breaks down

Manual routing — a manager reads each ticket and assigns it — has three failure modes:

Delay: The manager isn't always available. Tickets sit unassigned for hours.
Inconsistency: The same type of ticket gets routed to different agents based on who's available or who the manager remembers can handle it.
Bottleneck: As ticket volume grows, the routing manager becomes the constraint. You can't scale without removing this bottleneck.

The three routing strategies

1. Rule-based routing (keyword matching)

Tickets containing specific keywords go to specific teams or agents automatically:

Subject contains "refund" → Billing team
Subject contains "bug" or "error" or "broken" → Technical team
Subject contains "invoice" or "GST" → Finance team
Email sender domain = enterprise-client.com → Key account manager

This is the simplest form and handles 60–70% of tickets correctly for most businesses.

2. Round-robin routing

Tickets are assigned to agents in rotation: ticket 1 → Agent A, ticket 2 → Agent B, ticket 3 → Agent C, ticket 4 → Agent A again.

Round-robin works well for teams with generalist agents where all tickets are roughly similar. It distributes load evenly without needing keyword matching.

3. Load-based routing

Tickets are assigned to whichever agent currently has the fewest open tickets. This is smarter than round-robin — if Agent A closes tickets faster than Agent B, Agent A gets more tickets automatically.

Use load-based routing when ticket complexity varies significantly and some agents work through tickets faster than others.

💡 Combine strategies: The most effective setup is rule-based routing first (send billing tickets to the billing team) then load-based routing within each team. Rules handle specialisation; load balancing handles fairness within groups.

Set up ticket routing rules in Resolvo

Keyword rules, round-robin, load balancing. All configurable in minutes. Free to start.

Try Resolvo Free →

What to route on: building your rule set

Start by pulling your last 100 tickets and categorising them. You'll find 5–8 types that cover 80%+ of your volume. Write a routing rule for each.

Example rule set for a SaaS company: Rule 1: Subject contains "refund" OR "payment" OR "invoice" → Billing queue Rule 2: Subject contains "bug" OR "error" OR "crash" OR "broken" → Engineering queue Rule 3: Subject contains "feature" OR "request" OR "suggestion" → Product queue Rule 4: Priority = Critical → Manager + Senior Agent Rule 5: Sender email = [VIP client list] → Key Account Manager directly Rule 6: Everything else → General Support queue (round-robin)

Handling routing errors

No routing system is perfect. "Refund" might appear in a billing question or a technical question ("I need a refund because the feature is broken"). Build in a catch — agents should be able to re-route any ticket to the correct queue with one click, and that re-routing should feed back into your rule refinement.

Check your routing accuracy monthly: of tickets assigned automatically, what % were in the correct queue? Aim for 85%+. Below 70% means your rules need refining.

Priority routing: the most important rule

Priority-based routing deserves special attention. A Critical ticket that sits in a general queue unnoticed can cost you a major client. Set a rule: anything tagged Critical or received from a paying customer above a certain tier goes to a named senior agent immediately — not into a queue to be picked up when someone has time.

Stop assigning tickets manually — automate it in Resolvo

Routing rules, priority escalation, team queues. Free to start.

Start Free →