Why round-robin is so popular
When inbound meetings arrive faster than one person can take them, someone has to decide who gets each one. Round-robin — give the next meeting to the next person in the rotation — is the obvious answer.
It has real strengths. It is simple to explain. It feels fair, which matters a great deal on a team where meetings translate directly into commission. It spreads the workload so nobody is overwhelmed while others sit idle. And it is easy to automate.
For a team of similar people handling similar meetings, it works well. The trouble starts when either the people or the meetings are not actually similar.
Where strict rotation goes wrong
Pure round-robin makes one assumption: that every meeting is interchangeable and every rep is equally suited to it. In practice, neither is usually true. (Routing also decides how fast a request is answered. See speed to lead.)
Meetings differ in value and difficulty. A qualified request from a large enterprise and a curious enquiry from a two-person startup are both "one meeting" to a strict rotation. Whoever happens to be next gets whichever arrives.
People differ in expertise. One rep knows healthcare deeply; another has never sold into it. One speaks German; another does not. A strict rotation sends the German-speaking healthcare prospect to whoever is next.
Availability differs. If the next person in the rotation is busy at every time the prospect can make, a naive system either skips them — quietly breaking the fairness it was supposed to guarantee — or offers the prospect worse times.
Performance differs. Rotating strictly means your newest rep and your strongest closer receive the same share of your best opportunities. That may be a deliberate choice for development reasons, but it should be a choice rather than a side effect.
None of this means abandoning rotation. It means rotation should be one rule among several, not the only rule. The same principle applies at events, where matching attendees to the right expert matters more than spreading requests evenly.
Weighted, capped, and matched
Most effective distribution schemes combine three ideas.
Match first. Before any rotation happens, filter the eligible people by what the meeting needs: territory, industry, product line, language, deal size, existing account ownership. If only two people are qualified, the rotation is between those two.
Then rotate, with weights. Among eligible people, distribute in turn — but allow weights. A rep ramping up might receive half a share. A senior rep focused on large accounts might receive a smaller share of small ones. Weights make the policy explicit instead of leaving it to managers reassigning meetings by hand.
Then cap. Limit how many meetings any one person can take per day or per week. Beyond a certain point, extra meetings make every meeting worse, and caps protect preparation and follow-up time.
A useful mental model: matching decides who can take the meeting, weights decide how often each of them should, and caps decide when to stop.
If a tool applies these rules with AI, check that you can still see why a meeting went where it did. Our guide to AI meeting scheduling lists the questions to ask.
What fair actually means
Teams argue about distribution because "fair" has several reasonable definitions:
- Equal count: everyone gets the same number of meetings.
- Equal opportunity value: everyone gets a similar mix of large and small opportunities.
- Equal availability: everyone gets meetings in proportion to the time they have made available.
- Merit-weighted: people who convert more get more.
Each is defensible, and they produce different outcomes. The mistake is not picking the wrong one; it is never explicitly picking at all, so every rep assumes the definition that suits them.
Write the rule down. Share it with the team. Review it quarterly. Distribution disputes almost always become manageable once everyone can see the rule and the data.
Handling the edge cases
A distribution scheme is tested by its edge cases rather than its normal operation.
- Existing relationships. If an existing customer or an active opportunity books a meeting, it should go to the account owner, not the rotation. Rotation is for new, unowned demand.
- Time off. People on leave should drop out of the rotation automatically, and should not "owe" meetings when they return unless that is a deliberate policy.
- Reassignments. When a meeting is moved from one person to another, decide whether the rotation counts it for the original recipient or the new one. Either can be right; inconsistency is what causes friction.
- No-shows and cancellations. Does a meeting that did not happen count towards someone's share? Most teams decide it should not, otherwise no-shows quietly penalise whoever received them.
- Nobody qualified is available. Define the fallback in advance: a wider pool, a manager, or offering the prospect later times. Do not leave it to whoever notices first.
Measuring whether it works
Check the distribution against outcomes, not only counts. Over a quarter, look at:
- Meetings received per person, against their available hours.
- The mix of opportunity sizes each person received.
- Show rate and conversion rate per person and per meeting type.
- How often meetings were manually reassigned — a high number suggests the rules do not reflect reality.
- Time from booking request to confirmed meeting.
If manual reassignment is common, your matching rules are missing something. If conversion varies widely between people with similar meeting mixes, that is a coaching question rather than a routing one. Either way, what happens in the meeting itself matters as much as who gets it.
CallShark is being built with expertise-based routing: requests are matched on specialism, seniority, and language first, then distributed within limits and caps you define. The product is temporarily down.