Agent Rank vs Grade vs Call Count: in-group routing methods

VICIdial gives you more than a dozen ways to decide which available agent gets the next inbound call. Three of those methods lean on per-agent levers you set yourself: rank, grade, and call count. They sound similar but behave very differently, and picking the wrong one quietly skews how work lands on your floor.

Where these live

All three are chosen through the Next Agent Call method on the Ingroup. At the bottom of the in-group screen you will find a table listing every agent with their rank, their grade, and a running count of how many calls they have taken from that group today. You edit rank and grade in that table; the call count is tracked automatically.

Rank: a strict pecking order

Rank is a number you assign per agent, and the routing method sends calls to the highest rank first. This is Skills-based routing at its most blunt: your best closer gets every call until they are busy, then the next-ranked agent gets the overflow.

Rank is great when skill differences are real and you want your strongest people on the most calls. The downside is that lower-ranked agents can sit idle during quiet periods, so use it where output matters more than even distribution.

Grade: weighted, not absolute

Grade also assigns each agent a value, but instead of a strict winner-takes-all order, the grade-random methods turn those values into probabilities. A higher grade means a bigger slice of the calls, not all of them. An agent graded twice as high as a peer gets roughly twice the volume over time.

Grade is the gentler version of rank. You still favor your strong agents, but everyone keeps getting calls, which is better for morale and for keeping newer agents in practice. It softens the all-or-nothing feel of rank while still respecting skill.

Call count: even it out

The fewest-calls methods ignore skill entirely and route to whoever has taken the fewest calls from this group so far. This is the fairness lever. Over a shift, everyone ends up with a similar tally, which helps with Agent utilization and avoids burning out your fastest people.

Use call count when the work is uniform and you want load spread evenly, or when you are paying per call and want balance. Avoid it when one agent really is much better and you would rather steer hard cases their way.

Picking one

• Rank: maximize output, accept idle time at the bottom.
• Grade: favor skill but keep everyone working.
• Call count: spread work evenly, ignore skill.

There is no universally right choice; it depends on whether you optimize for results or for fairness. Our inbound call handling guide walks through the full menu of methods, and the Next Agent Call overview lists every option side by side. If you want to trial a couple of these against live traffic, our plans provision a dialer in under a minute.