Watch before reading. This video walks you through the core concepts for this module.
Video coming soon
What separates a system from a suggestion
The difference between a shop that runs callbacks consistently and one that runs them for two weeks is not motivation. It's measurement.
When you measure something, it improves. When you stop measuring it, it quietly disappears — and usually nobody notices until a month has gone by and the call log is empty.
This module gives you the metrics that matter, the reporting cadence that keeps the system alive, and the ability to read the data — to know when things are working and, more importantly, to catch the warning signs before the system falls apart.
🎯
Facilitator — open with this
"Without looking at any data — right now, today — tell me: how many callback calls went out from your shop last week?" If nobody can answer, that's the whole opening. Write the three questions on the board: How many calls? How many appointments? How many showed and what was the revenue? "If you can't answer all three, you don't have a system yet. By the end of this module, you will."
Why this module matters more than it seems
Metrics is usually the module people are least excited about going in and most grateful for coming out. It is not as energizing as the formula or as immediately practical as the script library. But it is the module that tells you whether everything else is actually working.
Here is the honest reason most BDC programs quietly die: nobody is watching the numbers. Calls go out, some appointments get booked, some customers show up. The system just kind of runs, or kind of does not. Because nobody is measuring anything specifically, nobody notices when things start to slip until they have already slipped badly.
Before you read Lesson 7.1, write down what you currently track from your callbacks — a specific number and how often you look at it. Not "we track results." What number. That answer tells you exactly where you are starting from.
Lesson 7.1System vs. Hope — What the Numbers Tell You8 min
Two shops. Same training. Six months later — very different outcomes. Here's how you tell which one you are from the numbers alone.
❌ You have a hope — these are the signs
✗Can't answer "how many calls went out this week" without digging
✗Call volume varies wildly week to week — high one week, zero the next
✗Appointments are tracked in someone's head, not the DMS
✗No way to connect callback revenue to specific calls
✗The system "paused" during a busy stretch and never restarted
✓ You have a system — these are the signs
✓Weekly call count is available in under 60 seconds
✓Call volume is consistent — busy weeks and slow weeks look similar
✓Every appointment is logged with source: callback type and script used
✓Callback-sourced revenue is tracked as its own line item
✓The system ran during your last three busy weeks without dropping
Lesson 7.2The Six KPIs That Matter12 min
There are six numbers to track. Not twenty. Not a dashboard with forty metrics. Six numbers that, read together, tell you everything about whether the system is working — and where it's breaking down when it isn't.
KPI 01
Calls Made
Daily total, by tier
Target: 15–25/day normal · 40+ slow day
The baseline. Everything else depends on calls going out. Low call volume is always the first sign the system is slipping.
KPI 02
Contact Rate
Contacts ÷ Calls Made
Benchmark: 40–60%
Measures list quality and time-of-day targeting. Low contact rate = wrong time, wrong list, or bad phone data in the DMS.
KPI 03
Appointment Set Rate
Appointments ÷ Contacts
Benchmark: 25–35%
The skills metric. This is where formula and objection handling show up in the numbers. Consistently below 25% = coaching needed.
KPI 04
Show Rate
Showed ÷ Appointments Set
Benchmark: 70–85%
Measures close quality. Low show rate = appointments being set without full confirmation (Step 4 of the five-step close being skipped).
KPI 05
Revenue per Callback Visit
Total callback revenue ÷ Showed appointments
Track against shop average RO
Callback visits should run close to or above the shop average RO. If they're significantly lower, the Opportunity step needs work.
KPI 06
Missed Sale Recovery Rate
Recovered ÷ Missed sale callbacks made
Benchmark: 35–50%
The highest-value metric in the system. Tracks the revenue specifically recovered from declined services. This is your ROI number.
📊
How to read the six together
The KPIs diagnose each other. Low appointment set rate with normal contact rate = skills issue (Modules 3–5). Low contact rate with normal call volume = list quality or timing issue (Module 6). Low show rate = confirmation not happening at the close. Low missed sale recovery = Connection step being rushed or objection handling breaking down. Each KPI points to a specific part of the system.
Your numbers vs. the benchmarks
You just read the six KPI benchmarks. Before you move to the revenue calculator, do an honest estimate for your shop right now — not where you want to be, where you actually are. Pick any two of the six KPIs and write your current realistic number next to each benchmark.
If you do not know your number, write that down instead. A metric you are not tracking is a gap in your system, not just a data problem. Note what it would take to find out.
Lesson 7.3What a Working System Is Worth10 min + calculator
You've seen the missed-sale calculator in Module 2. This one goes further — it models the full value of a running callback system across all six KPIs, using your shop's real numbers.
Full System Revenue Calculator
All five callback types contributing to total monthly value
Live
Daily calls made 20
Contact rate 50%
Appointment set rate 28%
Show rate 75%
Average revenue per callback visit $320
Working days per month 22
Calls / month440
Contacts made220
Appointments set62
Appointments showed46
Monthly callback revenue$14,720
Annual system value$176,640
Your annual system value: $176,640 — this is revenue generated by the callback system on top of everything else the shop does.
💰
After the calculator
Ask: "What does this number look like if the contact rate drops from 50% to 30% because the call list isn't being pulled correctly?" Set the slider to 30% and let the room watch the annual number change. That's the financial cost of a sloppy DMS pull. Numbers make the operational discipline argument better than words do.
Lesson 7.4Reading the Warning Signs8 min
The system doesn't fall apart dramatically. It slips quietly — one metric drifts, nobody notices, and three weeks later you're back to making callbacks only when someone remembers. Here are the signals to watch for before that happens.
⚠️
Call volume drops below minimum
Two consecutive days under the daily minimum target. Almost always means the DMS pull is being skipped or compressed. Check the log timestamps.
Action: Verify DMS pull happened. Identify what displaced it.
🔴
Appointment set rate drops below 20%
Not a bad week — a pattern. Below 20% consistently means Connection is being rushed or objection handling is breaking down. Pull call recordings.
Action: Listen to 5 calls. Identify at which step the call is losing.
⚠️
Show rate drops below 65%
Appointments being set without full confirmation. The five-step close (Step 4 — confirm and capture) is being skipped or done weakly.
Action: Audit close quality. Add confirmation reminder call 24 hrs before appointment.
🔴
Call log gaps — days with no entry
Any day with zero call log entries is a system failure, not a capacity issue. If it happened once, it can become a pattern within a week.
Action: Identify what happened. Rebuild the ownership assignment. Don't let it go unaddressed.
⚠️
Tier distribution skews toward Tier 3 & 4
If most calls are oil change reminders and relationship calls, but Tier 1 and 2 (satisfaction and missed sales) are thin — the specialist is doing comfortable calls first.
The highest-value call in the system is underperforming. Either the list isn't being worked or Connection is being skipped entirely on declined service callbacks.
Action: Hot seat drill on Scripts 04–06. Specifically focus on Connection.
Lesson 7.5The Weekly Review — Five Minutes Every Friday8 min
The weekly review is not a meeting. It's five minutes every Friday afternoon — the system owner fills in six numbers, checks them against benchmarks, and flags anything that drifted. That's it. If it takes longer than five minutes, the data isn't in the right place yet.
Weekly Review Template — Week of: ______________
5 min · Every Friday
Metric
This week
Benchmark
Status
Calls made
75–125 / week
—
Contact rate
40–60%
—
Appointment set rate
25–35%
—
Show rate
70–85%
—
Callback revenue
Track vs. prior week
—
Missed sale recovery
35–50%
—
Before the final assessment
You have covered all seven modules — the mindset, the five types, the formula, the scripts, objection handling, daily operations, and the numbers that tell you it is working.
Here is the question worth sitting with before the final knowledge check: what is the one thing from this course that you are most likely to actually implement in the next 30 days? Not the most interesting thing. Not the most compelling concept. The thing you will actually do, specifically, starting this week.
Write that down in the workbook before you start the assessment. The knowledge check is about what you know. That question is about what you will do. Both matter — but only one changes your shop.
Module 7Final Knowledge CheckCourse completion
10 Questions
Your answers save automatically as you type
0 of 10 questions answered
1. Name the three questions that separate a system from a hope — and explain why all three must be answerable at the end of every week.
2. Name all six KPIs and state the benchmark for each. Which KPI is the hardest to improve — and which module's content does it connect to?
3. If your appointment set rate drops below 20% for two weeks in a row, what does that tell you — and what's the first thing you do?
4. If your show rate drops below 65%, which specific step of the five-step close is most likely being skipped?
5. Using the revenue calculator — what is your shop's annual system value at your real call target and realistic conversion rates?
6. What is the weekly review — how long does it take, who runs it, and what happens when a metric is flagged?
7. Name three slippage signals and explain what each one means about where the system is breaking down.
8. In your own words: what is the difference between a shop that does callbacks and a shop that runs a callback system?
Answer at least 80% of questions to unlock completion
Course close — BDC Mastery: The Callback System
"This is simple. Not easy — but simple."
You've covered everything. The mindset that makes this feel like service instead of sales. The five callback types and what each one is designed to do. The formula that works on every call, every time. The scripts, the objections, the close. The daily system that makes it happen when you're busy and when you're slow. And now the numbers that tell you whether it's actually working.
None of this is complicated. What it requires is consistency — showing up for it every day, in every call, even when the shop is slammed and callbacks feel like one more thing to do.
The shops that win are the ones that make this non-optional. Not because someone told them to — but because they understand what it produces.
📞
Stay consistent — calls go out whether it's busy or slow, whether someone remembers or not
🎯
Stay proactive — reach out before customers drift, before problems grow, before the relationship goes quiet
👥
Stay in front of the customer — you think about their vehicle so they don't have to
Callbacks aren't extra work. They're the work that drives everything else. The next-day call that saves a relationship before it becomes a bad review. The missed-sale follow-up that turns a declined estimate into a $400 repair order. The maintenance reminder that books three appointments before the week starts.