Missed-Call Recovery: The 60-Second Window That Decides Local Service Revenue

The 60-second rule

A homeowner calls a plumber at 9 PM because the kitchen sink is backing up. The phone rings out. They hang up.

Within five seconds, the caller pulls up the next plumber in their search results. By thirty seconds, they have dialed it. By sixty seconds, the second plumber’s phone is ringing.

If the first plumber wants to recover that lead, they have a window measured in seconds. A text reply at sixty seconds saying “Hey, sorry we missed you — what’s the issue?” lands while the customer is still mentally on plumbing. A text reply at five minutes lands after the second plumber has already answered.

This is not a hypothetical. The data on speed-to-lead has been consistent across thousands of trades businesses for over a decade: response time is the single biggest predictor of close rate, and the curve is brutally steep. A response within sixty seconds closes around 30% of the time. A response at thirty minutes closes around 5%. After an hour, the lead is essentially gone.

Voicemail is not a recovery strategy in 2026. The recovery strategy is a text-back automation that fires within sixty seconds of the missed call.

How missed-call text-back actually works

The mechanics are simple. The software watches for a missed call on your business number. The instant it detects one — ring-out, no answer, voicemail — it triggers an outbound SMS to the caller’s number.

The text says something like:

Sorry we missed you at (205) 555-0142! This is the AI assistant from Acme HVAC — what can we help with?

The customer replies. The AI responds. A two-way SMS conversation happens. The AI qualifies the job, captures the address, pulls live calendar slots, and books the appointment.

A real recovery thread looks like this:

• AI, +12s: Sorry we missed you at (205) 555-0142! This is the AI assistant from Acme HVAC — what can we help with?
• Customer, +38s: AC stopped blowing cold. House is at 84.
• AI, +42s: Sounds like an emergency — we have a tech available today between 2:00 and 4:00 PM. Lock that in?
• Customer, +58s: Yes please. 1820 Birch Lane.
• AI, +1m 06s: Booked for 2:00 PM today — Mike will call when en route. Confirmation sent.

That is a recovered call. Ninety seconds from missed ring to booked job.

Why text beats callback

Most trades shops, when they think about missed-call recovery, think about calling back. Their voicemail says “leave a message and we’ll get back to you,” and then sometime later — an hour, the next morning — somebody at the office calls back.

The math has shifted. Call-back works for low-urgency, high-consideration purchases (a remodel quote, a maintenance plan inquiry). It does not work for emergency-driven service calls.

By the time you call back, the customer has already booked another shop. They feel awkward telling you that. They send your call to voicemail. Your callback rate is low, your conversion on the callbacks is lower, and the whole exercise feels like rowing upstream.

Text-back inverts the dynamic. The customer is not committing to a phone call — they are reading a notification. They reply when it is convenient. They are still in problem-solving mode because the issue has not been solved yet. The conversation can be picked up and put down without either party feeling rude.

And the AI runs the SMS conversation in real time, twenty-four hours a day, seven days a week, without burning out a human.

What the SMS conversation captures

A well-built missed-call text-back does not just recover the call. It captures structured information that makes the rest of the operation work.

By the end of a typical thread, the system has logged:

• Customer name, address, phone number, and best contact time.
• The specific service problem in the customer’s own words.
• Urgency level (emergency, same-day, this-week, planning).
• Whether the call was emergency-routable to a human.
• Whether the customer booked a slot or escalated.
• The full transcript, time-stamped and searchable.

That data lands in the CRM as a contact record. The follow-up sequence fires from there. The customer feels attended to from the first text through the booked appointment, and the office has a complete record without having to type a thing.

The compliance side

Text-back automation has a regulatory shape that matters in the United States. TCPA, the Telephone Consumer Protection Act, governs commercial SMS. The relevant nuance for missed-call recovery:

The customer just called your business. That is consent to a transactional reply. You are not cold-texting a stranger from a list — you are responding to an active inquiry. Courts have been reasonable about this distinction.

That said, the system needs to handle:

• Quiet hours: no automated SMS between (typically) 9 PM and 8 AM unless the customer initiated.
• STOP keyword: every message has to include opt-out language, and STOP must immediately and permanently halt future automation.
• HELP keyword: every message has to support HELP for support information.
• Opt-in evidence: the inbound call itself is the evidence; the system logs it.

A properly built missed-call text-back is TCPA-compliant by default. A jury-rigged one is not. The difference is in the details, and the details are the entire compliance question.

Where text-back fits in the larger system

Missed-call recovery is a safety net, not a primary strategy. The primary strategy is to answer the call live.

That is what an AI phone receptionist does. The AI picks up before voicemail kicks in, runs the conversation, books the job, captures the details. Most calls get caught at the front door.

Recovery is the system that catches the calls that still slip — the rare overflow when two calls come in at once, the dead-spot moments, the times the AI itself escalates and the human does not pick up. Those calls get the 60-second text-back.

Together, the two systems give you a phone that essentially never goes to voicemail. The AI catches the live ones. The recovery catches the rest.

For most owner-operated trades shops, that combination is the difference between a 70% answered rate and a 99% answered-or-recovered rate. At a $1,200 average ticket, that gap is not theoretical. It is the difference between the shop that grows and the shop that wonders why growth feels stuck.

Where to start

If you have inbound call data — and almost every shop does, even if nobody has looked at it in years — the recovery math reveals itself in fifteen minutes.

Pull the last 90 days of call records. Count the rings-out and the voicemails. Multiply by your average ticket. Divide by your historical close rate.

That number is your monthly leak. The text-back stops it within a week of going live. The AI receptionist that answers the calls in the first place takes a little longer to install, but the combined system is what closes the gap to near-zero.

Sixty seconds is the window. The shops that close it win the local market.