Missed-call cost calculator

What's a missed call actually costing you?

Put in how many calls you miss a week, the share that were a new job, and your close rate. This works out what's likely slipping past you: a week, a month, a year.

Everything runs in your browser. Nothing is sent anywhere and there's no email box.

The calls

There's no verified national figure for this, it depends entirely on how your phones are covered. Check your phone's missed-call log for a normal week and use that instead of the default.

That's more than one every working hour across a five-day week. The maths still runs, but double-check the number against your phone log.

Existing clients calling about work already underway aren't a lost sale. This is the share that were someone new, calling about work you don't have yet. An assumption, not a stat, until you check your own numbers.

The same 1-in-3 illustration used elsewhere on this site, not a measured industry figure. Swap in your own close rate if you track it.

The job
$

Prefilled at $3,000, the same illustrative figure used in the quoting post linked below. Use your own average.

That's an unusual average job value to run through this calculator. The maths still runs, but check the figure.
A month, on these numbers
$4,744

That's around 19 jobs a year that never got a call back, on these numbers.

A week$1,238
A year$56,925
Jobs a year, on these numbers19

A year is counted as 46 working weeks, the same count used on the ROI calculator: 52 less leave and stat days. All four inputs are assumptions unless you've swapped in your own numbers.

What this maths doesn't know

Two of these four numbers decide the whole result, and neither one is a stat you can look up. Here's where they can go wrong.

Not every missed call was ever going to be a job. Wrong numbers, spam, a supplier chasing an invoice, a mate ringing about the weekend. The share-of-new-job input tries to strip those out, and if you've never actually checked, it's a guess dressed up as an input.

The close rate assumes you'd have won it if you'd answered. Answering doesn't win every job; price and timing still matter. What answering does is get you into the running, which a missed call never does.

None of it counts the call that rang out and never tried again either. Someone who hits voicemail on a trade business often just rings the next name on the list. That caller isn't in this calculator at all, because there's no honest way to size how often it happens without a measured NZ figure, and I haven't found one worth citing.

The formula, and where the numbers come from

Calls you miss a week, times the share that were a new job, times your close rate, times your average job value, gives the money left on the table each week. Multiply by 46 working weeks for a year, divide by 12 for a month.

The close rate and job value defaults match the worked example in why trade tools automate the invoice but almost never the quote: 1 in 3, $3,000 a job. That post says plainly it's an illustration, not a citable NZ statistic, and the same is true here. The calls-missed and share-of-new-job defaults are plain assumptions with no source at all, because I couldn't find one worth trusting. Replace all four before you act on the result.

Cite the method freely. It's the formula worth citing here, not a specific number, since every input is an assumption you should replace with your own:

Missed-call cost calculator, Kove. kove.nz/missed-call-cost-calculator

Questions people ask

How do you work out the cost of a missed call?

Multiply calls missed a week by the share that were a new job, by your close rate, by your average job value. That's the money left on the table each week. Multiply by 46 working weeks for a year, divide by 12 for a month.

What close rate should I use?

Your own, if you track it. The 33% default is the same 1-in-3 illustration used in the quoting post on this site, not a measured NZ figure. It's there so the calculator has a starting number, not because it's true for your business.

Is every missed call really a lost job?

No. Some are wrong numbers, spam, or an existing client checking on work already underway. The share-of-new-job input tries to strip those out, but it's still an assumption until you've checked your own call log against what actually came in.

Why 46 working weeks for the year figure?

The same count used on the automation ROI calculator: 52 weeks less leave and stat days. It keeps the tools consistent and avoids overstating the annual number with weeks the business wasn't actually open.

Worth fixing how the phone gets answered?

Christchurch based, working remotely across New Zealand. If the fix is a $30 call-forwarding setting, that's what I'll say.