How Should a BDC Rep Handle Managing a Shared BDC Queue Across Stores?

A BDC rep managing a shared queue across stores should establish clear assignment rules (round-robin or skill-based), use a centralized system to track which leads belong to which store, set response-time standards for each location, and communicate handoff protocols with store managers weekly. Without structure, leads fall through cracks and follow-up becomes chaotic—especially in multi-store markets where phone volume and inventory vary by location.

What does a shared BDC queue actually look like across multiple locations?

A shared queue means one BDC team—or even one rep,handles inbound and outbound lead traffic for two or more dealerships. This might be a regional operation with a satellite lot, a family-owned group with stores 30 miles apart, or a hub-and-spoke model where one sales office feeds multiple service bays.

The challenge: leads come in with zero context. A call rings in. The rep doesn't know if it's a Fort Worth store truck buyer or a San Antonio inventory shopper. An email lands. It could be a trade appraisal question for the body shop location or a service-menu inquiry for the north store. Without instant clarity, you're guessing,and guessing wrong costs you deals.

Here's the real problem nobody talks about: managers at each location will assume their store's leads get priority. So a service advisor at Store B watches inbound traffic pile up on days when Store A is slammed, and morale tanks. BDC reps feel torn between competing demands. Leads age out because they're tagged to the wrong store and nobody touches them.

A shared queue isn't inherently bad. It can flatten workload spikes, let you cross-cover vacations, and build efficiency. But it only works if leads are segregated and routed with military precision.

How do you assign leads to the right store in a shared queue?

Start by deciding your assignment method. The two most common approaches are round-robin and skill or market-based routing.

Round-robin assignment

Leads bounce to Store A, then Store B, then Store A again. This is fair and predictable. It works well if your stores have similar volume, inventory depth, and customer profiles.

Pro: No arguments about fairness. Leads get distributed evenly.
Con: Doesn't account for store-specific needs. You might send a luxury SUV shopper to a store that sells mostly work trucks.
Best for: Identical store formats, similar walk-in patterns, comparable inventory mixes.

Skill or market-based routing

You route based on lead type, store location, or customer intent. A commercial-fleet inquiry goes to the store with the fleet manager. A luxury buyer goes to the location with premium inventory. A service lead goes to whichever service department has capacity.

Pro: Maximizes conversion because leads match store strengths. Respects store-manager preferences and CSI drivers.
Con: Requires manual decision-making. It's slower and only works if you document the rules clearly.
Best for: Multi-format groups (truck store + sedan store), wide geographic spread, stores with specialized inventory or team skill sets.

Most multi-store operations use a hybrid. You route by lead type first (sales vs. service), then by round-robin within that category. A sales lead goes to sales queues at both stores, alternating. A service lead goes to the nearest location or the one with open slots.

Whichever you choose, document it. Write it down. Share it with every store manager and update it every quarter. Stores change. Inventory changes. What worked in July might break in October when the lot rotates.

What systems and tracking do you need?

You need three things: a lead-management system that supports multiple locations, a clear tagging protocol, and a dashboard everyone can see.

Lead-management system with multi-store support

Your CRM or DMS must allow you to tag leads by store ID and track assignment history. You want to see:

Which store each lead was assigned to and when
How long it sat before first contact
Whether it converted or transferred to another location
Response time by store and by rep

If your current system doesn't support multi-store tagging natively, you'll need a workaround. Some teams use a shared spreadsheet with color-coding by location. It's clunky, but it beats guessing. Better yet, a platform like Dealer1 Solutions handles multi-dealership workflows and lets you see queue depth, assignment rules, and hand-offs across all locations from one view.

Tagging and naming conventions

Use consistent naming. Tag leads as "Store-FW" (Fort Worth), "Store-SA" (San Antonio), or "Store-A" and "Store-B",not "HQ," "the other place," or "satellite." Consistency matters because people skim. Vague tags cause misdirection.

Also tag by lead source and intent:

Sales-Trade | Sales-Showroom | Sales-Website
Service-Phone | Service-Online | Service-Walk-in
Parts-Counter | Parts-Phone

Now you can run reports: "How many sales leads are aging past 24 hours per store?" or "Which store has the highest first-contact rate on website leads?" These reports catch problems before CSI tanks.

A visible, shared dashboard

