Dealership CRM Lead Routing Rules

Most stores have a rotation. Very few have written rules, and the difference shows up on every lead that lands at 7pm on a Saturday.

Every dealership routes leads. Almost none of them can produce the rules on paper. What exists instead is a rotation somebody set up two years ago, a handful of exceptions the internet manager applies from memory, and a general understanding that certain leads go to certain people for reasons nobody can fully explain.

That works until it does not, and the failures are always the same. A lead lands at seven on a Saturday evening and sits until Monday. A previous customer comes back in and gets assigned to a stranger while the salesperson who sold them the last car is standing twenty feet away. A Spanish speaking customer gets three voicemails in English. Two salespeople both believe a lead was theirs and the manager has no record to settle it with.

None of those are software failures. They are unwritten rules meeting a situation nobody thought about. The fix is to write the ruleset down as explicit conditions, put it in the system, and then be able to prove afterward what happened. This page is about writing that ruleset. If you want the mechanics of rotation itself, the round-robin distribution page covers how a rotation is built and where straight rotation breaks.

Keep the inputs limited. A ruleset with fifteen conditions is a ruleset nobody can debug at nine on a busy Saturday.

Ownership. Does this person already belong to somebody? Prior customer, open deal, active conversation. This input outranks every other one and should be checked first.

Source. Website form, chat, phone, third party marketplace, seller lead, walk in follow up. Source is a decent proxy for intent and for how fast the response needs to be.

Time. Business hours, after hours, weekend, holiday. Time changes who is available, and after hours is where most routing designs quietly fail.

Skill or attribute. Language, department, product line, credit situation, commercial versus retail. Use this sparingly. Two or three skill splits is useful, eight is a maintenance problem.

Territory. Relevant for groups with rooftops close together, and for lead programs where the zone around your store defines what you receive in the first place. Two of your own stores bidding against each other for the same shopper is a routing problem disguised as a marketing problem.

Anything outside those five is usually a preference rather than a rule, and preferences belong in a conversation with a manager rather than in the routing engine.

The single most valuable rule in any dealership CRM is the one that asks whether this person is already known. It is also the rule most often missing.

A returning customer routed to a random salesperson costs you twice. The customer repeats themselves to a stranger, which is exactly the experience they were hoping to avoid by coming back. And the salesperson who earned the relationship finds out later, which does more damage to your culture than the deal was worth.

Matching has to be fuzzy enough to be useful. The same person comes in as Bob and Robert, from two different email addresses, with a cell number formatted three ways. If your matching only catches exact duplicates it will miss most of them. Match on normalized phone first, then email, then name plus one other field. Our page on duplicate lead management goes through the matching logic and the cleanup that has to happen first.

Then decide the exceptions honestly, before you need them. If the original salesperson no longer works there, the lead goes to the rotation. If they are on vacation longer than a couple of days, it goes to the rotation with a note. If the customer explicitly asks for somebody else, the customer wins. Write those down, because every one of them will come up.

Here is a working ruleset in evaluation order. Rules are checked top to bottom and the first match wins, which is the only structure that stays debuggable.

Two notes on that table. Rule three sits high on purpose, because suppression has to happen before routing rather than after somebody has already picked up the phone. And rule five reflects that seller leads are time critical: these are local owners who filled out a vehicle offer request and are usually speaking to more than one buyer, so ten minutes is not conservative.

Look at when your leads actually arrive. In most stores a substantial share land outside the hours anyone is sitting at a desk, and the standard design answer is to let them queue until morning. By morning the customer has talked to two other stores.

Three layers fix most of it. First, an automated first response that goes out immediately, is honest about the hour, and sets an expectation. Something that says a real person will call at nine and asks one useful question in the meantime beats silence by a wide margin, and it beats a message pretending to be a live human by more.

Second, an on call rotation for the hours worth covering. Not all of them. Friday and Saturday evening are worth staffing. Three in the morning is not, and pretending otherwise produces a rotation nobody honors.

Third, the inbound phone side has to be routed too, because a customer who calls and gets a full voicemail box has formed an opinion about your store. AutoMail provides IVR, call routing and call forwarding, so after hours calls are directed or captured rather than abandoned. And availability has to be part of the rotation itself: a salesperson on their day off should be skipped automatically, not assigned and then chased.

A routing rule that assigns a lead has done half a job. The half that matters is what happens when the assigned person does nothing.

