The 90-day rule
Ninety days after a customer says "not today," call them back. That's the rule. One line, and most shops still don't run it.
Picture it on the floor. Tech pulls a car in for an oil change, flags the rear brakes at 3mm and a serpentine belt that's cracking. Advisor quotes it. Customer says the brakes can wait, they'll do the belt "next time." Belt and brakes go on the RO as declined lines. Car leaves. And that's where most shops stop.
The declined line doesn't disappear. The brakes are still at 3mm. The customer didn't decide the work was wrong. They decided this week was wrong. Payday was tight, or they had a trip, or they just didn't want to think about $600 on a Tuesday. Ninety days later, most of those reasons are gone.
Why deferred work is money you already earned
You already did the hard part. The car was on your lift. Your tech found the problem, measured it, and wrote it up. The customer already trusts your read on their vehicle, or they wouldn't have brought it to you. Every declined line is a quote you don't have to generate and a customer you don't have to buy.
Compare that to a new customer. To get a first-timer in the door you're paying for Google Ads, or a mailer, or you're grinding for reviews. A declined line costs you one text.
Run the arithmetic. Say you flag eight declined jobs a week and the average declined line is worth $350. That's roughly $12,000 of identified, quoted work sitting in your system every month. You won't recover all of it. Nobody does. But if a callback rule turns even one in five into an approved job, that's real money off work you'd already written up. That's arithmetic, not a promise.
Why 90 days, not 30, not a year
Thirty days is too soon. The customer just told you no. The reason they said no, usually money, hasn't changed yet, and following up two weeks later reads as pressure.
A year is too late. The recommendation is stale, the customer has forgotten the conversation, and you should have caught them before thin pads turned into scored rotors.
Ninety days sits in the middle. It's a full paycheck cycle past the "no." A tax refund has come or gone. The noise they've been ignoring got a little louder. And the recommendation is still current, so you're not re-diagnosing, you're reminding. Late enough to feel like service, early enough to still be true.
How to run it off the RO
You don't need a new system to start. You need a list and a Monday.
The declined lines already live on your repair orders. Every shop management system captures them, even if you've never gone looking. The job is to get last quarter's declines in front of a human once a week.
A cadence that works: every Monday morning, pull the ROs from about 90 days back. Ryan does ours before the first car's on the lift, coffee in hand. Read the declined lines. Skip the tire-rotation-type stuff nobody's losing sleep over and pull the ones that matter. Brakes, belts, leaks, anything safety or "will get worse and cost more."
Then send a short text. Not a blast. One that names the car and the exact thing you found.
Hey Maria, it's Ryan at Smith's Auto. When the Civic was in back in April we flagged the rear brakes getting thin, about 3mm. Wanted to check in before they start scoring the rotors. Want me to grab you a slot next week?
Name the car. Name the item. Give one real reason it matters now. No coupon, no "URGENT SAFETY," no paragraph. If it reads like a care reminder from the shop that already knows their car, it lands. If it reads like a sale, it gets deleted with the rest of their texts. We broke down the message that converts, and the ones that backfire, in our guide to following up on declined services.
One touch. If they say no again, note it and move on. The 90-day rule isn't nagging. It's showing up once, at the right time, with something true to say.
Keep the loop honest
When a customer books off a callback, write it on the record. "Declined 4/12, approved 7/14 off the 90-day callback." Do that for a couple months and you'll know exactly what the rule is worth to your shop, in your zip code, on your ticket. You stop guessing and start running a number.
That record is also how you catch the ones you'd otherwise drop. A brake job declined twice, six months apart, is a safety conversation you want documented anyway.
Where the software comes in
You can run the 90-day rule on a spreadsheet and a phone. Plenty of good shops do.
Where it gets easier: in Pitlane, declined items park on the vehicle record instead of vanishing off a paper RO, so pulling last quarter's declines is a filter, not an archaeology dig. PitCrew can draft the callback text from the actual flagged line, naming the car and the item. You read it, fix what you want, and send. Nothing goes out on its own.
Call them back at 90 days. See how much of your own work you've been leaving on the table.