Mon - Sat: 9:00 AM - 6:00 PM
Call: 844-376-2274
AI & Communications
BDC Lead Routing Software
Rules that put every lead on a named person in seconds, escalate when nobody moves, and leave a record you can settle an argument with.
Routing is quiet, and that is why it leaks
Nobody in a dealership stands up in a meeting and says the routing is broken. They say the leads are bad. Those two complaints look identical from the general manager's chair, and telling them apart is the whole value of a real routing engine.
Here is the pattern. A lead arrives at 6:40pm. It lands in a shared queue because the agent it was assigned to left at six. It sits overnight. At 9:15 the next morning someone calls, gets voicemail, marks it attempted, and the record starts its slow drift toward dead. The customer bought that Saturday somewhere else. Nothing in that sequence shows up as a routing failure. It shows up as a bad lead.
Every store has a version of this, and most of them are losing more opportunity to it than to any lead source problem. The fix is not effort, because your people are already working. It is a set of rules that decide assignment instantly, notice when nothing happens, and move the lead to somebody who will act.
The six decisions a routing engine has to make
Write these down before you evaluate any vendor, because a routing feature that only answers the first two is a queue with extra steps.
- Who gets it. A named person, not a department, and not a pool that everyone can see and nobody owns.
- By what logic. Round robin, weighting toward stronger closers, by source, by store, by vehicle interest, or a specific person for a specific campaign.
- How fast they know. Notification that actually reaches them, including on a phone away from a desk.
- What happens when nobody moves. This is the decision most systems skip entirely, and it is the expensive one.
- What happens after hours and on the days the store is closed.
- Whether the customer is already someone's. Routing a returning customer to a stranger burns trust and starts fights.
LeadLocate covers all six through global lead distribution with rules, distribution lists for the cases a rule cannot express, and lead history that records the outcome of every decision. The configuration detail lives on the lead routing rules page.
Round robin, and the three ways it goes wrong
Round robin is the default for good reasons. It is fair, it is easy to explain to a sales floor, and it stops the loudest person in the room from harvesting the best sources. It also fails in three specific ways that you should plan for rather than discover.
The first failure is blind fairness. Even distribution means your weakest closer gets the same share of your most expensive traffic as your best one. That is fair to the staff and unfair to the store. Weighting is the answer, and it should be explicit and reviewed monthly, not an unspoken favor.
The second is availability. A strict rotation hands leads to people who are off, at lunch, in a delivery or on vacation. Any rotation worth running has to respect who is actually working right now, or it is just a slower shared queue.
The third is volume blindness. An agent already sitting on nine active conversations does not need a tenth more than the person with two does. Cap concurrency or watch quality drop. There is a fuller treatment on the round robin distribution page.
Escalation is the rule that pays for the software
If you only configure one thing, configure this. An assignment with no escalation is a hope, not a rule.
The pattern that works in most stores is short and blunt. If there is no logged contact attempt within a few minutes of assignment, the assigned agent gets a nudge. If nothing has happened by the time a second short window closes, the lead reassigns to the next person in the rotation and a manager is notified. The exact intervals belong to you and depend on staffing, but they should be measured in minutes, not hours.
Two things make this work politically as well as technically. First, the escalation notifies rather than accuses, because the goal is a worked lead and not a disciplinary file. Second, everyone can see the rule, so the reassignment is a known consequence rather than a manager playing favorites. Missed lead alerts are the mechanism, and there is more on them at missed lead alerts.
After hours needs its own rule. Decide in advance whether evening and Sunday leads hold for the morning rotation, go to a designated person on call, or trigger an automated acknowledgement that buys you until open. Any of the three beats the default, which is silence.
Route by source, because sources do not behave the same
Treating every lead the same because they all arrive in the same inbox is a habit worth breaking. A shopper who filled out a finance form is not in the same place as somebody who asked about hours, and a seller lead from a local owner asking for an offer on their vehicle needs an entirely different opening than a buyer lead.
The platform ingests lead feeds and custom source feeds, so third party providers, your own website forms, lead pages and campaigns all land with their source attached. Rules can then route on that source: finance inquiries to whoever handles them, acquisition inquiries to the used car manager rather than the floor, a specific campaign to the person who owns it.
Two practical notes. Set the source rules up before you add a new provider, not after the first week of complaints. And keep source naming disciplined, because routing rules built on inconsistent source labels are the reason a store ends up with fourteen rules doing the work of four. Source hygiene also feeds your lead attribution reporting, so the cleanup pays twice.
Ownership, duplicates and the fights they cause
The single most damaging routing mistake is sending an existing customer to a new person. The customer notices immediately, because they have to explain themselves twice. The original salesperson notices too, and that is where a good morning turns into a management problem.
Duplicate detection has to run at the routing moment rather than during a cleanup later. When a new submission matches an existing record by phone or email, the right default is to attach it to that record and notify the current owner instead of creating a fresh lead for a fresh person. Exceptions belong to a manager, not to a rule.
You also need a defined reassignment path for the ordinary cases: a salesperson leaves, an agent goes on vacation, a customer asks for someone else. Doing that in bulk and logging it keeps history intact instead of orphaning a few hundred records that nobody works again. That is a real category of loss, and it is covered at orphan lead management and duplicate lead management.
The audit trail, and what a manager should do with it
Global lead history records where every lead went, when, and what happened next. That sounds like a compliance feature. It is actually a coaching feature, and it is the reason routing arguments end.
The weekly review that gets results takes about fifteen minutes. Pull every lead from the last seven days with no contact attempt inside your target window and look at who they were assigned to. Pull every lead that escalated and look at whether the same names keep appearing. Then pull the leads that were worked well and read one or two of those conversations, because holding up a good example does more than correcting a bad one.
Because calls, texts and emails run inside the platform rather than on personal cell phones, that history is observed rather than reported. Add call recording with transcription and a manager can go from a routing report to the actual conversation in two clicks, which is how you tell a routing problem from a skill problem.
Rolling out new rules without a revolt, and what it costs
Routing changes touch pay, so treat the rollout as a people project with a software component rather than the reverse.
Announce the rules before they go live and put them in writing, including the escalation intervals. Run them for two weeks without consequences and publish the report, so everyone can see what the rule would have done. Adjust the intervals once based on what you learn, because your first guess at the timing is usually too aggressive for your staffing. Then enforce it consistently, because a rule enforced unevenly is worse than no rule at all.
Routing is part of the CRM rather than an add on, so it comes with the platform. CRM Only starts at $199 a month for a store bringing its own lead sources. Programs that include exclusive local leads in a mapped territory start at $799, and the seller side at $999, with the combined plan at $1,599. Everything is month to month with no long term contract, and no DMS integration or inventory feed is required to run it. Current figures are on the pricing page, and contact us if you would rather have someone walk your current rules with you first.
Frequently Asked Questions
Can we mix routing methods in one store?
Yes. Round robin for general internet leads, a named owner for a specific campaign, and source based rules for finance or acquisition inquiries can all run at once. Distribution lists cover the cases a rule cannot express cleanly.
What happens to a lead nobody touches?
Escalation. The assigned agent is nudged first, and if there is still no logged activity the lead reassigns to the next person in the rotation with a manager notified. You set the intervals, and they should be minutes rather than hours.
How are after hours and weekend leads handled?
You choose the rule: hold for the next rotation, send to a designated person on call, or trigger an automated acknowledgement that holds the customer until you open. Any explicit rule beats the default, which is a lead sitting untouched overnight.
Will a returning customer get routed to a new salesperson?
Not if duplicate detection is on. A submission that matches an existing record by phone or email attaches to that record and notifies the current owner, rather than creating a new lead for a new person.
Can I see where a specific lead went and when?
Yes. Global lead history logs every assignment and reassignment with timestamps, and because communication happens inside the platform you can go from the routing record straight to the actual call, text or email.
Does routing require a DMS integration?
No. Neither a DMS integration nor an inventory feed is required to operate. Lead feeds and custom source feeds bring leads in from your providers, website forms and campaigns on their own.
Bring your current routing rules and we will find the gap
Book a walkthrough and we will map assignment, escalation and after hours coverage against how your store actually staffs, then show you the lead history behind it. Month to month, no long term contract.


LeadLocate® All rights reserved. Other product and company names mentioned herein are the property of their respective owners.
Answers to your questions:
LeadLocate is an all-in-one lead generation software and CRM platform. We generate in-market sales leads and provide you with all the tools necessary to sell that customer. All of your leads, texts, calls, emails, deals, and files are available in one place, accessible with a single login.
LeadLocate® All rights reserved. Other product and company names mentioned herein are the property of their respective owners.
Answers to your questions:
LeadLocate is an all-in-one lead generation software and CRM platform. We generate in-market sales leads and provide you with all the tools necessary to sell that customer. All of your leads, texts, calls, emails, deals, and files are available in one place, accessible with a single login.



