CRM With Round-Robin Lead Distribution

A rotation is easy to build and easy to break. What matters is what happens on the third Saturday, when two people are off and one is hiding.

Before configuring anything, be clear about the problem, because stores implement round robin for two very different reasons and the right setup differs.

The first reason is fairness. Without a rule, lead flow goes to whoever is fastest on the refresh button, and that is usually the same two people. Everyone else stops trying, the newer salespeople never build a pipeline, and turnover goes up in the part of the roster you were trying to develop. A rotation is a management tool aimed at your team, not at your customers.

The second reason is speed. If nobody owns a lead, everybody assumes somebody else has it, and the lead sits. A rotation puts a name on it within a second of arrival, which means there is a person to hold accountable for the first response.

Those two goals conflict more often than vendors admit. Perfect fairness sends the lead to the person whose turn it is even when that person is at lunch and someone else is sitting at a desk doing nothing. Perfect speed sends every lead to your fastest closer and starves the rest of the floor. Every good distribution setup is a deliberate compromise between the two, and deciding where you want to sit on that line is a management decision you should make before you touch the configuration.

A pure rotation, applied without conditions, fails in the same places at almost every store. Know them going in.

Days off. The rotation hands a lead to someone who is off until Wednesday. The customer waits two days for a first call and buys elsewhere on Tuesday. This is the single most common failure and it is entirely avoidable.

Hoarding. A salesperson accepts every lead, works the two they like, and lets the rest go cold, because holding a lead costs them nothing and the rotation keeps feeding them anyway.

Skill mismatch. A commercial fleet inquiry, a trade-in appraisal request and a credit-challenged buyer all land on the same rotation as a routine internet inquiry, and the person whose turn it happens to be is the wrong person for two of them.

After hours. A meaningful share of internet leads arrive when the store is closed. A rotation that only assigns to the schedule leaves those leads unowned overnight, which is exactly when a fast response is most differentiating.

The argument. Six weeks later a manager says the store never received a lead, the vendor says it was delivered, and nobody can prove anything. This one is not a distribution failure at all. It is a record keeping failure, and it corrodes trust in the whole system.

LeadLocate runs global lead distribution with rules, layered over settings that individual stores can adjust, plus distribution lists for the cases a rule does not cleanly describe.

In practice that means you set the group or store default once, define the rotation membership as a list, then add conditions where you have a reason to. Rules can act on the attributes that come with the lead, so a source, a vehicle type or a time window can send the lead somewhere other than the default rotation. Multiple lists let you keep an internet rotation separate from a service-to-sales rotation separate from a seller lead rotation, rather than forcing every kind of opportunity through one queue.

Global lead settings hold the defaults, and global lead history holds the record of every assignment. Lead feeds and custom source feeds bring the flow in, including from your own site forms and third party providers, so the routing logic applies to everything rather than only to the leads we deliver.

For a group, the layering is the important part. A metro store with a ten person business development team and a rural point with three salespeople should not run the same rules, and they do not have to. See CRM for multi-location groups for how the group and store layers interact.

The fix for the days off problem is to treat availability as a condition rather than an afterthought. The mechanisms are simple and stores underuse them.

Keep the rotation lists current. This sounds obvious and it is the single most neglected piece of maintenance in any CRM. A list that still contains a salesperson who left in March is quietly sending a share of your lead flow into a mailbox nobody reads. Make list maintenance somebody's named job with a weekly check, the same way you would with a schedule.

Use separate lists for separate shifts rather than trying to encode a complicated schedule into one rotation. A morning list and an evening list, edited when the schedule changes, is easier to run and easier to audit than a clever rule nobody remembers writing.

Then handle the closed hours deliberately. Automations can send an immediate text and email the moment a lead arrives regardless of who is working, so the customer gets a real response at 10:40pm while the human assignment waits for the morning list. That single configuration usually does more for after-hours conversion than any change to the rotation itself.

Fairness is a good default and a poor absolute. There are cases where sending a lead to the next person in line costs you the deal, and your rules should name them explicitly rather than leaving them to whoever notices.

Repeat customers should go to the person who sold them the car, when that person is still with you. A returning buyer treated as a stranger by a rotation is an unforced error, and the customer notices immediately.

Seller leads generally belong with whoever actually appraises and buys, not with the general floor rotation. An opt-in seller lead from a local owner is an acquisition opportunity with a short clock on it, and routing it to a salesperson who has never appraised a car wastes the window.

Language, commercial and fleet inquiries, and specific franchises inside a group are all reasonable override conditions. So is source: a lead from a campaign a particular person is running should usually go to that person.

What should not be an override is a manager quietly reassigning good leads to a favorite. Every override should exist as a rule that anyone can read, because the moment overrides live in someone's head, the team stops believing the rotation is fair and you lose the benefit you built it for.

