When the Menu Meets Objections
Even a perfect menu won't close every customer on Best. They'll push back, ask questions, defer. That's where Module 03 (Objections) and Module 04 (Menus) come together. This lesson is the integration.
Use the LARR framework from Module 03 to handle objections that come up during a menu presentation — without losing the customer or caving to the lowest tier.
The Three Most Common Menu Objections
When you present a three-tier menu, here's what you'll hear most often. Each one has a specific play.
Objection 1: "Just do the Good one."
Usually budget. Sometimes skepticism about whether everything in Better/Best is really needed. Sometimes just decision fatigue — they want to be done with the call.
Right move: Respect the choice. Don't push. Document Better/Best as Declined Repair Ops. They become next-visit warm leads.
"Sounds good — we'll do the Good tier today. I'll note Better and Best on your file so we have them ready next time you're in. Want me to set up a follow-up reminder when those become more urgent? No pressure either way."
What NOT to do: Don't try to upsell back to Better. They told you their answer. Pushing destroys trust.
Objection 2: "Can I do part of Better but not all?"
Engaged customer who's actually thinking about it. They want the brakes and pads, but not the cabin filter. This is a great signal — they're not declining, they're negotiating.
Right move: Yes. Always yes. Customize the menu live and update CDK.
"Of course. Let's do that — front pads and brake fluid, skip the cabin filter for now. That brings you to about $720. I'll update the menu now and we'll get you scheduled. Make sense?"
The customer just told you exactly what they want. Give it to them.
Objection 3: "All three are more than I can do today."
Real budget constraint. Maybe their financial situation changed. Maybe an unexpected expense came up. Don't argue with it — adapt.
Right move: Acknowledge it, then drop below Good if needed. Find the safety-critical absolute minimum and make sure they leave safe.
"I hear you. Let's figure out the minimum to get you safe today. The front pads are the one thing we shouldn't put off — that's about $310 just the pads, no extras. We can schedule the rest for next month. That work?"
What NOT to do: Don't push them to "find a way" to do Good. If $480 is too much, $480 is too much. Find $310 or wherever the real minimum lands. Care about the customer, not the RO.
Other Common Objections (Apply LARR)
| Objection | Quick LARR move |
|---|---|
| "That's a lot of money." | Acknowledge → reframe with what's in the price → recommend Better as the smart-money pick |
| "I need to think about it." | Acknowledge → send the menu via CDK Engage → set a follow-up time |
| "I'll do it next time." | Acknowledge → name what waiting costs → offer phased option |
| "I need to talk to my spouse." | Acknowledge → send the menu and tech video → set a follow-up |
Module 03 covers each of these in full. Cross-reference whichever objection you're facing.
The Integration Mindset
A menu without objection-handling collapses at the first pushback. Objection-handling without a menu turns into a series of yes/no quotes that exhausts the customer. The two together — clear options + calm handling of resistance — is what produces consistent results. Don't think of them as separate; they're two halves of the same conversation.
The Hand-Off if You Can't Close
If the customer needs more time and the call has to end without a decision, the hand-off matters:
- Send the menu through CDK Engage — same options, in writing, on their phone.
- Send the tech video again if they haven't watched it.
- Set a specific follow-up time — "I'll call you tomorrow at 10."
- Document everything in SDL notes. The next advisor (or you tomorrow) shouldn't have to start over.
- Declined Repair Ops auto-create for whatever they didn't pick.
The Integration Checklist
Manager Coaching Tip
When an advisor reports "the customer just did Good," ask what objection came up first. If they can't name one, the conversation probably went too fast for the customer to engage. If they can name one and handled it well, that's a win — Good is a complete answer, not a failure. Track the next-visit conversion on those Declined Repair Ops — that's the real measure.
You Finished the Lessons
Seven lessons, one framework, one tool. Time to prove it sticks — knowledge check, then three roleplays where you'll present menus to live customer situations.