Inbound calls · 30 days
142
All sources combined · paid, LSA, GBP, referral
Stan Consulting · Marketing Atlas · Case File · Construction Marketing
The Plumber Who Lost 60% of His Pipeline to Callback Lag.
case_type: composite cluster: construction-marketing published: 2026-05-10
01
Wednesday afternoon, mid-July. The plumber is on a job in Roseville and his phone has been dead since lunch. He plugs it in at 5pm. Six missed calls in the last four hours. Three are from the same number. He calls the number back. The voice on the other end says they already booked the competitor across town · "He answered when we called the second time." Average ticket: $1,400. Average ticket on the other 38 missed calls last month: $1,400 each.
The conversation that ended that Wednesday is the conversation the audit reads in writing thirty days later. The operator is a residential plumber. Three-point-two million annualized. Six trucks across emergency and scheduled work. Eight technicians, a two-person daytime office, and one after-hours dispatcher covering six in the evening to seven in the morning. Monthly paid spend across paid ads, Local Services Ads, and a Google Business Profile runs about eight thousand dollars.
The operator's read of the business has been that the marketing is "fine." Lead volume is up year over year. Cost per lead is holding. What is not holding is the conversion from inbound call to booked job, and the operator has been investigating the phone-room script for two months when the answer is already in the call log, in a column he has not been reading.
The diagnostic is scoped on a Friday. The brief is two sentences. Pull the thirty-day inbound call data. Tell us what every missed call would have been worth if the office had picked up.
- Trade
- Residential plumbing · emergency and scheduled
- Annualized revenue
- $3.2M
- Fleet
- 6 trucks · 8 techs · 2-person office
- Monthly paid spend
- $8K across paid ads, LSAs, and GBP
- 30-day inbound calls
- 142 across all sources
- Missed calls
- 39 of 142 (27% miss rate)
- Average callback time
- 4.2 hours during business hours
- Engagement
- Contractor Lead Diagnostic · written verdict
02
The call log told a story the booked-jobs column could not see. Six numbers below. The two columns the operator had been reading were the wrong two columns.
Answered calls
103
Office picked up inside the first 30 seconds
Missed to voicemail
39
Rolled to voicemail without a human picking up
Missed calls reached on callback
11
Of the 39 missed, only 11 were ever reached again
Average callback latency
4.2h
Average elapsed time from miss to first callback attempt
Lost to competitor (estimated)
28
Missed calls that never returned · assumed to a competitor
The miss rate sat at twenty-seven percent. The industry data on residential plumbing during business hours puts the average miss rate right at twenty-two percent, with peak season climbing toward thirty-five. The shop was running near the band. What was not near the band was the four-point-two hour callback latency. The industry data on inbound conversion says intent collapses inside the first hour. Most studies place the practical floor at sixty seconds for the largest conversion lift. Four-point-two hours is not in the same conversation as sixty seconds.
The operator had assumed the missed calls would be re-attempted by the prospect or would convert on the eventual callback. Both assumptions were wrong against this thirty-day window. Of the thirty-nine misses, eleven were reached on callback. Twenty-eight never were. The eleven that were reached on callback converted at a rate of about eighteen percent. The twenty-eight that never returned a call had already booked a plumber by the time the office got around to dialing back.
03
Four explanations were live when the audit started. Each let the operator keep paying for more leads against an office that could not answer the ones already arriving.
Wrong reason 01
"The ads need fixing · cost per lead is creeping." The marketing read. The cost per lead had moved from about forty-five dollars to about fifty-eight over the trailing year, and the operator had read the creep as the cause of the soft booked-jobs column. The math is unforgiving. Even at fifty-eight dollars per lead, the operator was paying for one-hundred-forty-two leads in a month and converting zero on the thirty-nine that went to voicemail. Cutting cost-per-lead by half does nothing if the bottleneck is the office's ability to pick up the phone.
Wrong reason 02
"The phone-room script needs work." The conversion read. The office was using a script that had been written four years prior and the operator had been working with a sales coach to rewrite it. Script quality matters at the margin. The script does nothing for the twenty-eight calls that never connect to a human. The operator was working a refinement on the seventy-three percent he could pick up and ignoring the twenty-seven percent he could not.
Wrong reason 03
"Hire another office person." The headcount read. The operator was working through a hire decision on a second daytime office person. The hire would have helped at a cost of about fifty-thousand a year fully loaded. The hire was probably correct as a medium-term move; it was the wrong first move. There was a sixty-second-fix install that would recover seventy-eight percent of the misses against zero new headcount cost. The hire stayed on the table; the install shipped first.
Wrong reason 04
"The market is softening." The macro read. Residential plumbing was running flat against the prior year in the operator's region. The macro frame was real and unrelated. The thirty-nine missed calls were not a softening-market story. They were a phone-coverage story dressed up in macro vocabulary. The macro frame is the frame an operator reaches for when the operator has stopped reading the operating-floor data.
All four explanations pointed at marketing, sales, headcount, or the macro. None of them pointed at the phone. The phone was where the leak was.
04
There was no automated response on the line when the office could not pick up. Voicemail had been the answer to "what happens when the phone rings and nobody is there" for the entire history of the shop. The structural defect was not a person missing. The structural defect was a system missing. One sixty-second-fix install would have closed sixty percent of the leak before any headcount move was needed.
The decomposition that follows reads the thirty-nine missed calls against ticket value, against industry recovery rates on missed-call text-back automation, and against the competitor-win rate the operator's customers had already named in post-job surveys.
05
The diagnostic calculates the loss not from missed calls in general, but from the callback-lag specifically. Of the 39 missed calls in the trailing 30 days, 28 were never reached. Average ticket times 28 equals $39,200 in monthly revenue, gone. The fix is not hiring. The fix is a missed-call-text-back automation that costs $87 per month and recovers 60 to 78% of missed calls inside 60 seconds. Annual recovery: ~$280,000. Annual cost of the fix: $1,044.
The math on the missed calls is in three layers. Pipeline lost, pipeline recoverable, and the install that would recover it. The numbers below are the reveal the operator carried out of the diagnostic on a single sheet of paper.
L1
Pipeline value of the 28 unreached calls
The headline number
Twenty-eight missed calls were never reached. The shop's average ticket across the trailing year ran at fourteen-hundred dollars on residential service. Multiplying twenty-eight by fourteen-hundred names the headline. Thirty-nine-thousand-two-hundred dollars per month in lost revenue against the shop's existing inbound demand. Annualized, that is four-hundred-seventy-thousand. Against three-point-two million in revenue, the leak is fifteen percent of the top line. The operator had been measuring the pipeline as if the missed calls did not exist; the pipeline he had been reading was sixty percent of the pipeline he had been generating.
- Missed calls unreached · 28 of 39
- Average ticket · $1,400 residential service
- Monthly pipeline loss · $39,200
- Annualized loss · $470,400 · ~15% of revenue
L2
What the 78% recovery rate looks like
Industry data
Industry data on missed-call text-back automation says the recovery rate is around seventy-eight percent. A miss triggers an automated text within sixty seconds; about three-quarters of misses respond to the text within an hour. Of those responses, the operator's office books the job at roughly the same rate as a live-answered call, sometimes higher because the text bypasses the on-hold and IVR frictions that prospects already dislike. Applying seventy-eight percent recovery to twenty-eight unreached calls puts the recoverable count at twenty-two missed calls per thirty-day window. Twenty-two times the average ticket gets the operator inside thirty-thousand dollars of recoverable monthly revenue from a single install.
- Industry missed-call text-back recovery · ~78%
- Recoverable calls per month · ~22 of 28
- Recoverable monthly revenue · ~$30,800
- Recoverable annualized · ~$370K
L3
The install · configuration, not headcount
The 60-second fix
The missed-call text-back is a CRM-side configuration on most modern phone systems. The install on this shop took ninety minutes against the existing service-software phone integration. The text template is one paragraph: name of the shop, acknowledgment of the missed call, a question about the issue, and a callback-window option the prospect can choose from. The text fires within sixty seconds of the missed call. The office's morning queue then prioritizes the text-responders ahead of cold callbacks. No new headcount, no new software cost beyond the existing tracking subscription, no new sales process. The install is the entire fix on the L1 leak.
- Install time · ~90 minutes against existing phone integration
- New software cost · $0 inside existing call-tracking subscription
- New headcount · 0
- Text-response window · under 60 seconds from missed call
Thirty-nine-thousand-two-hundred monthly. Recoverable at seventy-eight percent. Install is ninety minutes. The math is the math. The operator did not need a marketing fix. He needed the configuration he had not been told existed.
06
The verdict named the install order. Five steps. The first two ship inside one week with no new spend. The remaining three sequence over the following month.
-
Day one · Configure missed-call text-back inside the existing phone integration
Open the phone-tracking or service-software dashboard. Locate the automation section. Build a missed-call rule that fires a text-message template within sixty seconds of any inbound call rolling to voicemail. Write the text in one paragraph: shop name, acknowledgment, an open question, a callback-window option. Test the rule against an internal phone. Confirm the text fires and the response routes back to the office line. The configuration is the install; the install is the fix on roughly seventy-eight percent of the leak.
-
Day two · Install a five-minute first-attempt callback rule for live callbacks
Voice callbacks against any missed call that does not respond to the text get a five-minute first-attempt rule. The office's morning queue runs missed-call returns ahead of cold prospecting. The callback latency moves from four-point-two hours toward thirty minutes inside the first week, with the queue cleared by the end of every shift. The rule is a procedural change; it does not require new headcount and it does not require a new phone system. The dispatcher owns the rule against a shift-end audit.
-
Week one · Install the after-hours voicemail loop into the text-back automation
The single overnight dispatcher cannot cover the six-to-seven-am window or the dinner-hour spike. The after-hours voicemail rolls into the same missed-call text-back rule, with a slightly modified template that names after-hours availability and a morning-callback promise. After-hours prospects are typically the emergency-plumbing audience and convert at higher tickets than business-hours scheduled work. The after-hours capture is incremental against the daytime capture and lifts the average recovered ticket above the daytime average.
-
Week two · Build the callback-rate dashboard
A single weekly read is added to the operator's Monday review. Inbound calls, answered calls, missed calls, text-back responses, missed-call-to-job conversion rate, average callback latency. The dashboard is the operating contract between the operator and the dispatcher. Variance from the prior week beyond ten percent triggers a Monday conversation. The dashboard makes the leak visible week-over-week and removes the assumption that voicemail is the floor of the office's response.
-
Month two onward · Reconsider the second-office-person hire against the new floor
The missed-call text-back recovery typically puts the miss-rate-to-loss conversion at roughly five percent rather than seventy-two percent. With the recovery automation in place, the second daytime office hire is no longer firefighting voicemail; it can scope into outbound estimating, post-job follow-up, and referral-program management. The hire decision is re-scoped against the new floor. The same fifty-thousand-a-year cost now produces a different return because the underlying system has been fixed first.
07
The compounding mechanism is the gap between the assumption that voicemail catches what the office misses and the data that says voicemail is where pipeline goes to die. Inbound prospects in residential plumbing have an intent half-life measured in minutes, not hours. The missed-call text-back is not a marketing automation in any meaningful sense. It is a phone-coverage rule that happens to live inside the marketing stack.
What this case file is for: any contractor running paid lead spend above three-thousand monthly who has not pulled the trailing-thirty-day call log against the booked-jobs log and named the gap. The gap is almost always in the same place. The fix is almost always the same fix. The math is almost always defensible against the install cost inside the first month.
The operator's call log was the right document. He had been reading the wrong column. The seventy-three percent conversion rate against answered calls described the office he had built. The four-point-two-hour callback latency described the office he did not know he had. The first column kept him optimistic about marketing. The second column was where the pipeline was being lost.
The phone was not the funnel. The four hours after the phone rang were the funnel.
Five Cents · Stan's note
Five Cents
What I keep seeing in service-trade accounts is the assumption that the marketing budget is the lever and the phone is the constant. The phone is not a constant. The phone is the funnel. The marketing budget delivers the funnel to the top of the phone. Everything that happens after the inbound rings is the actual business. The operators I work with are mostly investing at the top of the funnel and leaving the middle uncovered, and the middle is where the leak is almost always located.
The plumber in this composite is the version of the case I have seen on rooftops, in hydronics shops, in HVAC offices, and in roofing crews. The number changes. The shape does not. Twenty-seven percent miss rate, four-hour callback latency, sixty-percent loss to competitors on the unreached half. The operator reads the cost per lead and the booked-jobs total and the two numbers make the business look basically fine. The two missing numbers are the miss rate and the callback latency, and those two are where the next quarter of growth is already sitting, free of acquisition cost, waiting on a configuration change.
What I want operators to take from this is to pull the call log tomorrow morning. Count the missed calls. Multiply by the average ticket. The number on the back of that envelope is what the missed-call text-back automation is worth before any acquisition spend rises. The Contractor Lead Diagnostic produces the install order and the math. The install is then a ninety-minute configuration change inside the system the operator is already paying for.
Stan Tscherenkow · Marketing Atlas · 2026-05-10
09
Each link below points at a related Atlas page that handles a piece of the case file in more depth. Reference pages define the term. Position pages give the firm's defended doctrine. The hub gives the map.
If this is the pattern on your call log
Pull the call log. Count the missed.
If the case file maps to your shop — inbound running, a callback queue you have not measured, voicemail catching what the office cannot — the engagement that runs this diagnostic is the Contractor Lead Diagnostic. A written verdict against the missed-call recovery framework with the trailing-thirty-day math, the install order, and a recoverable-revenue line on the cover page. If the verdict does not name three specific moves that will move your phone inside 60 days, you keep the report and the Callback-Rate Calculator and we refund the $999.