The First 30 Days as a BDC Manager: A Practical Plan
A practical first-30-day plan for new dealership BDC managers, including what to review, what to defer, and how to build a 30-60-90 framework.
Use the first 30 days to establish a baseline
A new BDC manager often starts with access to the CRM and dialer, inherited process documents, and a team with established habits. The quality of that handoff varies by dealership.
The first month can be used to learn the CRM, listen to calls, observe handoffs, and understand urgent problems. A new manager also has a practical reason to ask basic questions before inherited assumptions become part of a new plan.
What the first 30 days are actually for
The phased sequence below is an adaptable example, not a universal schedule. A manager should change the sample size, meeting length, sequence, and review dates based on dealership volume, staffing, access, urgent risks, and the evidence available.
This framework uses the opening period for three activities in a suggested sequence:
- Understanding what is actually happening on the floor, in the calls, and in the metrics.
- Building trust with the BDC team and with the GM.
- Identifying a manageable set of candidate changes, with the team's input, for controlled review.
Those three steps provide the evidence needed to draft the next part of a 90-day plan. Changes made before that review should be limited to urgent customer, safety, compliance, or access problems.
Phase one: listen before broad changes
The temptation at the beginning is to act. The new manager may see a script with errors, a CRM workflow missing a step, or a metrics dashboard nobody uses. The instinct is to fix them immediately.
Resist it. The opening phase is for listening. An example review may include:
A representative call sample. Select enough recent calls to cover relevant lead sources, agents, routine work, and exceptions. Document how the sample was chosen and take notes after each call. The goal is not to treat a small sample as a performance score. It is to identify questions that deserve review against more evidence.
A focused review with the GM. Walk through recent lead-source data, appointment definitions, show and sale outcomes, staffing, and current priorities. Agree on which systems are authoritative and which urgent issues may require action before the wider baseline review is complete.
A structured conversation with each BDC agent. This is not a performance review. Ask what is working, what gets in the way, and which process deserves investigation. Agents hear direct customer interactions and may identify context that an aggregate dashboard does not show.
A handoff observation. Observe a useful sample of BDC-to-showroom transitions. Record what context reached the receiving owner, where the source record lives, and whether the next action reconciled with the CRM outcome.
At the end of the opening review, the manager should have written observations, source links, and questions. That record is a baseline input, not proof that a pattern applies to the entire operation.
Phase two: test limited fixes
The next phase can address a small number of clearly explained fixes rather than a broad restructure.
Candidate fixes might include a CRM tag that does not fire, a call-recording workflow that breaks after an ownership change, a handoff email using the wrong address, or an escalation script missing an approved path. Each example still needs source-record confirmation before it becomes a change request.
Limit concurrent changes so each one has a named owner, baseline, expected evidence, review period, and rollback or adjustment path. The appropriate number and review period depend on the risk and available volume.
Explain why each change was selected and what evidence will be reviewed. This gives the team a visible decision process without promising that one release pattern will produce a particular management or performance outcome.
Phase three: add the team's evidence
After the initial review, bring the observed evidence and unresolved questions to the BDC team.
Run a structured conversation with the full BDC team. The length should fit team size and the issues being reviewed. Three useful questions are:
- What is working that we should not break?
- What is broken that we have not fixed?
- What is missing that you wish we had?
Write the answers where participants can see them and group related observations. Preserve disagreements and link proposed themes back to source records before turning them into an agenda.
The conversation adds employee context to call samples and management reports. It does not prove that a proposed interpretation or change is correct.
Phase four: draft and review the longer plan
After the initial listening, source review, and limited changes, the manager may have enough context to draft a longer plan. One adaptable structure has three parts.
Initial review. Listening, baseline evidence, urgent fixes, and team input. The plan documents what was observed, what changed, and what remains uncertain.
Controlled structural work. Select a manageable set of changes from dealership evidence. Each one has a defined measure, owner, review period, and exception path.
Broader changes. A script rewrite, CRM workflow rebuild, dashboard replacement, or handoff redesign may follow when the dealership has enough evidence, authority, capacity, and rollback planning.
Put the plan in writing, share its assumptions with the GM and affected team, and define review checkpoints that match the dealership's operating cycle. Revise the sequence when source data, staffing, risk, or priorities change.
Management-transition risks to review
Three risks deserve attention during a manager transition.
Changing too much, too fast. Changing several systems at once makes it difficult to attribute an effect or explain which process now controls the work. The safer approach is to limit each release, define the expected evidence, and review the result before adding another change.
Skipping the listening. A manager may arrive with strong opinions from a previous role and apply them before understanding the current dealership. The fix is to listen before deciding and explain which local evidence supports each proposed change.
Optimizing the dashboard before validating definitions. New reports can consume time while preserving inconsistent appointment, contact, or outcome definitions. Review source records and reconcile the underlying terms before treating a dashboard redesign as the priority.
A note for the GM who hired the new manager
If you are the GM who just hired a BDC manager, agree on the manager's decision boundaries, access, urgent responsibilities, and review points.
Introduce the manager's role to the team and explain which decisions the manager owns, which require approval, and how concerns or exceptions should be raised.
Then provide room to listen, establish ownership, and identify the right changes. Agree on decision boundaries and review points instead of demanding an unsupported quick win in the first month.
The first month should prioritize a reliable baseline and a manageable plan for the work that follows.
Where to go from here
If you are walking into a new BDC manager role, draft the questions, access needs, and evidence you expect to review. Treat that draft as a hypothesis and change it when the dealership's actual records or risks require a different sequence.
The plan is not the work. It is a record of assumptions, owners, evidence, review points, and unresolved questions that supports the work.
If you are a GM working with a new BDC manager, give the manager room to listen, document the baseline, and make a small number of controlled changes. Larger changes should follow once the dealership has defined the problem, owner, evidence, and review period.
If you want help thinking through the first 30 days at your store, or the 90-day plan that follows, book a quick call and we will walk through it together.