Every store manager should see queue depth in real time. Not a guess. Not a daily email. Live numbers showing:

Leads waiting for first contact by store
Average age of lead in queue
Response-time SLA compliance
Today's assignment count by store

When a manager sees their queue climbing, they know to ask for overflow help or pull a sales rep to make calls. When the BDC rep sees Store A buried and Store B quiet, they can shift capacity proactively. This kind of workflow,where everyone sees the same data,is the difference between reactive firefighting and deliberate operations.

What response-time standards should you set by store?

Response time is the biggest mover of CSI and conversion. You need store-specific standards because not all stores operate the same way.

A typical benchmark:

Showroom traffic (sales): First contact within 2 hours during business hours. These are hot leads; they walked in or called immediately after a search.
Internet leads (sales): First contact within 4 hours on business days, 24 hours on weekends. Less urgent, but still time-sensitive.
Service phone calls: Same-day callback if called after 4 p.m. or on weekends. Next-morning callback if called during the day.
Trade appraisals: First contact within 1 business day.

But here's the real talk: your standard should be tighter than the industry average. If industry standard is 4 hours, you should target 2. The stores that win in competitive markets aren't the ones hitting standard,they're the ones crushing it.

Now, shared queues make this harder because you're managing multiple stores' expectations at once. A lead assigned to Store A gets a 2-hour SLA, but if BDC rep 1 is buried on Store B's service callbacks, that Store A lead ages.

Solution: Prioritize ruthlessly. Your SLAs should rank like this:

Showroom traffic (sales)
Service phone calls (same-day emergencies)
Internet sales leads
Service online or walk-in requests
Parts inquiries

During a crunch, don't let a parts phone call bump a showroom buyer. Set this priority ladder with your store managers and stick to it.

How do you handle handoffs and transfers between stores?

A customer calls Store A, interested in an F-150. Store A doesn't have the right year or color. Store B, 25 miles away, has exactly what they want. Now what?

Without a clear handoff protocol, this happens:

Store A rep calls Store B and says "Hey, I got a guy who wants a truck. You got one?"
Store B says "Yeah, bring him in."
Customer shows up. Store B had that truck yesterday; it sold. Nobody updated the shared inventory list. Customer is furious.
The lead disappears into a gap. Store A thinks it's Store B's problem. Store B thinks it's a no-show.

Your handoff protocol should look like this:

Step 1: Confirm inventory in real time

Before you transfer a customer, verify the vehicle is still on the lot. Check your inventory system,the one source of truth. Don't rely on a text or a phone call to the other store.

Step 2: Create a transfer note

Document the handoff in your CRM. Log the reason (inventory, appointment availability, customer request, etc.). Tag it as a transfer. Both stores should see this note. Include:

Customer name and phone
Vehicle details (year, make, model, VIN)
Which rep is handling it now
Expected appointment date/time
Any special notes (credit-challenged, trade-in pending, etc.)

Step 3: Set an ownership timer

The receiving store owns it. They confirm the appointment within 2 hours. If the customer doesn't show, they document it and it goes back to the originating store or closes as a no-show. No orphaned leads.

Step 4: Sync with both managers

Send a Slack or email to both store managers summarizing transfers that happened that day. They'll spot problems fast: "Wait, we didn't have that truck" or "That customer called me directly." Gaps surface and you patch them.

This might sound rigid, but it's not. It's just documentation. A 30-second note prevents a customer from falling into a void and saves your reputation. Stores that track transfers properly see 20–30% better conversion on inter-store moves because both locations are rowing the same direction.

How should you communicate with store managers about queue performance?

Weekly syncs are non-negotiable. Spend 30 minutes on a call or Slack review with each store manager. Walk through:

Response-time compliance for the week (% of leads touched within SLA)
Average queue age by day
Leads transferred between stores
Any bottlenecks or patterns you're seeing
Staffing adjustments needed for the coming week

This conversation surfaces problems early. A manager might tell you, "Tuesday afternoon, we're always slammed with walk-ins and my sales team can't make outbound calls." Now you know to batch outbound dialing for Tuesdays early morning or reassign some of Store B's volume for that window.

Also,and this is important,give store managers a say in assignment rules. If they feel the shared queue is unfair, fix it or explain why it's fair. When managers understand the logic and feel heard, they advocate for the system instead of fighting it. When they don't, they'll direct customers to BDC reps directly, and you'll end up with a shadow queue that nobody tracks.

