Multi-Rooftop Lead Routing: What Actually Works

You run five stores. Same ownership, same ad agency, same CRM. And somehow, a customer who submitted a form on your Honda site is sitting in your Toyota store’s CRM queue right now. Nobody called her. Nobody knows she’s there. She’ll buy from the single-point Honda dealer down the road who picked up the phone in 40 seconds.

This is the multi-rooftop routing problem. At a single store, lead routing is already the difference between a sale and a missed opportunity. At a dealer group, it’s that problem multiplied by every rooftop, every brand, and every overlapping market you operate in.

It sounds like you’ve already tried fixing this. You’ve built CRM rules. You’ve assigned territories. You’ve told the BDC to “make sure Honda leads go to Honda.” And leads still end up in the wrong queue, get worked by the wrong person, or don’t get worked at all.

Here’s what actually works.

The Core Problem: Shared CRM, Separate Stores

Most dealer groups run one CRM instance or a handful of connected instances. Leads come in from OEM sites, third-party sources, and your own websites. The CRM has to figure out which store gets each lead.

When that logic is wrong, or when there’s no logic at all, three things happen:

1. Leads land at the wrong rooftop and sit until someone manually forwards them.
2. Two stores work the same lead simultaneously and the customer gets called twice.
3. Leads from a high-performing store overflow into a low-performing store’s queue and die there.

Each of those is a lost deal. At $3,200 average front gross plus $2,100 in F&I, that’s $5,300 per unit that walked. Across five stores doing 150 leads per month each, even a 5% misroute rate is 37 leads per month landing in the wrong place. If half of those never recover, that’s over $98,000 per month in lost front-end gross.

Geo-Routing: Closest Store Wins

The simplest multi-rooftop rule is proximity. Every lead includes a zip code or postal code. Map each code to the nearest store.

It seems like this should be obvious, but most groups don’t do it cleanly. They let the CRM assign based on which website the customer found, not where the customer actually lives. A customer in zip 30318 finds your Marietta Chevy store through a Google ad but actually lives eight minutes from your Buckhead location. Without geo-routing, Marietta gets the lead, the customer drives past Buckhead to test drive, and your Buckhead team never knew the opportunity existed.

Set up zip code tables for each rooftop. When a lead’s zip matches Store A’s territory, it routes there. When it falls in an overlap zone, use a tiebreaker: closest by drive time, or whichever store has the faster response time that week.

Brand Routing: Make and Model Determine the Store

If you operate Honda, Toyota, and a CDJR store, a Civic lead has no business in the Ram queue. This seems obvious. It breaks in practice because:

Want more appointments from the leads you already buy? Try the live demo and see how Ringlead gets a live voice on the lead fast.

• Third-party lead providers don’t always pass the make/model cleanly.
• OEM leads route to whichever franchise code is on file, which may be outdated.
• Trade-in leads mention two vehicles and the system picks the wrong one.

Brand routing needs a hard rule: if the primary vehicle of interest is a Honda product, it goes to the Honda store. Period. No exceptions, no manual review, no “the Honda BDC is busy so let’s send it to Toyota for now.”

The secondary rule handles trade-ins. A customer who wants a Civic and has a Corolla trade goes to Honda. The Toyota store doesn’t need to see it. If you want to route trade-in opportunities separately, build that as a distinct workflow after the sale closes.

Performance Routing: Speed Over “Fairness”

This is where groups get uncomfortable. Performance routing sends leads to whichever store or salesperson picks up the phone fastest. Not whose turn it is. Not which store “owns” that territory. Whoever answers.

At a single store, round-robin feels fair. At a group level, it’s a disaster. Your Honda store averages 3-minute response times. Your Toyota store averages 47 seconds. Under round-robin territory rules, the Honda store gets the same lead volume despite being three times slower.

Performance routing fixes this. Route the lead to the primary store first. If they don’t pick up in 60 seconds, it overflows to the next available store. The customer doesn’t care which rooftop calls them. They care that somebody called. Velocify research shows 391% higher close rates when contact happens within the first minute. That’s the only number that matters.

The “fairness” objection always comes from the store that’s losing leads. The answer is simple: pick up the phone faster. You don’t earn leads by existing. You earn them by answering. For the metrics and methodology behind comparing stores objectively, see how to benchmark lead response across stores.

Overflow Routing: The 60-Second Safety Net

Overflow is the most important rule in multi-rooftop routing and the one most groups skip entirely.

Here’s how it works. A lead comes in for your Chevy store at 2:15 PM. The system rings the Chevy BDC. Nobody picks up within 60 seconds. Instead of that lead sitting in a CRM queue until someone checks their notifications, it immediately rolls to your Ford store across town. The Ford BDC picks up. The customer hears a live voice. The appointment gets set.

