A tech drives back out on Thursday afternoon to re-treat a kitchen. Forty minutes on site, twenty minutes of driving that wasn't on anybody's route plan. No invoice is written. No ticket gets a dollar amount. Nothing about that trip will appear anywhere in your financials, ever.

It still happened, and it still cost you about $36, and it came out of an account that produces $63.25 of gross profit on a good visit.

Most shops track callbacks as a service-quality metric, if they track them at all. It belongs on the cost side of the business, because that is where it lands.

The stop your books cannot see

Every other cost in your operation eventually names itself. Chemical shows up as a vendor bill. Fuel shows up on a card statement. A tech's hours show up in payroll. A callback shows up as all three, blended into route cost, with nothing to attach it to.

Price it out on the standing example this site uses. A $30 loaded field hour, which is a mid-range figure for a licensed tech with taxes, workers' comp, and benefits on top of wage, not a benchmark. Sixty minutes of tech time on a callback is $30 of labor. Add roughly $6 of product. Call it $36 of direct cost, and treat that as illustrative, because your loaded hour is knowable and mine is a guess about your business.

Now put that against what the account earns. A $115 quarterly service at a 55% gross margin, which is the top of the healthy range for a pest operation per NPMA industry data and PCO Bookkeepers guidance, produces $460 of revenue a year and $253 of gross profit, or $63.25 per visit.

One callback consumes 57% of a visit's gross profit. That is the whole finding, and it is not on any report you own.

The same account at three callback rates

Run one account through a year at three different levels of unscheduled return work:

  • No callbacks. $460 of revenue, $207 of cost of service, $253 of gross profit at a 55% margin. The number you think you're running.
  • One callback. Add $36 of cost. Gross profit falls to $217, and the margin on that account is 47.2%.
  • Two callbacks. Add $72. Gross profit falls to $181, and the margin is 39.3%.

A 55% account that generates two callbacks a year is a 39% account. Same customer, same price, same route, nearly sixteen points of gross margin gone into work you already agreed to do for free and never counted.

It is a six-visit account priced for four

That is the clearer way to hold it. You built the price around four scheduled services. If the account reliably pulls two returns, you are delivering six stops and collecting for four.

Revenue per stop delivered drops from $115 to $76.67. Nobody in your operation would sign a $76.67 quarterly account on purpose. Plenty of shops have a few dozen of them and have never seen it, because the price on the agreement still says $115 and the extra stops never made it into a system that counts.

What an 8% callback rate costs a five-truck shop

Move up from the account to the fleet, because the second cost is bigger than the first and it isn't measured in dollars.

Five trucks at 13 stops a day, 250 days a year, put 16,250 scheduled stops on the calendar. At an 8% callback rate, meaning eight return trips for every hundred scheduled stops, that's another 1,300 trips a year nobody bills. One truck produces about 3,250 stops a year, so four tenths of a truck spends the entire year servicing your own warranty.

Cut that rate from 8% to 4% and you free roughly 650 stops. At $115 a stop that is about $74,750 of route capacity, without buying a vehicle, without a hire, without a single new customer.

Be precise about what that is: it is capacity, not revenue. It converts only if you have demand to put in it, which is why this belongs next to the decision to add a technician rather than in place of it. But if you are within sight of buying the fifth truck, find out how much of the fourth one is already doing free work before you sign anything.

The July callback and the January callback are not the same cost

Both burn $36 of labor and product. Their real cost is nowhere near equal.

In January the route has slack in it. The return trip displaces windshield time and a slow afternoon. In July the route is full, and every unscheduled return pushes a billable stop into next week or off the schedule entirely. The direct cost is identical. The opportunity cost is a $115 stop you could not run.

Which means the single annual callback rate is close to useless, for the same reason a single cancellation rate is. Look at it by month, and compare July to last July rather than reading a rolling twelve-month figure that blends your peak into your dead season and reports the average of two businesses you don't run.

If your callbacks cluster in the months your trucks are full, and in most of the country they do, then your callback problem is a capacity problem wearing a quality costume.

Callbacks are made at the sale, not at the visit that failed

The callback lands on the tech who serviced last. That tech is almost never the person who caused it.

Three things create most of them, and all three happen before the visit that gets blamed:

The over-promise at the sale. Somebody on the phone said "you won't see another ant." The customer saw an ant. The service worked exactly as designed and you now owe a truck roll, because a sales sentence set an expectation the chemistry cannot meet.

The initial run at route speed. The initial service is the one visit that genuinely needs double the time, and it is frequently slotted into a normal route day because a full day is a productive day. A rushed initial buys you three months of returns on that account, at $36 apiece, to save 30 minutes once.

