Most local businesses know they miss calls. Fewer know what those calls are worth, which makes it hard to decide whether answering them deserves attention this quarter. The arithmetic below takes about ten minutes with two numbers you almost certainly have: average job value and an honest count of calls nobody picked up. The method is deliberately conservative, so the result is a floor rather than a sales pitch.
Start with the value of one job
Take last year's revenue and divide it by the number of completed jobs. If your work ranges from a small repair to a full system replacement, run the figure separately for each service line. A missed drain clearing and a missed replacement estimate are not worth the same thing, and averaging them together hides the calls you most want back.
For each line, write down the average ticket and then the value of a first-time customer over the length of a relationship. A customer who calls once for a repair and returns twice more in three years is worth several times the first invoice. Keep both numbers visible, because the first makes the case and the second shows why one unanswered call deserves a process rather than an apology.
Count the calls you never answer
Open your phone system's call log for a normal week and look for three patterns: calls that rang with no answer, calls that landed in voicemail, and calls that came in outside your posted hours. Most owners are surprised by the after-hours figure, which is usually larger than expected in trades and smaller than expected in retail.
If your system does not keep a log, count the hard way for one week. Ask everyone who answers the phone to mark a tally each time a call rings out during a job. Add the voicemails that never got a callback. One week of counting is enough to build the estimate, and the exercise usually changes how the front desk treats the phone before any software is involved.
Apply a conservative close rate
Not every caller becomes a customer. Use a rate you would defend in front of your own team, not the best month you ever had. For service work, thirty percent of answered inquiries turning into a booked job is a reasonable planning number; for estimate-driven work like remodeling or roof replacement, twenty percent is safer.
Now multiply: missed calls per week, times the percentage of callers who would have booked, times average ticket. The answer is what a single week of silence costs you. Multiply by four for a month. If the number makes you uncomfortable, that discomfort is the point. It also means the fix has a budget far larger than the subscription that solves it.
The costs the invoice does not show
The lost job is the easy part. A caller who never reaches you also never sees the review request that follows a completed visit, never becomes the referral that mentions your name at a neighbor's cookout, and never returns for the next problem. In service businesses with long customer lives, the second and third jobs often outweigh the first.
There is a reputational cost as well. A customer who called twice and heard nothing does not think of you as busy. They think of you as unreliable, and they say so when someone asks for a recommendation. Those conversations are impossible to measure and impossible to get back.
Why after-hours calls cost the most
Calls placed outside business hours tend to be urgent. A burst pipe, a dead furnace in January, a shop shutter that will not lock. Urgency means the caller is already dialing the next name on the list before your voicemail finishes playing, and it means they are far less price-sensitive than a person comparing quotes during a quiet afternoon.
That combination makes evening and weekend calls the most valuable calls you receive and the easiest ones to lose. If your phone strategy has a single gap to close, it is this one. A live answer at nine in the evening is a differentiator in a category where the default outcome is voicemail.
What to fix first, in order
Start with missed-call text-back, because it is the cheapest and fastest change: when a call goes unanswered, the caller gets a message within seconds that acknowledges the call and asks what they need. It does not answer the phone, but it stops the silence that sends people elsewhere. Add after-hours live answering once text-back is running reliably.
Then measure. Track four numbers each month: calls received, calls answered, texts sent, and jobs booked from text replies. Compare them with the month before you changed anything. The goal is not a perfect answer rate; it is a falling ratio of missed calls to booked work, with a number you can point at when someone asks whether any of this was worth paying for.
A worked example on a two-person team
Take an electrical contractor with an average job value of four hundred and twenty dollars and about forty calls a week. Assume five of those calls go unanswered during jobs or after hours, and that only thirty percent of those callers would have booked. Five calls times thirty percent times the average ticket is six hundred and thirty dollars a week, or roughly twenty-five hundred dollars a month.
Now add the relationship. If a third of those recovered customers return twice in three years, the same five weekly calls are worth several times the monthly figure over the life of the business. That is the number to bring to a conversation about hiring or software, because it is built entirely from figures the owner already knew before reading anything.
What good looks like after ninety days
Three months in, the phone log should tell a different story: a lower ratio of unanswered calls, a text sent within seconds of every missed call, and a handful of jobs each month that trace back to a text reply rather than a conversation. If none of that is visible, the business bought a tool rather than changing a habit.
Write the three numbers where the team can see them: calls answered, texts replied to, jobs booked. Numbers people can see get attention, while dashboards only the owner opens do not. That visibility is what stops an answering strategy from quietly decaying back into voicemail six months later.