Set a timer on every rule. Fifteen minutes during business hours is a reasonable default for the first escalation, and the escalation should be visible rather than silent: the manager gets an alert, the lead moves, and the original assignee can see it moved. Silent reassignment teaches people nothing.

Build a second escalation at the hour mark and a third that pulls the lead back to a manager queue by end of day. Most stores stop at the first tier, which means a lead that survives one escalation into an equally distracted person's queue disappears just as thoroughly.

Missed lead alerts are the mechanism, and task automation is what puts the resulting work on a real person's list rather than leaving it as a notification nobody clicks. There is more on the missed lead alerts page. If you want to formalize the timers as a written standard your team can be held to, the response time SLA template gives you the wording.

Not every inbound record should reach a salesperson, and the rules that stop them are as important as the ones that assign them.

Opt outs and blacklist entries come first, and the blacklist has to be central. If a customer told one salesperson to stop contacting them and that ended up in a personal phone rather than in the CRM, the store will contact them again from a different direction. Import your existing suppression lists when you set the system up rather than assuming you are starting clean.

Then there are the softer cases: obvious junk submissions, duplicates of a record created eleven minutes ago, and test entries from your own website vendor. Suppressing these is not about lead quality, it is about not burning your team's time and not embarrassing the store. Nothing here is filtered or scored by us, and we do not make quality claims about what arrives. Every submitted lead in your zone is delivered to you exclusively, and problems are handled by post delivery replacement review. What suppression governs is what your own rules do with a record once it is in your database.

Sooner or later a salesperson will insist they never received a lead, or two people will claim the same customer, or a general manager will want to know why a Saturday afternoon inquiry was answered on Tuesday. Without a record, those conversations are unwinnable and they poison a sales floor.

Global lead history records where every lead went and why: which rule matched, who it was assigned to, when it escalated and where it landed. That log is worth more than most of the reporting in a CRM, because it turns a personality dispute into a factual question. The login log covers the related question of who was actually working when.

Use it proactively rather than only forensically. Once a month, pull the leads that took longest to reach a first response and read the routing history on each one. The pattern is usually a specific rule, a specific hour, or a specific person, and all three are fixable. Chasing it as a general discipline problem is not.

Do not deploy a new ruleset on the first of the month. Build it, then run it in parallel for a week by leaving your existing routing in place and comparing what the new rules would have done. Most stores find two or three conditions they had not considered, and it is much cheaper to find them that way.

When you do switch, change one layer at a time. Ownership matching first, because it produces the fastest visible improvement and buys you credibility with the floor. Then escalation timers. Then skill and after hours routing. Changing all of it at once means that when something goes wrong you will not know which rule did it.

Review the ruleset quarterly and after any staffing change. A rotation with a salesperson in it who left in March is the most common broken rule in the industry, and it silently eats leads for months.

On cost: routing is part of the CRM rather than an add on. CRM Only starts at $199 per month if you already have your own lead sources, programs including exclusive local buyer leads start at $799, and combined buyer and seller programs start at $1,599. Everything is month to month with no long term contract, and current figures are on the pricing page.

What should the first routing rule check?

Whether the person is already known. Open deal owner first, then prior customer if that salesperson is still employed. A returning customer routed to a stranger costs you the relationship and damages the floor's trust in the system.

How fast should escalation fire?

Fifteen minutes during business hours is a sensible first tier, with a second escalation at an hour and a third that returns the lead to a manager queue by end of day. Stopping at one tier is why escalated leads still get lost.

How do we handle leads that arrive after hours?

An immediate automated first response that is honest about the hour, an on call rotation for the hours actually worth staffing, and IVR with call routing so inbound calls are directed rather than abandoned into a full voicemail box.

Can different rooftops in a group have different rules?

Yes. Global distribution rules set the group default and individual stores can deviate where they have a reason to, with distribution lists covering the cases that do not fit a rule. Lead history still rolls up.

How do we settle a dispute over who owned a lead?

Global lead history records which rule matched, who it went to, when it escalated and where it ended. That turns an argument about memory into a factual question, which is the only way these get resolved cleanly.

Do routing rules require a DMS integration?

No. Neither a DMS connection nor an inventory feed is required to operate the platform, so routing works the same whether you have one or not.

We will map your ownership matching, escalation timers and after hours coverage, then show you the history that settles who got what. Month to month, no long term contract. Call 844-376-2274.