Which KPIs Matter for Managing a Shared BDC Queue Across Stores? A BDC Manager's Guide

Track lead volume per store, answer speed, contact rate, appointment-setting rate, and cost-per-appointment to manage a shared BDC queue across multiple locations. These five core metrics reveal whether your queue is fairly distributed, whether leads are dying in the system, and whether you're getting a return on your investment. Without them, you're flying blind—and chances are one store is absorbing all the outbound work while another coasts.

Why most multi-store BDC queues fail

A shared BDC queue sounds efficient on paper. One team handles inbound and outbound for three, four, or five stores. You save on overhead, you flatten the organizational chart, and theoretically everyone's busy all the time. In practice, it's a disaster—unless you're measuring the right things.

The problem isn't the model. It's that without clear KPIs, the queue drifts. One store's sales manager starts complaining. Their store gets prioritized. Another location's leads sit cold for hours. CSI tanks. Appointments drop. You hire more BDC staff to fix it, but you still don't know what broke.

A BDC manager with no metrics is like a service advisor reading MPIs blind,just guessing.

The stores that actually make shared queues work treat them like a real operation: they measure, they monitor, and they adjust. The ones that don't usually fold the queue back into individual stores within 18 months, and everyone's worse off for it.

What is lead volume per store and why it matters

Lead volume per store tells you how many inbound and outbound leads each location is responsible for in a given day or week. Straightforward metric. Huge blind spot in most multi-store operations.

Here's what happens without tracking it: Store A (your high-traffic location) sends 45 leads into the queue. Store B sends 22. Store C sends 18. The BDC team works Store A leads because they're drowning in volume, and Stores B and C feel abandoned. Their sales managers complain. The BDC manager pulls a person to work Store B and C leads manually. Now Store A's leads back up. You've created a resource war, not a system.

What you need to track:

Total inbound leads per store per day (phone, web form, chat, text, social)
Total outbound dials the queue assigns to each store per day
The ratio of inbound to outbound work (some stores need more outbound follow-up than others)
Whether the queue is distributing work fairly or clustering on one or two locations

A typical multi-store setup might look like: 35 inbound leads daily across three stores, plus 80 outbound follow-ups on aged inventory or past visitors. The BDC queue should show you where every one of those leads goes,and which store's work is piling up.

If Store A is consistently getting 60% of the queue while only generating 40% of the leads, something's wrong. Either Store A's leads are higher quality (and worth the bias), or your queue logic is broken.

Answer speed: the first metric customers notice

Answer speed is how fast your BDC team picks up inbound calls and responds to inbound messages. This is not optional. This is not a "nice to have."

A customer calls your dealership at 10:47 a.m. on a Tuesday morning. They want to know about the 2022 Civic in your inventory. If your BDC answers in 30 seconds, they feel valued. If they hear four rings and then a voicemail greeting, they're already looking at the competitor three miles away.

Industry standard: 80% of inbound calls answered within 30 seconds. Some stores push for 40 seconds. A few (the really sharp ones) track answer speed by store and by time of day, because lunch hours and end-of-shift are different pressure points.

What to measure:

Average answer time (in seconds) across the shared queue
Answer speed by store (because Store A might be getting faster answers than Store C)
Answer speed by time of day (do you have enough bodies at 4 p.m.?)
Abandonment rate (what % of calls hang up before anyone picks up)

If your shared BDC queue has a 45-second average answer time, you need more staff or better call distribution. Full stop. A 45-second wait feels like an eternity to someone shopping for a car.

Contact rate: are you actually reaching people

Contact rate is the percentage of outbound dials that result in a real conversation with a decision-maker. A lot of dealerships ignore this metric. They just count dials and calls made and assume the rest is noise. That's wrong.

Say your BDC team makes 200 outbound calls per day. If contact rate is 15%, you're reaching 30 people. If contact rate is 35%, you're reaching 70. Same effort. Wildly different results.

