What is the difference between grading and coaching a BDC call?

A quality-assurance review checks the call against defined requirements and records the result. A coaching review uses specific moments from the call to choose a behavior to practice. Dealerships may need both; coaching should not replace required compliance, consent, disclosure, or policy checks.

How many BDC calls should a manager review?

There is no universal number. Choose a sample that fits call volume and manager capacity, then include recent calls, different lead types, exceptions, complaints, transfers, and a representative selection of ordinary conversations. Document how calls were selected so the sample is not presented as broader proof than it supports.

What should be on a BDC coaching form?

Keep the coaching section specific: the relevant call moment, what the representative did, why it mattered, one behavior to practice, and when the manager will review it again. Keep mandatory QA, consent, disclosure, and dealership-policy checks in a separate section that is not discarded for convenience.

How long should a BDC coaching session take?

Use enough time to replay the relevant moment, hear the representative's interpretation, agree on one practice action, and define a follow-up. The appropriate length depends on the call, the employee, the issue, and whether the review uncovered a policy or customer-risk concern.

A BDC Call Review Process Built for Specific Coaching

A practical BDC call-review framework that separates required QA and compliance checks from specific, behavior-focused coaching.

A BDC call-review program often tries to do several jobs at once. It checks policy, scores quality, documents manager oversight, trains the representative, and sometimes contributes to a performance review.

Those jobs should not be collapsed into one unexplained score.

A useful process separates two related activities:

Quality assurance: Did the call follow required consent, disclosure, dealership-policy, documentation, and escalation rules?
Coaching: What specific behavior should the representative practice on the next comparable conversation?

Coaching does not replace quality assurance. A short coaching note is not evidence that a required control occurred, and a high score does not tell an employee what to do differently.

Define the purpose before selecting calls

Start each review by identifying its purpose.

A compliance or policy review may need calls involving opt-outs, required disclosures, finance or credit questions, transfers, complaints, recorded-call notices, or other defined risk events. A coaching review may focus on discovery questions, careful listening, setting expectations, documenting a handoff, or handling an exception without inventing an answer.

The selection method should match the purpose. Do not claim a few recent calls represent the entire operation unless the sample was designed to support that conclusion.

A practical review set can combine:

Recent calls, so the employee can remember the context
Different lead sources and conversation types
Exceptions, escalations, and customer complaints
Transfers and appointment handoffs
A representative sample of ordinary conversations
Follow-up calls related to a prior coaching action

Document why each call entered the sample. This helps managers distinguish targeted risk review from general quality monitoring.

Preserve required QA checks

Required checks belong in a controlled QA section, not in an optional coaching conversation.

The exact checklist depends on dealership policy, communication channel, jurisdiction, vendor responsibilities, and counsel's guidance. It may include whether the representative:

Used required disclosures or identification
Honored consent and communication preferences
Avoided unsupported inventory, pricing, finance, or trade claims
Followed the approved transfer and escalation path
Documented the call and next action accurately
Protected customer information according to role and policy
Avoided changing a status without supporting evidence

A failed required check may need immediate correction, manager escalation, record remediation, or broader process review. Do not bury it inside an average score.

Use a specific coaching note

After QA requirements are handled, the coaching section can be short.

A practical note contains five fields:

Call moment: Identify the timestamp or exact exchange.
Observed behavior: Describe what the representative said or did without guessing at intent.
Customer impact: Explain what question remained unanswered, what context was missed, or why the handoff became unclear.
Practice action: Choose one behavior to rehearse on the next comparable call.
Follow-up: Define when and how the manager will review that action again.

“Needs a better opener” is too vague. “After the customer asked whether the advertised vehicle was available, verify inventory before moving to an appointment request” is specific enough to practice and review.

Let the employee interpret the call

A coaching session should not begin with the manager reading a verdict.

Replay the relevant moment and ask the representative what they heard, what they were trying to accomplish, and what information they had at the time. The answer may reveal a training issue, but it may also reveal a broken CRM field, unavailable inventory data, a conflicting script, or an escalation path that nobody owns.

That distinction matters. Coaching an employee cannot repair a system problem.

Choose one practice action

A call may contain several opportunities, but a coaching session does not need to address all of them at once.

Prioritize required policy or customer-risk issues first. For ordinary skill development, choose one behavior that is observable on a future call. Examples include:

Confirming the customer's actual question before offering a next step
Repeating appointment details and documenting how the appointment was defined
Using the customer's words rather than inferring purchase intent
Verifying inventory before discussing availability
Escalating finance, credit, legal, or dealership-policy questions to the authorized person
Creating a clear owner and due task after a transfer

Record why that action was chosen. A later reviewer should be able to understand the decision without relying on memory.

Set a cadence the manager can sustain

There is no evidence-based universal number of calls or minutes that fits every BDC.

The cadence should reflect call volume, manager capacity, employee tenure, current risks, lead mix, and the number of issues that require follow-up. A frequent short review may be useful for one team; a deeper session may be necessary after an escalation or for a new workflow.

What matters is closure. If a coaching action is assigned, the next review should check a comparable call and record whether the behavior appeared, whether the situation differed, and whether the coaching action should continue, change, or close.

Keep scoring in context

A score can help summarize defined checks, but it should not become a substitute for the underlying record.

If scores are used:

Define each item in observable language
Train reviewers on the same examples
Preserve required-item failures instead of hiding them in an average
Separate lead or customer outcome from representative behavior
Review disagreement between scorers
Link the score to the call and written evidence

Appointment or sale outcomes are influenced by inventory, source, customer intent, pricing, staffing, and many other factors. Do not attribute a conversion change to coaching without comparing equivalent records and investigating competing explanations.

Review the process itself

Managers should periodically audit whether the call-review process produces usable records.

Check whether:

Calls were selected according to the documented purpose
Required QA items were completed
Coaching notes cite specific moments
Practice actions are observable and assigned
Follow-up reviews actually occur
System problems are routed to an owner rather than mislabeled as employee failures
Reports preserve exceptions instead of averaging them away

A good review process creates a traceable path from call evidence to a manager decision and then to a follow-up. It does not promise that one form or cadence will improve every team.

Need help separating QA from coaching? Talk with Paramount Lead Solutions about reviewing your current call-review workflow and definitions.