Is it ideal? No. The Chevy team should’ve answered. But the alternative was a dead lead. A customer who submitted a form, waited, got nothing, and submitted to your competitor 12 minutes later. That’s the math. An imperfect live connection beats a perfect dead queue every time.

Set your overflow window at 60 seconds. That’s the standard top-performing stores use. Anything longer and the customer is already gone.

The Cherry-Picking Problem at Scale

Cherry-picking is bad enough at one store. At a group, it metastasizes. Your best salesperson at Store A logs into the group CRM and grabs the hottest leads from Store B’s queue. Store B’s numbers tank. Store B’s manager blames the ad agency. Nobody realizes the leads were stolen by their own team.

Multi-rooftop routing has to enforce store boundaries. A salesperson at the Honda store should never see Toyota leads in their queue. The CRM should wall off each rooftop’s leads with hard permissions, not guidelines.

If you’re running performance-based overflow, that’s different. The system made the routing decision, not the salesperson. The distinction matters: system-driven overflow is a process. Salesperson-driven cherry-picking is theft.

Central BDC vs. Distributed: Pick Your Trade-Off

Every dealer group with more than three stores faces this question. Do you build one central BDC that handles all inbound leads, or let each store run its own team?

Central BDC pros:

• Consistent speed across all stores. One team, one process, one standard.
• Easier to staff for coverage. Ten people covering five stores is more flexible than two people per store.
• One training program. One set of scripts. One quality standard.

Central BDC cons:

• The BDC agent setting an appointment at your Chevy store has never walked the lot. They can’t answer “do you have the Z71 in black?”
• Customers sense when they’re talking to a call center versus someone at the store.
• Handoff to the local salesperson adds friction. The customer tells their story twice.

Distributed BDC pros:

• Local product knowledge. The BDC agent knows what’s on the lot.
• No handoff. The person who answers the phone is at the store the customer will visit.
• Store managers control their own team.

Distributed BDC cons:

• Inconsistent speed. Your best store responds in 40 seconds. Your worst store responds in 22 minutes.
• Staffing gaps. When two BDC people at a single store call in sick, that store goes dark.
• Harder to compare performance because each store runs differently.

Most groups above five stores land on a hybrid. Central BDC handles first contact and appointment setting. Local team handles follow-up and day-of confirmation. The central team gets the speed. The local team gets the knowledge.

Reporting Across Locations: The 18% vs. 8% Problem

Here’s a real scenario. Five-store group. Same ownership, same ad agency, roughly the same ad spend of $45,000 per month per store. Same CRM. Each store gets about 150 internet leads per month.

Store A closes at 18%. That’s 27 deals from internet leads. Store E closes at 8%. That’s 12 deals.

Same leads. Same market. Same spend. The difference is 15 deals per month. At $3,200 front gross, that’s $48,000 per month Store E is leaving on the table. Add F&I at $2,100 per deal and it’s $79,500.

The group GM looks at total units and sees Store E “doing fine.” They sold 45 total units last month. But their internet close rate is half of Store A’s, and nobody’s asking why because the CRM dashboard shows green.

Multi-rooftop reporting has to normalize by lead source. Compare internet close rate to internet close rate. Compare speed-to-contact across stores. Compare contact rate, not just total dials. When you put Store A and Store E side by side on the same scorecard, the gap becomes obvious:

	Store A	Store E
Internet leads	150	150
Avg. speed-to-contact	52 seconds	14 minutes
Contact rate	88%	61%
Close rate	18%	8%
Internet deals	27	12
Gross per month (front)	$86,400	$38,400

Store E doesn’t have a lead problem. They don’t have an ad problem. They have a routing and response problem. Fix the speed, and the close rate follows.

What a Working Multi-Rooftop Routing System Looks Like

Lead comes in. The system checks brand first: Honda lead goes to Honda store. Then geo: which Honda store is closest to this customer’s zip code? Then availability: is someone at that store ready to take a call right now? If yes, their phone rings in under 10 seconds. If nobody picks up in 60 seconds, the lead overflows to the next Honda store. If no Honda store picks up, it goes to the central BDC.

No manual assignment. No CRM queue-checking. No “I’ll get to it after lunch.” The customer hears a live voice inside of a minute, and they don’t know or care which location picked up. They know somebody answered.

That’s the system that turns $45,000 per month in ad spend into 24 deals instead of 12. Same leads. Same budget. Better routing.

Try the Live Demo

Frequently Asked Questions

Sources

• Velocify (now ICE Mortgage Technology). “Speed-to-Contact Study.” Findings show 391% higher close rates when contact is made within the first minute of lead submission.
• InsideSales.com. “Lead Response Management Study.” 50% of sales go to the first responder.
• Harvard Business Review. Oldroyd, James B. and McElheran, Kristina. “The Short Life of Online Sales Leads.” HBR, March 2011. 21x qualification drop after 30 minutes.
• Foureyes. “Dealership Lead Follow-Up Study.” 43% of internet leads never receive a real phone call.