Nobody described normal. Seeing activity in the days after a treatment is the treatment working, and the customer has no way to know that unless somebody says it out loud at the door. Left unsaid, the customer reads a working service as a failed one and picks up the phone.

None of that is fixed by coaching the tech whose name is on the last ticket.

There are two ways to lower the number, and they look identical on the report

You can fix the service, or you can stop the customer from calling. Both make the callback rate go down. Only one of them is good for you.

A tech who says "let's see how it looks by your next regular visit" just turned a $36 cost into a retention risk on an account worth $253 a year. If that customer is at visit two, they are still $190 underwater on the $250 you spent to acquire them, and a cancellation there costs you $186.75. You saved thirty-six dollars and put a hundred and eighty-seven at risk.

This is the reason a callback rate should never be a number a technician is graded on by itself. Grade the pair: callbacks and cancellations on that tech's book, together. A tech whose callbacks drop while their cancellations rise is not improving.

Your rate is one number hiding forty accounts

On a book of 800 quarterly accounts you run 3,200 scheduled stops. An 8% callback rate is 256 return trips, about $9,200 of direct cost.

Those 256 trips are not spread across 800 customers. They are concentrated in a few dozen. The crawlspace that needs an hour. The conducive condition the homeowner will not fix. The German roach job that got sold at a general pest price. The rental with a new tenant every spring.

So the useful output is a list of names, not a percentage. Rank accounts by returns over the last twelve months and look at the top thirty. Some of them need a different service plan, some need a construction conversation, and some need to be priced at what they actually cost to serve at renewal. If one of those cancels over the new price, that was the outcome you were going for.

Don't start charging for them

The obvious response to a $36 cost is to bill for it. Resist that on recurring accounts.

The free re-service is most of what you sold. It is the reason the customer is on a plan instead of calling somebody once a year, and billing $89 for a return visit on a $115 quarterly account is a very efficient way to convert a $36 cost into a lost $253 annuity plus the $250 you'll spend replacing it.

Price it in instead. If your real rate is 8%, then your service is 4.3 stops a year, not 4, and your pricing should carry that. A shop with a 4% rate can profitably sell below a shop with a 12% rate and both can look at the same price list and reach opposite conclusions about whether it works.

One-time jobs are a different question with a different answer, and the warranty window you print on the invoice is the whole negotiation.

I'm not going to give you an industry callback rate

You can find published re-service percentages. They cannot settle anything, because shops do not count the same event.

Some open a ticket for every warranty visit. Some let the tech absorb it on the next scheduled stop and never open one at all. Some count only customer-initiated calls, others count any unscheduled return including the ones the tech decided to make. Termite and WDO warranty work behaves nothing like quarterly general pest and gets blended into the same figure anyway. Two operations running identical service can publish 3% and 14% and both be describing their own counting rules more than their own work.

Yours is in your field software right now, and yours is the only one that changes a decision.

The ten-minute count

Pull last month's completed service tickets. Count the ones with no invoice attached, or typed as re-service or warranty. Divide by total stops for the month. Then run it again on July.

Multiply the count by your loaded hour, plus product, and you have the direct cost. Multiply the July count by your average ticket and you have the opportunity cost, which is the bigger of the two.

If your field software cannot produce that count, that is not a reason to skip this. That is the finding: you are running an unmeasured cost that scales with your route, and the first fix is making techs open a ticket for every return trip, priced at zero.

How to actually see it

Be clear about which system holds what, because this one splits cleanly.

The count lives in your field software. Service tickets, service types, visit dates, and which tech ran which stop are all over there, and a callback exists only as a ticket, so nothing in accounting will ever produce the number for you.

The cost side lives in your books, and that is the half most shops are missing. Connected to QuickBooks read-only, The Forecast reads your real gross margin and invoice-level revenue by customer, which is what turns a raw callback count into gross profit per visit and a loaded cost per field hour. It reads. It does not edit your books, and it does not move money.

There is also a fingerprint you can watch without any ticket data at all: revenue per account flat while field payroll and fuel per account climb. That pattern means you are delivering more stops for the same money, and unbilled return work is one of the few things that produces it.

On a bank-only connection you get cash flow, spending, and an estimated margin. A bank feed cannot see a service ticket, and it never knew the customer's name.

One caveat on every dollar above. If your reported gross margin sits well clear of the 50–55% band with field payroll still parked in operating expenses, the margin is overstated by 8 to 12 points. That makes gross profit per visit look bigger than it is, which makes each callback look cheaper than it is. Fix the account structure before you decide how much this is costing you.

Sources: gross margin range from NPMA industry data and PCO Bookkeepers guidance (50–55% healthy, roughly 58% average). Loaded labor rate, ticket price, product cost, stop counts, book size, and callback rates are illustrative; run the same arithmetic on your own numbers.