They Said They’d Call Back. Call Them First.

When a caller says “I’ll call you back,” the shop usually waits. A simple callback habit for small HVAC and plumbing shops: same business day, one opening line, three tries at most, and the outcome written next to the reason code.

The call went fine. The caller was polite. At the end they said, “Let me think about it. I’ll call you back.”

So the shop waits.

Meanwhile the caller is still on the couch with a broken water heater and a phone in their hand. They don’t owe you a call. They owe themselves hot water.

Issue #4 gave you a reason log: one code for every answered call that didn’t book. This issue is what to do with the codes you can still win back.

Who gets a callback

Not every unbooked call. Just the warm ones.

From the Issue #4 codes:

H — Calling back / thinking it over. These go first. The caller told you the door was open.
E — Fee declined, F — Wanted a price first, J — Getting other quotes. Call these back only if you have something new to offer: a clearer fee explanation, an opening on the schedule, or just a direct question about whether they want to book.
A through D — never. Wrong numbers, existing jobs, out of area, work you don’t do. They were never bookable, and a callback won’t change that.

G (no slot that worked) and I (needs a spouse, owner, or landlord) aren’t on this list. G is a capacity question for your Friday review. I depends on when the person who decides is around.

ServiceTitan sorts things in a similar way. As of October 2026, its unbooked-call follow-up guide (dated Sep 30, 2026, and written for its AI phone agent) puts “Customer said they'd call back later,” “Customer gave an objection and hung up,” and “Customer said they were getting other quotes” under “Customer issue - VA tried, customer declined”. Problems on the shop’s side, like service area or job types, go on a separate checklist. That’s close to the never-bookable pile.

You don’t need their software for this. You need the list from last week and one person with a phone.

Same business day

Don’t wait until next week. Call the same business day.

The same ServiceTitan guide puts it this way: “that call is still a warm lead. Follow up within the same business day when possible” and “Call within 2–4 hours when possible — the issue is still fresh.” That’s a vendor’s advice to customers of its AI agent, not a measured rule. It just matches common sense. Someone with no heat at 10 a.m. hasn’t forgotten about it by 1 p.m.

Call during business hours, not at 9 p.m. because the to-do list said so. Even the software companies build in limits here. As of October 2026, Housecall Pro has a Quiet Hours setting, a limited test for shops with 24/7 business hours (Pipeline help page, Aug 6, 2026), so automated pipeline texts aren’t sent overnight, “so customers aren't texted at inconvenient times.”

The habit (our suggestion): at the end of each shift, pull every call coded E, F, H, or J. One person owns the callbacks. Not “whoever’s free.” One name.

One opening line

You don’t need a script binder. You need one sentence that doesn’t sound like a sales call.

Here’s an example, word for word from ServiceTitan’s follow-up guide. Remember, that guide was written for its AI phone agent, so treat it as a sample, not a standard:

“Hi, this is [Name] from [Company]. I saw you called earlier about [issue] — I wanted to make sure we took care of you. Do you still need help with that?”

Then, in their words: “Acknowledge, address, and offer a time.”

That last part matters. Offer a time. Not “just checking in.” A real slot.

A recent Contracting Business column by Wakefield & Brown (Oct 14, 2026) makes the point well, although it’s about in-home sales visits, not phone calls: “Sometimes what we call follow-up is really a decision that was unnecessarily postponed.” And: “The point isn't that follow-up is bad. Unnecessary follow-up is.”

The same applies on the phone. If the callback is just another “any thoughts?”, you’ve made another follow-up for later. Ask for the decision. “I have Thursday at 9 or Friday at 1. Want one of those?”

On the first callback, also ask: “Is it OK if we text you about this?” Write down Y or N. More on why below.

Three tries, then stop

Our suggestion, not a sourced rule: at most three attempts.

The same-day call.
A call on the next business day, or a text if they said texting was OK.
One last try.

After that, it’s done. Log it and move on.

