Centralized BDC for Dealer Groups: When to Centralize and How to Route by Rooftop

When a dealer group should centralize its BDC, with a worked staffing example, written routing rules by rooftop and the per-store reports GMs need.

A centralized BDC is one business development team that answers leads and calls and books appointments for every rooftop in a dealer group, instead of a separate BDC at each store. Centralizing tends to pay off when stores share systems and processes and have enough calls to pool, and tends to fail when routing rules and store reporting are vague.

At a glance

A centralized BDC can cover peak call volume for several rooftops with fewer agents on the phones than separate store BDCs, because one queue absorbs the peaks that each store would otherwise staff for alone.
Trade sources and dealer forums describe the same failure points for central BDCs: stores accusing the BDC of favoring the host store, weak local product knowledge, complex service calls bouncing back to the store, and dependence on one strong manager.
Many groups split the work by call type: the central team takes after-hours calls, overflow, outbound campaigns and first-contact sales appointments, while each rooftop keeps complex service calls and established customer relationships.
General managers accept a central BDC more readily when every result is reported by rooftop: leads received, response time, appointments set, shown and sold, and calls answered and abandoned per store.

What a centralized BDC is, and the three ways dealer groups organize BDC work

A centralized BDC is a single team, managed by one BDC director or manager, that handles inbound leads, phone calls and outbound follow-up for all of a dealer group's stores. For a general explanation of what a BDC does and how a single store staffs one, see what a car dealership BDC does. This guide is about the group-level decision.

A June 2026 article from Numa, a company that sells AI phone and messaging software to dealers, describes the three structures dealer groups choose between:

Centralized: one team, often at a corporate site or working remotely, handles calls for all rooftops and reports to a central BDC director.
Decentralized: each rooftop runs its own BDC, usually with two to five agents, managed at the store.
Hybrid: work is split between a central team and rooftop teams by call type, time of day or function.

A centralized BDC is not the same as an outsourced BDC. In a centralized model the group employs and manages the agents itself; in an outsourced model a third-party company does the work under contract. The trade-offs in this guide are about the in-house central model.

Real groups have run central BDCs at very different sizes. Auto Dealer Today reported in January 2012 (a source more than three years old) that Grappone Automotive in Bow, New Hampshire, ran one central BDC with 10 business development representatives for six franchises on four rooftops, after trying two or three reps in each store for about a year and moving back to a central team. In a December 2021 Fullpath podcast (also more than three years old), Team Automotive Group's director of digital operations described routing the phone numbers of all six of the group's North Carolina stores to one call center in a building separate from the dealerships, staffed by 21 sales BDC agents and 10 service BDC agents plus managers and team leaders.

When a centralized BDC makes sense for a dealer group

A centralized BDC makes sense when a dealer group's stores already run on shared systems and processes, sit in markets close enough to share customers, and generate enough calls and leads that one pooled team can cover peaks more efficiently than separate store teams. Use the checklist below as a self-assessment; it is a recommendation built from the sources in this guide, not a validated scoring model.

Shared CRM and scheduling. Central agents need to see every store's leads, customer history, inventory and service calendar in one place. Numa's article lists the need for standardized DMS and scheduling systems as a drawback of centralizing; if each store runs different tools, fix that first.
Common processes. Team Automotive Group's director said in the Fullpath podcast that all of its stores run on the same processes and platforms, which let the group move managers between stores and set up a new store quickly. Stores with very different sales processes are harder to serve from one team.
Overlapping markets. Grappone consolidated its BDC partly because shoppers were researching online and comparing makes across several of the group's sites, according to Auto Dealer Today. Stores that compete for the same shoppers gain the most from one team that sees all of a customer's inquiries.
Enough volume to pool. The staffing section below shows why pooling saves agent hours when each store's peak volume is small. If each rooftop already keeps a full team busy all day, the saving is smaller.
Scriptable work. First-contact sales calls, appointment confirmations and outbound campaigns follow a script well. Complex service calls, such as repair-order status or a customer with a long multi-visit history, depend on store knowledge.
A leader and a successor. A central BDC concentrates risk in one manager, as the risks section explains.

Group size is a rough guide, not a rule. Numa's article suggests decentralized BDCs usually suit groups under five rooftops, a hybrid starts to make economic sense at five to 12 rooftops, and centralizing high-volume, scriptable calls is usually justified above 12. That guidance is a vendor's opinion without published data behind it, and the Grappone and Team Automotive examples show groups of four to six rooftops running central teams. The checklist above matters more than the store count.

The same logic applies to RV, marine and powersports dealer groups, with one difference: their call volume is often more seasonal. A central team that can shift agents between stores during a boat show, an RV show or the spring riding season is one of the stronger arguments for pooling in those groups.

Risks of centralizing a BDC and how dealer groups reduce them

The main risks of a centralized BDC are store distrust, loss of local knowledge, service calls that bounce back to the store, and dependence on one manager, and each one has a known countermeasure.

Stores believe the BDC favors one rooftop

