How leads reach agents affects speed-to-call, fairness and morale. VM CRM supports two strategies. Here is how to choose.
Round-robin
Leads are dealt out in turn: agent 1, agent 2, agent 3, then back to agent 1. VM CRM remembers where the last batch stopped, so the next batch continues with the next agent rather than starting over.
Use it when
- agents have similar experience and similar workloads,
- leads arrive in batches (a daily portal export, a campaign file),
- you want distribution that is obviously fair.
Least-loaded
Each lead goes to the agent who currently has the fewest open leads.
Use it when
- agents work different hours or some are part-time,
- someone is back from leave with an empty queue,
- you want to even out backlogs instead of adding to them.
Side by side
| Round-robin | Least-loaded | |
|---|---|---|
| Fairness people can see | High | Medium |
| Evens out backlogs | No | Yes |
| Best for | Uniform teams, batch imports | Mixed shifts, uneven queues |
Mistakes to avoid
- Distributing to people who aren’t working. Limit distribution to agents on shift today.
- Re-distributing leads that are already being worked. Only distribute unassigned or genuinely stale leads. Reassigning an active conversation resets the relationship.
- Ignoring lead quality. If one source converts far better than another, distribute each source separately so everyone gets a share of the good leads.
- One notification per lead. VM CRM sends one “you have 25 new leads” notification per agent, not 25 separate alerts.