Global lead history is the least exciting feature on this page and the one experienced managers ask about first, because they have all lost the argument at least once.

Every lead carries a record of where it went and when. That settles four recurring disputes at a stroke: whether the store received a lead at all, who it was assigned to, whether it was reassigned and by whom, and how long it sat before anyone touched it. Combined with the login log and role based user management, you can also answer the harder questions that come up when a salesperson leaves for a competitor and someone asks what they had access to.

The reporting layers turn the individual records into a pattern. Activity reporting shows what people did, company reporting shows store level performance, and management reporting rolls it up. Because texting, calling and email all happen inside the platform rather than on personal phones, that activity data is real rather than self reported, which is the difference between a report you coach from and one everyone quietly ignores. More on the measurement side in lead response tracking.

Distribution is only half the job. The lead now has an owner, and what happens next decides whether the rotation was worth building.

Automations can fire an immediate text and email so the customer hears from your store within seconds. RCS with automatic SMS fallback renders the message richly on handsets that support it without leaving anyone out. The click to call dialer and VoIP softphone put the first call one click away rather than behind a copied number and a personal cell phone. Call recording with transcription means the conversation becomes searchable text a manager can read in half a minute.

At the same time, the phone validator and email validator check the contact details on the way in. Knowing immediately that a number is not a working mobile line is worth a great deal more than discovering it after two days of unanswered calls, and it stops a rotation from being polluted by leads that were never contactable.

Set a standard for first response, write it down, and let the system enforce it rather than leaving it to memory. The argument for why that number matters more than almost anything else in the pipeline is on response time SLAs.

Any rotation needs an answer for the case where the assigned person does nothing, because that case is common and it is where deals disappear quietly rather than loudly.

Missed lead alerts raise a flag when a lead passes your response standard untouched. Task automation creates the follow up work and surfaces it to a manager when it goes overdue rather than letting it sink to the bottom of a list. Reassignment then becomes a decision someone makes with information, and it is recorded in the history like every other assignment.

One piece of management advice that has nothing to do with software. Publish the response numbers by person, weekly, where the team can see them. Most hoarding and most slow response stops within two weeks of the numbers becoming visible, without a single conversation about it. The pattern you will find is usually specific rather than general: one shift, one source, one day of the week, one person.

And expect the first month of real data to be uncomfortable. Every store we have seen believes its follow up depth is higher than it is. Our page on what to expect from car sales leads covers why that gap is where most of the lost money sits.

Three starting points that cover most stores. A small independent with four salespeople usually wants one rotation, current membership, immediate automated response, and a manager alert at your response threshold. That is the whole configuration and it takes an afternoon.

A store with a business development team usually wants inbound internet leads on a business development rotation, floor traffic and repeat customers routed to individuals, seller leads to whoever appraises, and a separate evening list. Add escalation to the business development manager rather than to the general sales manager.

A group wants group level defaults with per rooftop deviation, territories drawn deliberately so two of your own stores are not competing for the same shopper, and management reporting that compares stores on first response rather than only on volume.

All of it is included in the platform rather than priced as an add-on. CRM Only starts at $199 a month if you bring your own lead sources. Plans that include exclusive local leads start at $799 for inbound buyer leads, $999 for seller lead programs and $1,599 for the combined plan, month to month with no long term contract. Figures live on the pricing page, and the routing detail continues on lead routing rules. We cannot guarantee close rates, and nobody honestly can, but you will always know exactly where every lead went.

Can the rotation skip salespeople who are off?

Yes, by keeping rotation membership current and using separate lists for separate shifts. Keeping those lists accurate is the most neglected piece of maintenance in any CRM and it deserves a named owner and a weekly check.

Can we route certain lead types outside the rotation?

Yes. Rules can route by source, vehicle type, time window or lead family, and distribution lists cover the cases a rule does not describe cleanly. Repeat customers and seller leads are the two overrides most stores want first.

What happens to leads that arrive after hours?

Automations can send an immediate text and email regardless of who is working, so the customer gets a real response at once while the human assignment follows the shift list. That change usually moves after-hours conversion more than any rotation adjustment.

How do we prove who received a given lead?

Global lead history records every assignment and reassignment with timestamps, and the login log covers access. That settles the recurring dispute about whether a lead was delivered and who had it.

Does this apply to leads from our own website and other providers?

Yes. Lead feeds and custom source feeds bring outside flow into the same routing logic, so the rules apply to everything rather than only to leads we deliver.

What stops a salesperson from hoarding leads they never work?

Missed lead alerts and overdue task escalation surface it, and the reporting makes it visible by person. In practice, publishing response numbers weekly stops most of it within two weeks.

Watch the rotation assign, the instant response fire and the history record all of it. Month to month, no long term contract.