In a December 2021 DealerRefresh forum thread, a manager who ran a centralized BDC for three rooftops from one of the stores said the other stores repeatedly accused his team of mishandling their leads because of where the team sat. He recommended a neutral location and neutral lead distribution. Written routing rules (see the routing section) and per-store reporting (see the reporting section) give stores a way to check the claim instead of arguing about it.

Agents lack local product and store knowledge

In the same thread, a participant whose group centralized about half of its 50 stores said a central team only works if agents spend a day or two a month at the stores they serve, are paid well enough to stay, have good tools, and handle outbound as well as inbound work. A standard process for getting vehicle availability and fresh trade photos from each store, mentioned by another participant, closes much of the knowledge gap.

Complex service calls bounce back to the store

Numa's article says routing complex fixed operations calls to a central team typically results in escalations back to the store, and that centralizing can hurt customer satisfaction mainly in fixed operations. This is why many groups keep repair-order status calls and advisor-specific follow-up at the rooftop. For how a service BDC is set up inside a store, see how to set up a service BDC.

The BDC depends on one manager

A 2006 WardsAuto article (nearly 20 years old, so treat it as history rather than a benchmark) reported that Asbury built a centralized BDC for its Mississippi dealers that ran well for a couple of years and then fell apart after the manager who ran it left. The experts quoted recommended succession planning, processes that work without one person, and a trained successor. For what the manager role involves day to day, see what a dealership BDC manager does.

Staffing a centralized BDC: a worked pooling example

A centralized BDC usually needs fewer agents on the phones at peak than separate store BDCs, because one shared queue smooths out random bursts of calls that each small store team must staff for alone. Call centers estimate this with the Erlang C formula, which TechTarget describes as a traffic model that estimates caller waiting times from call volume, handling time and the number of agents.

The example below uses invented numbers to show the method. They are not benchmarks; replace them with each store's own call counts from the phone system.

Group: four rooftops.
Peak-hour inbound calls: 12 per store, 48 for the group.
Average handle time: 4 minutes per call, including after-call notes in the CRM.
Answer target: 90% of calls answered within 30 seconds.

Erlang C results for this example, calculated for this guide:

Separate store BDCs: each store needs 3 agents on the phones at peak to reach the target (about 96% answered within 30 seconds), so the group needs 12 agents across four stores.
One central BDC: the pooled queue of 48 calls an hour needs 6 agents on the phones to reach the target (about 91% answered within 30 seconds).

Agents on the phones are not the same as agents on the schedule. Breaks, training and meetings take time away from calls; this is called shrinkage. A 2023 guide published by Call Centre Helper uses 30% shrinkage in its example and calls that figure the industry average without citing a source. At 30%, the example becomes about 17 scheduled agents for separate stores and about 9 for the central team during the peak hour. Use your own shrinkage figure once you have a few weeks of schedule data.

Three limits apply to this method:

Erlang C assumes callers never hang up while waiting and that calls arrive independently, and TechTarget notes the results are usually acceptable only when callers outnumber agents by about 10 to 1. Small store queues fall short of that, so treat store-level results as rough estimates.
Erlang C covers live calls only. Texts, emails, web leads and outbound campaigns need separate workload estimates, and quiet-period capacity in a store BDC is often spent on that outbound work rather than wasted. The Call Centre Helper guide makes the same point: small teams often cover other channels during quiet periods.
The saving appears only if central agents can actually take any store's call: same CRM, same scheduling access and enough knowledge of each store.

An older rule of thumb for outbound and lead workload comes from the same 2006 WardsAuto article, which quoted Rick Case's "sweet spot" of 200 to 250 opportunities per rep per month. That figure is nearly 20 years old and comes from one dealer, so use it only as a starting point to compare with your own data.

Routing by rooftop: the rules a centralized BDC needs in writing

A centralized BDC needs written routing and ownership rules that say which store owns each lead, which work the central team handles, and how a customer is handed to a store, because unwritten rules are what stores argue about. The rules below are a template; each group fills in its own choices. For how leads are split among people inside one store, see lead distribution at dealerships.

Which store owns a lead?

Inventory inquiry: the store that holds the vehicle the shopper asked about.
General or brand inquiry: the store that sells that brand nearest to the customer's address, or the store whose website or phone number the shopper used. Pick one rule and apply it to every store.
Existing customer: the store that sold the customer's current vehicle or last serviced it, for a set number of months.
Shopper who contacts several stores: one record and one agent. Grappone's BDC kept each customer with one representative regardless of brand until a sales manager handed the customer to a salesperson, according to Auto Dealer Today.
Vehicle at another store: the store that will deliver the vehicle, with the transfer decision made by the sales managers, not the agent.

Which work goes to the central team and which stays at the rooftop?

Numa's article describes a hybrid split that many groups use as a starting point:

Central team: after-hours inbound calls, high-volume outbound campaigns (recall, declined service and lapsed customer follow-up), overflow during peak hours, and first-contact sales appointment setting.
Rooftop: complex inbound service calls (repair-order status, escalations, multi-visit history), follow-up where a customer has an established relationship with an advisor, and same-day schedule changes that need real-time coordination with the shop.

How is a customer handed to a store?