Stop right away if they say no, or ask you to stop. That counts as an answer.

The software defaults point the same way, if you already use them. As of October 2026, Housecall Pro’s Pipeline (help page dated Aug 6, 2026) moves a lead through First Contact, Second Contact, and Third Contact, then Lost. Its example automations say: “When a lead is First Contact for [X] days, send SMS and update status to Second Contact.” and “When a lead is Third Contact status for [X] days, update status to Lost.” Jobber’s quote follow-ups send “up to two reminders” (Automations help, updated Aug 6, 2026), on the Connect plan and up as of October 2026. But they only work on a quote you’ve sent, not on a phone call with no quote.

Three is our number. The point is to have a number at all, so callbacks don’t keep going forever or stop after one try.

Log the outcome next to the code

Keep your Issue #4 code. Add one outcome after the callbacks are done. Only these four:

Booked
Not booked (new code if the reason changed). If an H turned into an E on the callback, write the E.
No answer after all tries
Asked not to be contacted

Plus the Y/N from the first callback: OK to text?

A filled example (unbooked calls only):

Date	Caller	#4 code	Callback owner	OK to text?	Tries	Outcome
Mon	Brooks	H	Office	Y	1	Booked
Mon	Chen	E	Office	N	2	Not booked (new code if the reason changed): E
Tue	Okafor	H	Office	Y	2	Not booked (new code if the reason changed): I
Tue	(555) 017-6604	J	Office	N	3	No answer after all tries
Wed	Patel	F	Office	N	1	Asked not to be contacted

Every row has a code, an owner, and one of the four outcomes. No blank lines.

ServiceTitan’s guide says something similar: “If they don't book: log the reason. After 2 weeks of data, look for patterns.”

If you already use our free night-call log, it now has columns for callbacks too: attempts, who's calling, when, the outcome, and OK to text.

Friday, fifteen minutes

Same Friday look as last week, with four more questions (our suggestion):

How many callbacks were made, and how many booked, for each code? H, E, F, J.
Is one code losing even after callbacks? That tells you the callback isn’t fixing it.
Are E or F rising? That usually means your fee or price conversation needs work, not your callback.
Which calls never got a callback at all? Those are the expensive ones, and nobody even tried.

The Contracting Business column has a good line for this: “Don't just ask how many opportunities there are. Ask why they're there.”

When not to call, and texting

If they said don’t call back: log “Asked not to be contacted.” Stop. Don’t send a text either.

Texting. This is not legal advice. Check with a lawyer before you text customers.

Some lines from the FCC’s consumer guide (reviewed Feb 27, 2026):

“FCC rules ban text messages sent to a mobile phone using an autodialer unless the phone owner previously gave consent.”
“Commercial texts require written consent; for informational texts, your consent may be oral.”
“You may opt out of any robocall or robotext at any time and in any reasonable manner.”

As of October 2026, the FCC adopted changes to its opt-out rules on Sept 30, 2026. According to a law-firm summary, they haven’t taken effect yet. Don’t rely on a blog post for the details. Ask your lawyer. State rules differ too, and this post doesn’t cover them.

A simple habit that keeps you on the cautious side: ask “Is it OK if we text you about this?” on the first callback and write the answer down. If they text STOP or tell you no in any clear way, it’s final.

Soft close — call them first

You already wrote down why the call didn’t book. Now use it. Pull the warm codes at the end of the shift, have one person make the call the same day, offer a real time, and write down what happened.

If you don’t have the codes yet, start with the free reason card, or read Issue #4 for where they came from. The rest of the free tools are at shopdispatch.github.io/shopdispatch/offers.

A few things to try this week, if they fit:

Before you clock out, circle every H on the card. Each one gets a call the same day if you can, and next morning at the latest.
Write your one opening line on the card. Whoever makes the callback says it the same way every time.
Next to every H, E, F, and J, write one of the four outcomes: Booked, Not booked (new code if the reason changed), No answer after all tries, or Asked not to be contacted.