Use your own numbers
Start with one month of phone records. Count inbound calls that rang out, reached voicemail, or arrived while your team was already helping someone. Remove spam, wrong numbers, and repeat calls about an open job. Keep first-time callers separate from existing customers.
Then estimate the value of the opportunity. Multiply unanswered qualified calls by the share of answered inquiries that become customers, then by the average first-job value. This is a rough opportunity estimate, not guaranteed lost revenue: some callers will try again, and some inquiries will not fit your service.
A worked example, not a benchmark
Suppose your log shows 20 unanswered qualified inquiries in a month. If your own records show that 3 in 10 answered inquiries become jobs and a typical first job is worth $450, the estimated monthly opportunity is 20 × 0.30 × $450, or $2,700. Change the inputs to match your business. Do not treat this example as an industry average.
Count the calls that matter
Track the caller's reason, whether a person answered, whether the caller left a message, how quickly someone followed up, and the outcome. A short reason code such as booking, quote, urgent service, existing job, or other is enough to start. Avoid collecting more personal information than your team needs.
SCORE advises small businesses to prioritize phone coverage and follow up quickly when a call is missed. Its article reports that roughly six in ten calls to small businesses go unanswered. Treat that figure as a broad warning from SCORE, not a forecast for your shop; your call records are the better baseline.
Compare the cost of a fix
Test a change for a defined period. It might be call forwarding during busy hours, a rota for callbacks, an answering service, or automated intake for routine questions. Compare qualified calls answered, callbacks completed, appointments booked, and revenue collected before and after. Include the cost of the tool and the time your team spends reviewing its work.
Keep a person available for exceptions. A caller with an emergency, a complaint, or a complex request needs a clear path to someone who can make a decision. Automation is useful when it captures the reason for the call and routes it accurately; it is not a substitute for judgment in every conversation.
A simple weekly review
Once a week, review the unanswered call list and label each outcome. Look for patterns by time, day, and call type. If the same hour repeatedly creates a backlog, adjust coverage there before paying for all-day capacity. After four weeks, compare the results with the previous month and decide whether to keep, change, or stop the experiment.