A working-average 205-area-code plumbing shop burns through $22,862.40 a month of recoverable revenue on the missed-call share — same formula as the calculator, the after-hours slab-leak overlay, and the per-shop worked example on /case-studies. Same plain voice as /birmingham/plumbing , the just-shipped 205-area-code Birmingham plumbing trade rebut page this article reinforces, /birmingham , the per-trade routed math on /plumbing/calculator, and the playbook on /resources/missed-call-recovery-playbook.
The math
A small reference card for a working-average 205-area-code plumbing shop. The inputs below mirror the defaults on /plumbing/calculator; only the per-shop numbers your own call log produces change.
| Symbol | Description | Working value |
|---|---|---|
| weeklyCalls | Working-average weekly inbound call volume | 80 calls/wk |
| missedRate | Share that miss a live person on the first ring | 25% |
| weeklyMissed | Calls per week that walk into voicemail or a hang-up | 20 missed/wk |
| monthlyMissed | Carried across a 4.33-week month | ≈86.6 missed/mo |
| closeRate | CLOSE_RATE_DEFAULT held as a constant in the formula | 55% |
| avgTicket | The $480 plumbing mid-band default on /plumbing/calculator | $480/ticket |
| monthlyRecovery | Upper bound on what a 100%-clean recovery layer could pull back | $22,862.40/mo |
Step through the per-call formula with a working-average 205-area-code plumbing shop — roughly 80 inbound calls a week, about 25% missing a live person on the first ring, and the $480 plumbing average ticket the /plumbing/calculator defaults to — and the math lands on $22,862.40 of monthly recoverable revenue. That is the upper bound on what a fully clean recovery layer could put back on the dispatch board; a real shop typically nets somewhere under that figure, and an under-tuned one nets much less.
The full formula is the same one the rest of the funnel runs against: weeklyCalls × missedRate × CLOSE_RATE_DEFAULT × avgTicket, carried across the 4.33 weeks/month constant the per-shop worked example also uses. The exact per-shop number shifts with how heavy the after-hours mix is on the missed-call share, but the shape is the same — and every line item in the formula is a number that comes out of the call log and ticket history the audit-request intake reads.
Plumbing runs the most after-hours volume of the three trades the trade pages publish, the same emergency mix that lifts the per-call number above the cross-trade $620: the $480 mid-band default is what the /plumbing/calculator starts from, and the after-hours premium on water-heater swaps, sewer back-ups, and slab-leak diagnostics is what gives the recovery $14,300 in margin even before the after-hours slide lifts the ticket.
The per-call formula is generic; the per-call number lands where it does because of what the Birmingham plumbing market looks like. Most of the 205-area-code trades a Holdfast audit sees are residential plumbing shops whose after-hours share runs above 30% — March slab-leak calls on a Hoover ranch at 11:40pm, no-hot-water after-hours emergencies in Mountain Brook duplexes before the morning crew is on the road, water-heater swaps before an open house on a Sunday. That after-hours volume is what makes the missed-call layer hardest to staff by hand; the dispatcher would be asleep for most of the volume the recovery layer is built to catch.
Three things shape the overlay. First, the 205 area code covers a wide service-area geometry — Hoover, Homewood, Vestavia, Mountain Brook, Cahaba Heights, and the Trussville lots on the north side — and the dispatcher is rarely sitting next to the same physical call list the office answers. Second, the after-hours mix is disproportionately composed of the high-urgency jobs (slab-leak diagnostics, no-hot-water emergencies, water-heater swaps) that pull the average ticket above the mid-band and run a Sunday-morning cadence the marshaling routing on /birmingham/plumbing is tuned against. Third, the next-shop-around dynamics on a Sunday afternoon run hot — a slab-leak call that misses the shop is a call another plumbing shop is happy to answer before the morning crew.
The overlay is what an install tunes against, and it is what the audit-request intake walks when an owner-operator starts the conversation. The same overlay shows up on /birmingham — three trade verticals under one after-hours recovery layer — and on /plumbing in the proof bullets the calculator leans on. The numbers above are not invented stats; they are the working averages the install is tuned against, drawn from the per-trade proof points and re-used on the per-trade routed calculators so the starting average ticket is the same number the trade page is published with. The worked projection on /case-studies walks the same per-shop sheet against the same numbers.
Once a recovered-call layer is in place, three things shift on the dispatch board. First, the same per-call math that lands at $22,862.40/mo for a working-average Birmingham plumbing shop becomes a per-shop worksheet — the audit-request intake pulls ten of your recent 205-area inbound calls and your last quarter's ticket values to fill the same inputs from real numbers. Second, the after-hours slot the dispatcher would have missed asleep is a confirmed booking on the dispatch board before the morning crew is on the road — same shape as the 3-touch SMS cadence and the booking handoff the playbook on /resources/missed-call-recovery-playbook walks.
Third, the dispatcher load shifts from 'catch as many calls as the office can answer' to 'work the bookings the recovery layer has already qualified' — the per-shop shape the audit pulls ten recent recordings against. The cross-trade averages the per-call math leans on are what carry the formula into a defensible monthly figure for your vertical; the per-shop numbers your own call log produces are what the audit writes back into the same sheet.
The worked projection on /case-studies — Crescent Plumbing, the 3-truck residential + light-commercial shop — walks the same per-shop sheet with the same cross-trade averages, with the monthly recovery figure tuned to a real-shape shop's weekly call volume. Labeled as a sample; the audit is the path to the shop's own numbers.
Last reviewed: 2026-08-19. The per-call formula and the slab-leak / after-hours overlay on this page are the same shape the calculator and the per-shop audit publish.
See it on your own calls
A 20-minute audit uses ten recent 205-area inbound calls and your last quarter's ticket values to walk through the same per-call math for your shop — no install, no commitment.
See also
Read next
Three sibling articles in the same per-call math cluster + /calculator + /audit. The audit-CTA is one click away from any article in the funnel.
Methodology
Last reviewed: 2026-08-19. The per-call math on this page is the same formula the calculator and the per-trade routed calculators publish, run against a working-average 205-area-code plumbing shop — 80 weeklyCalls, 25% missedRate, $480 average ticket, 55% close rate. The 205-area-code overlay and the after-hours / slab-leak share are pulled from /birmingham/plumbing, /birmingham, and /plumbing, and the per-shop reshape is filled by the audit-request intake against your own call log and last quarter's ticket values.
Scope. Same plain voice as the rest of the site — one paragraph per claim, no per-minute framing, no meter. This page is general information, not a per-shop quote and not legal advice. Where a specific shop needs the math walked against its own call log, the audit-request intake is the place to ask for it. The per-call math itself doesn't drift; the per-shop tuning does.
See what those missed calls could be costing your shop.