Mike: Wednesday night. Quarter to seven. I'm locking up the shop and my phone buzzes — voicemail notification. Homeowner on the west side, water heater's leaking, she sounds panicked. Says she found us on Google, tried to call, nobody picked up.
Chris: Quarter to seven. Your CSR clocked out at five.
Mike: Clocked out at five. So this woman — she's standing in her utility room with a towel on the floor — she leaves a message and waits.
Chris: How long did she wait?
Mike: She didn't. I listened to that voicemail the next morning at seven fifteen. Called her back at seven twenty.
Chris: And?
Mike: She'd already booked somebody else. Found another shop that picked up at seven AM. They were at her house by nine. That's a twelve-hundred-dollar water heater install I heard about eight hours too late.
Chris: So the lead came in. You earned the search click. You earned the call. And the only thing between you and that job was ninety minutes of dead air.
Mike: Ninety minutes. And I didn't even know the call existed until the next day.
Chris: That's the leak we're fixing today.
Chris: That call Mike just described — it's not a one-off. ServiceTitan's own data shows forty to fifty percent of online bookings come in after hours. That's half your demand hitting voicemail or ringing out while nobody's watching. And every one of those calls is a person with a problem and a credit card who is going to book somebody in the next sixty minutes.
Mike: I'm Mike. That's Chris. And today we're building the loop that catches those calls — a fifteen-minute missed-call recovery process you can ship this week with whatever CRM you're already running. No new software. No new headcount. Just a queue, an owner, a timer, and two callbacks.
Chris: So let's put a number on this. MIT ran a study on lead response — cross-industry, not just trades — and found that contacting a lead within five minutes made you twenty-one times more likely to qualify them than waiting thirty minutes.
Mike: Twenty-one times.
Chris: Twenty-one times. Harvard Business Review ran a similar study. Responding within an hour — just one hour — made you seven times more likely to qualify than responding after an hour. And that's for web leads, where the person filled out a form and is probably still browsing. A phone call is higher intent than a form. That homeowner with the leaking water heater isn't comparison shopping on a spreadsheet. She's standing in a puddle.
Mike: Right. And she's calling the next number on the list the second your voicemail beeps.
Chris: Exactly. So the decay curve on a missed call in home services is steeper than what those studies even measured. You're not competing with a thirty-minute window. You're competing with however long it takes the homeowner to tap the next listing on Google.
Mike: And during June — HVAC season, plumbing season, garage doors — the volume goes up but the answer rate doesn't. You've got the same two CSRs handling twice the call volume. More calls are hitting voicemail. More calls are abandoning in queue. And you don't even know it's happening because you're out on a job or you're in the truck.
Chris: And that's the part I underestimated for a long time. I used to think missed call recovery was an after-hours problem. It's not. It's a Tuesday-at-two-PM problem when both your CSRs are on the phone and a third call rings in and drops.
Mike: That's the one nobody sees.
Chris: Nobody sees it. And here's a detail that trips people up if you're on ServiceTitan with Contact Center Pro — CCP separates voicemails from abandoned calls. They're two different lists. A caller who waits in queue and hangs up shows up in Abandoned Calls. A caller who leaves a voicemail while in queue shows up under Voicemails. Not Abandoned.
Mike: Wait — so if I'm only watching my abandoned call report, I'm missing every voicemail?
Chris: Every single one. They're categorized separately. So if you built a recovery workflow around your abandoned call list and thought you had it covered — you've got a blind spot the size of half your missed calls.
Mike: That's a design choice that costs people money.
Chris: It's a reporting distinction. And once you know it exists, you build two views — one for abandoned, one for voicemails — and you work both. But most shops don't know. They see a low abandoned count and think they're fine.
Mike: Okay. So we've got calls falling through — after hours, during peak, in queue. What does the recovery loop actually look like?
Chris: Five pieces. And the whole thing runs inside fifteen minutes from the moment the call is missed. First piece — the call has to land in a queue you can see within about sixty seconds. If you're on ServiceTitan, that means you need your voicemail playback set up in Call Playback and your CCP views saved for both abandoned calls and voicemails. Pin both of those for your CSRs. They should be the first thing they see when they open the dashboard.
Mike: And if you're on Jobber?
Chris: Jobber doesn't have native call logs the same way. But there are integrations — Quo is one, JustCall is another — that catch missed calls and voicemails and push them into Jobber as Requests. Quo will check the caller ID against your Jobber contacts, and if there's no existing request, it creates one automatically with the AI call summary and the full transcript attached.
Mike: So the transcript is sitting right there on the request.
Chris: Right there. Your CSR opens the request, reads what the caller said, and calls back without having to listen to a two-minute voicemail first. That's the speed advantage of transcript-attached recovery.
Mike: Okay. That's actually faster than listening to the voicemail.
Chris: Way faster. So that's piece one — the queue. Piece two is ownership. The second a new item hits that queue, somebody claims it. Not "the team will get to it." One person. Their name is on it. And they start a fifteen-minute timer.
Mike: A literal timer?
Chris: However you want to do it. A CRM task due in fifteen minutes. A kitchen timer on the desk. An emoji in your team channel. The mechanism doesn't matter. What matters is that the clock is visible and somebody's name is next to it.
Mike: And if nobody's free? If both CSRs are on calls?
Chris: Then the service manager takes it. Or whoever's on-call. The rule is — if no CSR claims it within five minutes, it escalates. You don't let it sit.
Mike: That's a lot of pressure during a busy afternoon.
Chris: It is. And that's why you designate a recovery lead during peak hours. One CSR per hour whose job it is to watch the queue. The other CSR handles inbound. You rotate it. It's not extra headcount — it's a role assignment.
Mike: Okay. So we've got the queue, we've got ownership. What's the actual callback look like?
Chris: Piece three — two call attempts and one text in between. First attempt is a phone call, inside five minutes of the miss. You call from your shop number so the caller ID matches. And your CSR says something like — "Hi, this is Sarah with Apex Plumbing. Looks like we just missed your call about the water heater. I've got the schedule open — do you need a tech today, or is tomorrow morning better?"
Mike: Two options. Not "when works for you."
Chris: Two options. Always. You're closing, not asking. If they don't pick up, you leave a short voicemail — same structure. "Sorry we missed you. I can hold Thursday morning or Friday afternoon. Call or text me at this number." Then you send one text.
Mike: And this is where it gets tricky.
Chris: This is where it gets tricky. The text has to come from a registered number. Both ServiceTitan and Jobber require A2P ten-DLC registration before you can send two-way texts through the platform. If you haven't registered, your texts might get blocked by the carrier and you won't even know.
Mike: I've heard guys say their texts just stopped going through and they had no idea why.
Chris: That's exactly what happens. The carrier silently drops them. So before you add texting to this loop — go into your CRM settings, find the texting registration section, and complete it. ServiceTitan calls it "Register for Texting." Jobber calls it "Register Your Number." You'll need your tax ID and business details. Takes about ten minutes.
Mike: And the text itself — what does it say?
Chris: Keep it under a hundred and sixty characters. Something like — "Apex Plumbing. Sorry we missed your call about the water heater. We can do Thursday AM or Friday PM. Reply YES to book or STOP to opt out." That's it. You identify your business, you reference the issue, you give two windows, and you include the opt-out. That last part is not optional.
Mike: STOP to opt out. On a callback text.
Chris: I know it feels weird. But the FCC's TCPA rules and the carrier industry guidelines from CTIA are clear — you identify yourself, you make it easy to opt out, and you stop immediately if they say stop. This is not legal advice. Talk to your attorney about your specific setup. But the baseline is — one short text, business name included, opt-out included, and you honor it instantly.
Mike: Okay. So we've called once, texted once. Then what?
Chris: If no response after the text, you make one more call before the fifteen-minute mark. Same structure — "Circling back so we can lock a spot. Thursday or Friday — which works?" If they answer but aren't ready, you schedule a concrete next step. An estimate slot, a specific callback time. Something with a date on it.
Mike: And if they just don't pick up either time?
Chris: Then you disposition it and move on. That's piece four — every record gets a clear outcome tag. Booked. Estimate scheduled. Reschedule requested. No answer after two attempts. Wrong number. Do not contact. And you add a reason — after-hours overflow, price shopper, out of service area, emergency resolved. One line.
Mike: You really think my CSR is going to type a reason code on every missed call?
Chris: She's going to pick from a dropdown. You set up five or six reasons in advance. She taps one. Takes three seconds. And the reason is what makes the daily review useful — because if you see "price shopper" twelve times in a week, that's a pricing conversation, not a callback conversation.
Mike: That's a different problem.
Chris: Different problem. But you only see it if you're tagging.
Chris: Piece five is the daily review. And this is the piece that separates shops that try this for a week from shops that actually keep it running.
Mike: Because the loop itself is not that hard. The hard part is doing it every day when June hits and you're slammed.
Chris: Right. So the review is ten minutes. The service manager pulls yesterday's unrecovered calls — the ones tagged "no answer" or "left voicemail, no callback." And they pull two or three recorded calls from CSRs who did make callbacks.
Mike: You're listening to the recordings?
Chris: Two or three. Not all of them. You're listening for three things — did the CSR attempt the callback within the window, did they use the talk track, and did they offer two specific time slots instead of an open-ended "when works for you." That's it. Ten minutes. And you coach from what you hear.
Mike: So it's not a report you read. It's a recording you listen to and a conversation you have.
Chris: And that conversation is what changes behavior. You can hand someone a script. But until you listen to them use it and say "hey, on that seven-fifteen callback, you asked when works for them — next time try Thursday or Friday morning, give them two slots" — that's when it sticks.
Mike: What about after-hours calls? The ones that come in at six forty-five like mine did?
Chris: First thing in the morning. Eight AM, before you take new inbound. Your CSR opens the after-hours queue sorted by timestamp and works it oldest first. The talk track shifts slightly — "Hi, this is Sarah with Apex. We saw your call last night about the water heater. We kept a slot open this morning if you still need help."
Mike: "We kept a slot open." That's good.
Chris: It implies urgency and availability. And it's true — you should be holding a morning slot for exactly this. The after-hours calls are your highest-intent leads. They called when they had a problem. If you're the first one to call back at eight AM, you're booking that job.
Mike: Now — I know someone's listening to this thinking, "Chris, I've got four techs and two CSRs and you want me to add a recovery queue and a daily review and a ten-DLC registration and disposition codes? In June?"
Chris: Yeah. I do. Because here's what you're already doing in June — you're losing three, four, five calls a day to voicemail or queue abandonment. At an average ticket of four hundred dollars, that's two thousand dollars a day walking out the door. You don't need to recover all of them. If this loop books one extra job a day — one — that's twenty jobs a month you weren't getting.
Mike: Twenty jobs a month.
Chris: At four hundred average ticket, that's eight thousand dollars in revenue from a process that costs you zero in software and maybe thirty minutes of CSR time a day. The math is not close.
Mike: And the scorecard — what are you actually tracking?
Chris: Four numbers. Time to first attempt — you want the median under ten minutes, stretch goal under five. Two-attempt completion rate — did the CSR actually make both calls and send the text? You want eighty percent or better. Recovery rate — out of the calls where you reached someone, how many booked? Set a baseline in week one and aim for ten to twenty percent improvement by week four. And after-hours first attempt by eight thirty AM — ninety percent or better.
Mike: That's clean. Four numbers.
Chris: Four numbers. You can track them on a whiteboard if you want. The point is visibility. When the number drops, you know where to look — the recordings tell you why.
Mike: What about the PlumbRite thing — that Nebraska plumbing company. Didn't they do something like this?
Chris: Vendor-reported case, so take it with that caveat. But Scorpion published a case study on PlumbRite — they used an automated response tool to catch missed and overflow calls and route qualified requests back to the team. Scorpion says it resulted in more booked jobs from previously missed calls. They don't publish the exact lift number, so I can't give you a percentage. But the pattern matches — faster response on missed calls equals more bookings. That's consistent with everything the MIT and Harvard research shows.
Mike: Even without the exact number, the direction is obvious.
Chris: The direction is obvious. And you don't need a vendor tool to do it. You need a queue, an owner, a timer, and a talk track. That's the whole loop.
Mike: So that water heater call I told you about at the top — the one that came in at quarter to seven. If I'd had this loop running, what would have been different?
Chris: The voicemail hits the queue. Your after-hours process flags it. Next morning at eight, your CSR sees it first thing — transcript attached, caller name, issue. She calls before the homeowner's even had coffee. "We saw your call last night. We kept a morning slot open."
Mike: And instead of hearing "I already booked somebody else," I'm dispatching a tech by nine.
Chris: That's the difference between a twelve-hundred-dollar install and a voicemail you listened to too late. The loop doesn't require anything you don't already have. It requires you to decide that missed calls get worked like leads — with an owner, a clock, and a talk track.
Mike: We put together a one-page SOP for this — the "Missed-Call Recovery in Fifteen Minutes" sheet. It's got the full loop, the talk tracks, the disposition codes, the scorecard, and the ten-DLC registration reminder. ServiceTitan and Jobber variants. Grab it on the Resources page, print it, hand it to your CSRs Monday morning.
Chris: One question for this week. Pull up yesterday's voicemails and abandoned calls. Count them. Then ask yourself — how many of those had an owner assigned within five minutes? If the answer is zero, you know where to start.
Mike: That's this week. I'm Mike.
Chris: I'm Chris. Go catch those calls.