Every appointment is booked into the receiving store's calendar, with an owner named at the store before the customer arrives.
The agent's notes, messages and call history stay on the customer record, so the store does not repeat questions.
A missed handoff (no store owner, or no contact within a set time) goes back to the central team and is counted in that store's report.

Shiftix Cloud's CRM lists condition-based routing by source, vehicle type, location or round-robin, and tracking of the assigned rep, department, location and ownership changes. Its Unified Customer Inbox lists conversation assignment and reassignment, team and role-based access, and department handoffs that keep the earlier exchange on the customer record. If you want an outside view of where leads and calls are slipping between your stores, the Revenue Leak Audit is a complimentary, no-obligation review of lead response, follow-up, conversion, customer retention, accountability and workflow, and Shiftix walks through the findings with you.

Per-store reporting that keeps general managers on board

General managers support a centralized BDC when they can see, every week, exactly what the central team did for their store, so every BDC number should be reported by rooftop as well as for the group. The scorecard below is a recommended starting set:

Leads received by store and by source.
First response time by store, measured the same way for every store. See how to measure dealership lead response time.
Calls answered and abandoned per store phone number, including after-hours calls.
Appointments set, shown and sold by store. The show rate is where handoff problems appear first; see dealership appointment show rate.
Service appointments booked by store, separated into inbound and outbound campaigns.
Escalations and missed handoffs by store, with the reason.
Cost per appointment shown by store, once the BDC cost is allocated.

Allocating the BDC's cost is part of reporting, and any method works if every store agrees to it in advance. Common choices are splitting the cost by each store's share of leads handled, by share of appointments shown, or by a fixed share agreed at budget time. Allocating by appointments shown ties each store's cost to what it received, which tends to reduce arguments; allocating by leads is simpler to count. The choice is a management decision, not a rule.

Recorded calls make store disputes easier to settle, because a manager can listen to what was actually said. Before recording, check the consent rules in each state the group operates in; see call recording laws for dealerships. Shiftix Cloud's Signal Call Intelligence lists coaching recommendations based on activity and conversation evidence, and performance trends for response, conversion and activity over time.

How to roll out a centralized BDC in phases

The safest way to centralize a BDC is one call type at a time, starting with work the stores are not doing well today, so the central team proves itself before it takes anything the stores value. Numa's article also recommends starting with a single call type. A suggested sequence:

Before launch: put every store on the same CRM setup, write the routing rules above, agree the cost allocation and build the per-store scorecard. Measure each store's current response time, answer rate and show rate so there is a baseline.
First phase: after-hours and overflow. The central team answers calls and leads the stores miss. This adds coverage without taking work away, which makes it easier for general managers to accept.
Second phase: outbound campaigns. Service reminders, declined service, recall and aged lead follow-up move to the central team, with results reported by store.
Third phase: first-contact sales leads. New internet leads and sales calls route to the central team during business hours, with appointments handed to the stores under the written rules.
Review after each phase: compare the per-store scorecard with the baseline before moving on. If a store's show rate or answer rate falls, fix the handoff before adding the next call type.

After-hours coverage can also include AI help. Shiftix Cloud's Aria AI Assistant lists configured after-hours conversation support and SMS and email drafts that a team member reviews and approves before sending, so the central team stays in control of what customers receive.

Next steps

The decision comes down to three questions, answered store by store:

Do all stores share one CRM, scheduling access and process? If not, standardize first; a central team cannot work across tools it cannot see.
Is peak volume per store small and uneven? If yes, run the pooling calculation above with real call counts. A large gap between separate and pooled staffing favors centralizing at least after-hours and overflow calls.
Which calls need store knowledge? Keep those at the rooftop and centralize the scriptable work, which is the hybrid model most groups can start with.

Related reading: what a BDC representative does for agent duties and targets, and call tracking for dealerships for tying each store's calls to their sources.

Frequently asked questions

Where should a centralized BDC be located?

A centralized BDC is often best placed away from any single store. A manager who ran a central BDC from inside one of three rooftops said on DealerRefresh that the other stores kept suspecting favoritism, and recommended a neutral site. Team Automotive Group used a separate building. A neutral site costs more, so groups that cannot afford one rely more heavily on written routing rules and per-store reports.

Does a centralized BDC hurt CSI scores?

A centralized BDC can lower satisfaction scores, mainly in service, if complex calls are sent to agents who cannot answer them. Numa's article names fixed operations as the area most at risk. Keeping repair-order status and advisor relationships at the rooftop, and measuring escalations by store, limits that risk. Sales appointment setting and outbound reminders carry less risk because they follow a script.

Can a dealer group with only two or three stores centralize its BDC?

A small dealer group can centralize, but the staffing saving is smaller and a hybrid is often enough. Grappone ran one BDC for four rooftops, and a DealerRefresh member described running one for three. A two-store group often gets most of the benefit by sharing after-hours and overflow coverage while each store keeps its own daytime team.

What should agents in a centralized BDC be called when they phone customers?

Some groups use a customer care title instead of a sales one. A DealerRefresh participant said his group renamed its BDC the Customer Care Centre, and another said calls introduced by a customer care manager got a warmer response than calls from an internet sales manager. That is anecdotal, so test the wording against your own appointment and show rates.