Why does contact rate matter in a shared queue? Because it tells you whether your BDC reps are actually trained, whether your timing is right, and whether your script is working,or whether you're just throwing labor at the wall.

Factors that tank contact rate:

Calling old leads (a 90-day-old web form has a much lower contact rate than a 3-day-old one)
Calling at bad times (calling a busy manager at 8:30 a.m. gets you voicemail)
Bad phone numbers or incomplete customer data
BDC reps who don't know how to talk past gatekeepers
Leads sitting in the queue too long before anyone dials them

A healthy multi-store BDC queue should maintain a contact rate between 25% and 40%. If you're below 20%, something's broken,and you should know it.

Appointment-setting rate: the one metric that directly impacts sales

Appointment-setting rate is the percentage of contacts (not dials,contacts) that result in a scheduled appointment. This is the closest thing a BDC team has to a revenue metric.

If your BDC reps are reaching 60 people per day and scheduling 12 appointments, your appointment-setting rate is 20%. That's decent. If they're reaching 60 people and scheduling 3 appointments, your rate is 5%, and your BDC team is wasting everyone's time.

What's a good appointment-setting rate? Industry average is 12% to 18% for outbound. Top-performing queues hit 20% to 25%. If you're tracking this and you're below 10%, your BDC reps need retraining, your leads are bad, or both.

Why does this matter for a shared queue specifically? Because it's the one metric that holds individual BDC reps and stores accountable. If Store A's appointment-setting rate is 8% and Store B's is 22%, you've got a training gap, not a queue problem.

Track:

Appointment-setting rate by BDC rep (who's converting)
Appointment-setting rate by store (Store A leads vs. Store B leads)
Appointment-setting rate by lead source (web form vs. phone vs. social)
Show rate on those scheduled appointments (if they schedule 12 but only 6 show up, that's a separate problem)

Cost per appointment: the one metric most BDC managers avoid

Cost per appointment is your BDC salary budget divided by the number of appointments your queue sets per month. A lot of BDC managers hate this metric because it feels like you're reducing their team to a math problem. But it's honest, and honest is what you need when you're running a shared queue.

Let's say your shared BDC queue costs $180,000 per year (salaries, benefits, systems, phone lines). You set 900 appointments per month. That's $200 per appointment.

Is $200 good? Depends. If those 900 appointments convert to 180 sales per month (20% show-and-close), that's $1,000 per sale,highly profitable. But if your show-and-close is 5%, you're spending $4,000 per sale, and the BDC queue might not be worth the overhead.

This is the one metric that will tell you whether a shared queue actually makes financial sense or whether you should split it back into individual store operations.

How to calculate it fairly across stores:

Add all payroll, benefits, software, and phone costs for the shared BDC queue
Divide by total appointments set per month
Compare to your cost per appointment for any single-store BDC operation you can benchmark against
Factor in whether the queue is saving you money on overhead (fewer managers, one system license, one phone system)

If cost per appointment is trending up while appointment-setting rate stays flat, you're running in circles. Hire better, train harder, or restructure the queue.

Secondary KPIs that matter more than you think

The five core metrics above will get you 80% of the way there. But a few secondary metrics are worth watching if you're managing a sophisticated operation.

Lead age at first contact: How many hours or days pass before a BDC rep dials a fresh lead? A lead contacted within 1 hour is five times more likely to convert than a lead contacted after 24 hours. If your shared queue is sitting on fresh leads for 4+ hours, something's wrong with your staffing or call distribution.

Talk time and script adherence: Are your BDC reps rushing through calls (sub-2-minute talks) or spending real time with customers? For a shared queue, this matters because it tells you whether the team is trained consistently or whether different stores are running different playbooks.

Text and email response time: Younger customers don't want to call. They want to text or email. If your shared BDC queue is answering emails in 8+ hours, you're losing deals. Track response time for every channel.

Callback vs. immediate contact: Some calls go to voicemail and the BDC rep leaves a callback request. That's fine. But if your callback conversion rate is below 5%, your voicemail game is weak. This kind of workflow is exactly what a solid DMS and communication platform (like Dealer1 Solutions) can help you standardize across stores,so Store A and Store C aren't using different voicemail templates.

How to set up KPI dashboards for a shared queue

Metrics are useless if nobody's looking at them. You need a dashboard,something your BDC manager and your store managers can check every morning.

A good shared-queue dashboard shows:

Today's lead volume (inbound and outbound) by store, updated in real time
Current answer speed and abandonment rate
Yesterday's contact rate, appointment-setting rate, and cost per appointment
This week vs. last week (trend)
Individual BDC rep performance (so poor performers don't hide in the crowd)
Red flags: leads sitting longer than 2 hours, answer speed above 40 seconds, contact rate below 20%

Your DMS should be feeding this data automatically. If you're pulling reports manually or asking your BDC manager to build spreadsheets, you're wasting time and introducing error.

A pattern we see across top-performing dealerships is a brief morning huddle,5 minutes,where the BDC manager walks the team through yesterday's metrics. "Answer speed was slow yesterday from 3 to 5 p.m. Who's covering the desk then? Let's adjust." That simple discipline compounds.

Frequently asked questions

What contact rate should I expect from a shared BDC queue on aged leads?

Aged leads (30+ days old) typically run 10-15% contact rate because many customers have already bought or lost interest. Fresh leads (under 48 hours) should hit 30-40%. If you're seeing poor contact rates even on fresh leads, your team needs retraining or your phone numbers need validation. A mix of fresh and aged work is normal; just track them separately so you know what's realistic.

Should I measure appointment-setting rate differently for inbound vs. outbound?

Yes. Inbound appointment-setting rates are typically higher (25-35%) because the customer called you. Outbound rates are lower (12-20%) because you're calling them. Don't mix them in one metric,track both separately. That way you know whether your inbound process is broken or whether your outbound dialing is the weak link.

How often should a shared BDC manager review these KPIs?

Daily for answer speed and lead volume (these tell you if something broke today). Weekly for contact rate, appointment-setting rate, and cost per appointment (these show trends). Monthly for a deep dive: compare this month to last month, compare stores to each other, and adjust staffing or training. If you're only reviewing KPIs monthly, you're fixing problems too late.

Can I use these KPIs to hold individual store managers accountable?

Partially. Lead volume and appointment-setting rate by store are fair. But be careful,if Store A has lower-quality leads than Store B, Store A's appointment-setting rate will naturally be lower. Use KPIs to start conversations ("Why is Store A's contact rate dropping?"), not to blame. The BDC queue is a shared resource, so shared accountability matters.

What happens if my shared queue's cost per appointment is higher than a single-store BDC?

The shared model only makes sense if the total cost is lower or the quality is significantly higher. If cost per appointment is creeping up, look first at appointment-setting rate,are your reps converting less? Then look at volume,are you setting fewer total appointments? Either way, you need to fix something, or the shared queue experiment isn't working financially.

Should I track KPIs differently if one store has much higher volume than others?

Yes. A store with 3x the lead volume will naturally set more appointments in absolute numbers, but its per-rep metrics should be similar. Track volume-adjusted metrics: appointments per BDC rep hour worked, contact rate (which is already volume-adjusted), and cost per appointment (which spreads costs fairly). Don't penalize Store A for being busier.

Moving from guessing to measuring

A shared BDC queue is only as good as your commitment to measuring it. Without KPIs, you're running on emotion,one store complains, you react. A rep struggles, you don't see it. A lead dies in the system, nobody notices.

With the five core metrics,lead volume per store, answer speed, contact rate, appointment-setting rate, and cost per appointment,you can see what's actually happening. You can spot unfair load distribution. You can identify training gaps. You can decide whether the shared model is worth it financially.

Start with those five. Get them into a dashboard. Review them daily. Make one small adjustment per week based on what the numbers tell you. Within three months, you'll have a different operation.