Walking the calculator math against a working-average Chattanooga shop — 80 calls/week, 25% miss rate, $480 ticket — and pulling the per-trade proof points from /plumbing, /hvac, and /electricalthat the formula leans on. Same plain voice as /faq, the playbook on /resources/missed-call-recovery-playbook, and the per-shop sheet on /pricing.
The math
A small reference card for the inputs and the line items the formula produces. Each row below is the same number the calculator produces when you punch it in by hand.
| 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 | The 55% close rate the calculator holds as a working average | 55% |
| avgTicket | The $480 mid-band the generic /calculator defaults to | $480/ticket |
| monthlyRecovery | The upper bound on what a 100%-clean recovery layer could pull back | $22,862.40/mo |
Step through the calculator with a working-average Chattanooga shop — 80 calls per week, roughly 25% of those missing a live person on the first ring, and a $480 average service ticket — 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 same formula lives on /calculator and on each trade-specific routed calculator (/plumbing/calculator, /hvac/calculator, /electrical/calculator) — and on /pricing as the per-shop worked example. We use it because it is the cleanest way to compare a shop's weekly mix to what the week actually booked, without dragging the answer through a per-call-services model or a marketing-bonus carveout.
If our own math is right, a service-trade operator running the kind of weekly call volume a mid-size Chattanooga shop runs is leaving the equivalent of a senior tech's labor cost on the floor every month — and most of it shows up not in lost jobs but in jobs the next shop took the call on.
The math is a formula. The number it produces is only as honest as the per-trade averages it leans on. For plumbing, HVAC, and electrical — the three trades the trade pages cover — we publish a small set of proof bullets on /plumbing, /hvac, and /electrical, and those numbers are what carries the formula into a defensible monthly figure for your vertical. The calculator gives the formula, the trade pages give the per-vertical numbers, the audit gives the per-shop numbers.
These are not invented stats. They are the cross-trade averages the install is tuned against, drawn from the trade-page 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 post leans on exactly that chain — and where it diverges from your shop, the audit fills it back in from your last quarter's invoices.
The same numbers above appear, in different shapes, across the rest of the funnel. The playbook on /resources/missed-call-recovery-playbook walks the 3-touch SMS cadence that turns that recovered-call slot into a confirmed booking on whichever dispatch board the shop already runs — and a booking that doesn't land is a call Holdfast doesn't get paid on. The per-shop worked example on /pricing shows how the bonus bills against the booking, not against the recovery, so the math lines up for both sides of the invoice.
If your shop is the kind that has its own call log and ticket history ready to walk, the audit-request intake is the fastest next step — a 20-minute audit pulls ten of your recent inbound calls and your last quarter's ticket values to fill the same inputs from real numbers. No install, no commitment, the same per-shop sheet the pricing page walks through.
See it on your own calls
A 20-minute audit uses ten recent inbound calls and your last quarter's ticket values to walk through the same missed-call-recovery math for your shop — no install, no commitment.
See also
Methodology
Last reviewed: 2026-08-15. The math in this post is the same formula the calculator and the per-trade routed calculators publish, run against a working-average Chattanooga shop — 80 weeklyCalls, 25% missedRate, $480 average ticket, 55% close rate. The per-trade proof bullets are pulled from /plumbing, /hvac, and /electrical, and the same numbers feed the per-trade routed calculators so the formula and the trade pages cannot drift.
Voice.One paragraph per claim, plain prose, no per-minute framing and no meter. The miss rate is acknowledged as a working average, not a guarantee — actual shops swing from below 10% on a quiet Wednesday to above 35% during a Tuesday afternoon HVAC spike. The audit-request form is the place to ask for the per-shop reshape; this post is the place to read the math against a working-average shop. The analysis itself doesn't drift; the per-shop tuning does.