The BDC Rep's Checklist for Managing a Shared BDC Queue Across Stores
A BDC rep managing a shared queue across multiple stores needs a daily checklist covering lead routing, response-time tracking, store-assignment clarity, follow-up sequences, and hand-off accountability. The biggest risk is leads slipping through cracks between locations—so your checklist must lock down who owns each lead, when it moves to the next step, and how you'll catch delays before CSI tanks.
Why a shared BDC queue creates friction in the first place
You know that moment when a lead comes in and three people think it belongs to somebody else? That's the shared-queue problem in its purest form. When you're managing BDC reps across multiple store locations, a single lead database means every rep can see every lead—which sounds great until you realize nobody's clear on whose turn it is to work it.
The chaos compounds fast. A lead arrives at 2:47 p.m. on a Tuesday. Store A thinks it came from a Store B web form, so they skip it. Store B assumes the digital marketing person at Store A already touched it. By Wednesday morning, the lead has been sitting untouched for 16 hours, and when the customer finally gets a call, they've already bought from somebody else.
Shared queues also create a "tragedy of the commons" dynamic around response time. If every rep knows that three other reps could grab a lead, the incentive to work it fast dissolves. Actually,scratch that, the real problem isn't laziness. It's that without clear ownership, reps waste time wondering if they should pick up a lead at all, or if they're duplicating effort. You lose focus and momentum.
A solid checklist doesn't eliminate the shared queue; it just makes sure the queue works like it's supposed to.
The daily stand-up: start here every single morning
Every BDC team managing a shared queue across stores needs a 5-minute daily stand-up. Not a meeting,a stand-up. Everyone in the channel (or via a quick team sync) answers three questions:
- How many leads are in each store's bucket right now? Pull the number from your DMS this morning. If Store A has 23 leads and Store B has 4, you know there's an imbalance.
- What was yesterday's response time to first contact? You're looking for the median time from lead arrival to first outbound call or text. If it's creeping past 2 hours, something's broken.
- Are there any leads over 24 hours old still in the queue? These are your red flags. Every lead older than a day without at least two contact attempts is a CSI risk and a missed revenue opportunity.
This isn't busywork. You're building real-time visibility into queue health across all locations. Stores that get this right tend to catch bottlenecks on the same day they form, not three days later when the damage is done.
Lead routing and assignment: the foundation of your checklist
Before a lead can be worked, it has to be assigned. And before it can be assigned, you need a routing logic that everyone agrees on.
Set a clear routing rule and document it
Your routing checklist item is simple: Every lead has a primary assigned store within 15 minutes of arrival. Not "eventually." Fifteen minutes.
How you assign it depends on your dealership's structure. Some stores route by lead source (web leads to Store A, phone leads to Store B). Others rotate by rep availability or store inventory match. Others use a round-robin to balance load. Pick one rule and write it down in a place every rep can see it,a shared doc, a pinned message in your team channel, or a placard above the desk.
The rule itself matters less than the fact that there IS a rule and everyone knows it.
Mark ownership visibly in your DMS
Your DMS should have a field that says "Primary Store" or "Assigned Queue." Make sure that field is filled in before a lead hits the rep pool. Some dealerships use notes or tags. The medium doesn't matter as much as the consistency,you need to be able to look at any lead and know instantly which store owns it.
This is the kind of workflow Dealer1 Solutions was built to handle,each lead gets a clear owner, and every rep sees who that is at a glance.
Response time and contact attempts: your core daily metrics
Managing a shared queue means managing response time obsessively. Here's what your checklist covers:
First contact within two hours (or your store's SLA)
Check your DMS daily for any lead that arrived more than 2 hours ago without a note showing a phone call, text, or email attempt. Flag it. Assign it to a specific rep with a note: "First contact attempt due now." Don't assume it'll happen; make it visible and accountable.
A typical dealership sees roughly 60–70% of leads contacted within 2 hours convert at a much higher rate than leads touched after 4 hours. The difference is real and it's measured.
Track the sequence: first attempt, second attempt, third attempt
Your BDC reps need a clear follow-up sequence burned into their workflow:
- Phone call (first attempt, within 2 hours)
- Text message (if no answer, within 30 minutes of first attempt)
- Email (if no text response, within 4 hours)
- Phone call (second attempt, next business day)
- Text message (second attempt, next business day)
- Hand off to sales team or drip campaign (if no contact after 48 hours)
Your checklist item: Every morning, verify that leads in the queue have a note showing which attempt number they're on. A lead without a contact note is a lead nobody's worked yet. A lead with five days of no contact notes is a lead that's fallen through the cracks.
Create a "hot lead" flag for high-priority vehicles
Some leads matter more: in-stock inventory matches, high-intent keywords, previous customers, trade-ins. Tag these in your DMS so reps see them first. Your checklist includes a daily scan for hot leads that haven't been contacted yet.
Managing handoffs and preventing duplicate work
One of the biggest wastes in a shared queue is two reps calling the same lead on the same day. Your checklist prevents it.
Add a "last contact" timestamp
Every time a rep makes contact (call, text, email, or even a voicemail), they log it with a timestamp and a note about what happened and what the next step is. Before a rep picks up a lead, they check this field. If the last contact was today, they skip it (unless they're following the sequence you set). If it was three days ago, they're good to work it.
Use a status field for stage clarity
Your DMS status might look like: "First Contact Attempted," "Voicemail Left," "Texted,Awaiting Reply," "Spoke with Customer," "Scheduled Appointment," "Transferred to Sales," "No Contact After 48 Hours."
These statuses should auto-update based on rep activity, or reps should update them manually every time they touch a lead. Your checklist includes a 10-second scan at the end of each day: any lead with a status older than 24 hours without a new note gets reviewed for follow-up tomorrow.
Load balancing across stores: keeping the queue fair
A shared queue can accidentally create resentment if Store A gets 30 leads a day and Store B gets 8. Your checklist manages the math.
Track leads per store per day
Pull a daily report showing how many NEW leads each store received in the last 24 hours. If you see a pattern where Store A always gets twice as many, investigate. Is the web form routing misconfigured? Does Store A's marketing budget dominate? Is there a seasonal pattern? Understanding the imbalance helps you adjust.
Redistribute when necessary
If Store A has 40 leads and Store B has 5, and you have a BDC rep at each location with capacity, move some leads intentionally. Not randomly,use your routing rule. If Store A is swamped, temporarily route new leads to Store B for the next few hours until the queues even out.
Monitor hours per lead worked
Beyond raw lead count, track how much BDC time each store's leads are consuming. A used-vehicle lead might take 20 minutes of phone time to explore budget, timeline, and trade-in. A new-vehicle lead with a trade might take 45 minutes. If one store's queue is skewed toward high-effort leads, adjust the workload or staffing accordingly.
Escalation and stuck leads: the safety net
Every shared queue needs an escalation protocol.
Define "stuck" clearly
A lead is stuck if it's been in the queue for more than 48 hours without a confirmed contact or a reason for the delay (e.g., "Customer requested callback Friday at 10 a.m."). Your checklist includes a daily scan for stuck leads at 4 p.m.
Who escalates, and to whom?
If a lead is stuck, it doesn't stay stuck. The escalation might be: BDC rep → BDC manager → sales manager. Or: reassign to a different rep, or bump it to the sales team for a warmer handoff. The point is that no lead ages without a conscious decision by someone in leadership.
Track escalations
Keep a log of escalated leads. Once a week, review them. Are the same reps escalating lots of leads? Is there a time-of-day pattern? Are certain lead sources harder to contact? This data tells you where your process is breaking down.
Weekly review: the meta-checklist
Your daily checklist is tactical. Your weekly review is strategic.
Once a week, pull a summary report covering:
- Total leads received across all stores
- Average response time to first contact (target: under 2 hours)
- Percentage of leads contacted within 24 hours
- Average follow-up attempts per lead
- Leads currently stuck in queue (over 48 hours, no recent contact)
- Leads handed off to sales (and the reason: appointment set, unqualified, no contact)
- CSI scores by store (if available)
Look for trends. If response time is creeping up, you need more BDC headcount or a process change. If one store consistently has older leads, that rep might need coaching or a different routing strategy. If CSI is dropping at one location, it might be because leads are sitting too long before handoff to sales.
This weekly discipline keeps your shared queue from drifting into chaos.
Technology: what your DMS checklist should include
Your DMS should make this checklist easier, not harder. At a minimum, confirm that your system can:
- Assign leads to a specific store with a visible field
- Timestamp every contact attempt (call, text, email)
- Show the rep who last touched a lead and when
- Filter and sort leads by store, age, status, and contact attempts
- Generate daily reports on queue health (leads by store, response times, stuck leads)
- Flag leads over a certain age threshold automatically
- Support bulk actions (reassigning 5 leads at once, for example)
If your DMS can't do these things, your checklist becomes a manual nightmare and reps will cut corners.
Frequently asked questions
How do I handle a lead that matches both Store A and Store B inventory?
Set a tiebreaker rule in advance. Some dealerships assign by which store has the closer color match. Others alternate by store on a rolling basis. The key is deciding before the lead arrives, not in the moment. Document your tiebreaker and stick to it.
What response time should I target for a shared BDC queue?
Industry standard is first contact within 2 hours of lead arrival. Some high-volume dealerships push for 1 hour. Anything longer than 4 hours and your conversion rate drops noticeably. Pick a number that your team can hit consistently, measure it daily, and hold reps accountable.
Should I rotate BDC reps between stores or keep them assigned to one location?
If reps are assigned to a single store, they feel ownership and are less likely to let leads slip. If you rotate them, you need stronger process discipline and clearer handoff protocols. Most dealerships find that assigned reps + a shared lead database (for overflow or imbalance) works better than fully rotating reps.
How often should I review my shared queue performance?
Daily for tactical health (response times, stuck leads, queue balance). Weekly for strategic trends (staffing gaps, process breakdowns). Monthly for overall KPI review against your targets (conversion rates, appointment sets per BDC rep, cost per appointment).
What do I do if one store's leads consistently sit longer than the other?
First, find out why. Is that store understaffed? Are the leads lower-quality or harder to contact? Is the rep not following the sequence? Then adjust: add staffing, retrain the rep, temporarily route new leads to the other store, or change your assignment logic to balance effort, not just volume.
Can a shared BDC queue work across more than two stores?
Yes, but the more stores you add, the more important your checklist becomes. Three stores = three possible owners for each lead and three places for confusion to hide. Make sure your routing logic is even clearer, your escalation path is shorter, and your daily monitoring is tighter.
---