What metrics matter most for a shared BDC queue?

Track these four numbers religiously:

1. First-contact rate

Percentage of leads touched by a live person (phone, email response, SMS) within your SLA. Target: 95% or higher.

2. Queue age (average and 90th percentile)

How long does a lead sit before first contact? Track both the average and the 90th percentile. The 90th percentile catches your slow-moving outliers,leads that sit for days. Target: No lead sits past your SLA threshold.

3. Response time by store

Which store's leads are aging? Is one location consistently slower than the other? This surfaces assignment imbalance or staffing gaps.

4. Transfer rate and rework rate

How many leads get transferred between stores? How many get called back by the same customer because the first contact was weak? A high rework rate suggests your BDC team doesn't have enough context or skill to handle the queue. A high transfer rate might mean your assignment rules are wrong.

Report these metrics weekly to management. Don't hide bad numbers. Use them to make better staffing and process decisions.

What common mistakes should you avoid?

Here are the traps we see teams fall into:

Mistake 1: No clear definition of "shared"

Everyone assumes something different. One manager thinks you'll prioritize their store; another assumes equal splits. You think you're rotating leads; they think you're random. Ambiguity breeds resentment. Define it on paper, get buy-in, and revisit quarterly.

Mistake 2: One rep owns too much

Assigning a multi-store queue to a single rep sounds efficient until that rep takes a day off or quits. Suddenly, nobody knows the protocols and the queue implodes. Cross-train at least two reps. Let them trade queues weekly or by shift.

Mistake 3: Ignoring store-specific inventory differences

Store A has premium trucks, high price point, older buyers. Store B has economy sedans, younger buyers, lower price point. If you round-robin leads without looking at vehicle type, you'll send a luxury buyer to the economy store and a first-time buyer to the premium lot. They'll leave confused. Match lead type to store strength.

Mistake 4: No fallback for system failures

Your DMS goes down. Your email system hiccups. Now what? You need a paper-based or phone-based backup. I've seen teams lose an entire day's leads because they relied 100% on automation and had no contingency. Keep a simple, daily log of inbound calls with store tags. It's old-school, but it works.

Mistake 5: Not auditing assignment accuracy

Pull a random sample of 20 leads from last week. Check: Did they get assigned to the right store? Did the tag match the customer's intent? Did they get the right response time? Audit monthly. You'll find routing errors that are costing you deals.

Frequently asked questions

What if one store's volume is three times higher than the other? Should I still use round-robin?

No. Use weighted round-robin or skill-based routing. If Store A gets 300 leads per week and Store B gets 100, send three Store A leads for every one Store B lead,or assign based on response capacity (how many calls each store can handle per day). Round-robin only works if stores are roughly equal in volume.

How do I prevent a BDC rep from favoring one store over another?

Transparency and measurement. Make the queue visible to all managers and audit response times weekly by store. If one store consistently gets slower response, it's visible immediately and you can address it with the rep. Also rotate which store the rep starts with each day or week,don't always start with their "favorite."

Should service leads and sales leads be in the same shared queue?

Not necessarily. Service has different urgency, skill requirements, and SLAs than sales. Many multi-store operations run separate service and sales queues. But if you combine them, prioritize ruthlessly (sales showroom first, then service emergency calls, then sales internet) and use clear tagging so reps know what they're picking up.

How often should I adjust the assignment rules?

Quarterly at minimum. Monitor the metrics monthly, but don't tinker every week,changes need time to settle. Every three months, sit with your store managers and look at volume trends, conversion by store, response times, and CSI. If something's broken, fix it. If it's working, leave it alone.

What's the best way to train a new BDC rep on a multi-store queue?

Pair them with your strongest rep for two weeks. Have them shadow calls first, then take calls while shadowed. Walk them through one full day in each store's shoes. Review the assignment protocol, SLA expectations, and common handoff scenarios. Test them on queue tagging accuracy before you let them own leads independently. Don't rush it,a month of strong training pays off in 10 months of clean data.

Can a small dealership group (2 stores) use the same BDC approach as a large group?

Yes, but simplified. You still need clear assignment rules and response-time standards. For a two-store operation, round-robin usually works fine. For handoffs, a simple phone call plus a CRM note is enough. The principles scale; the complexity doesn't have to.