The most uncomfortable moment in a demo is not the sales dashboard. It is the retention screen, when an owner sees for the first time how many cancellation calls their office processed last month with no save attempt at all. Not a bad save attempt. None. The customer said "I want to cancel," and the person on the phone said "okay, no problem, thank you, bye," and closed the account. I have watched owners go quiet at that screen more times than I can count, and most of them say the same thing afterward: "I thought they were doing their best."
They probably were. Doing your best at a job nobody defined is still just processing a request. This post is about how to define it: what save rate actually means, why the number your office reports is probably inflated, what a save call should sound like, and how to measure it from recordings so you stop guessing.
What save rate is, and the trap most offices fall into
Save rate is saves divided by cancellation requests. A save is any outcome where the customer stays on a recurring plan: they keep the service, they downgrade frequency, or they pause for a season and come back. A cancellation request is any call, text or email where a current customer asks to end service.
That denominator is where it goes wrong. Most offices count cancellation requests by looking at what got logged as a cancellation in FieldRoutes. But a cancellation that got saved often never gets logged as a cancellation request at all. The rep talked the customer into a pause, changed the frequency, and moved on. So the log shows the ones that were lost, and the saves are invisible. Run that math and you get a save rate near zero, which is obviously wrong, so nobody trusts it, so nobody tracks it.
The opposite failure is just as common. A CSR marks a cancellation as "saved" because the customer agreed to a pause, and then the pause quietly turns into a cancellation ninety days later when nobody follows up. That one shows up as a win in the weekly report and a loss in the annual revenue.
The only honest denominator is every call where a customer asked to stop service, whether or not anyone logged it. The only honest numerator is accounts that were still active on a recurring plan sixty or ninety days later. Both of those require looking at the calls themselves, which is the whole problem.
The retention math
Here is why this matters more for pest control than for almost any other home service. A recurring pest account is an annuity. Take a quarterly customer paying somewhere around $120 a visit. That is roughly $480 a year, and a good chunk of that is margin once the route is dense, because the truck was already on the street. If that customer stays three years, which is not unusual for a general pest plan, you are looking at well over a thousand dollars of revenue from one account you already own.
Now compare that to what it costs to replace them. Operators I talk to put customer acquisition cost somewhere between $75 and $150 for a new residential customer, depending on market and channel. Door to door companies often run higher once you count the rep commission. Those numbers move around and I would not treat any of them as gospel, but the shape holds: a new customer costs you real money before you have collected a dollar, and a saved customer costs you one phone call.
Put it together for a mid-sized company. Say you get 80 cancellation requests a month in the off-season and more in the fall when the door knockers show up. If your office saves 10% of them, that is 8 accounts. If a coached office saves 30%, that is 24. The difference is 16 accounts a month, and at roughly $480 a year each, that is somewhere around $90,000 in annual recurring revenue kept, from calls that were going to happen anyway. Your numbers will be different. Do the math with your own. It is rarely small.
Why cancellations go unsaved
When I ran inside sales I assumed unsaved cancellations were a skill problem. Some of it is. But after looking at a lot of cancellation calls across a lot of companies, it comes down to three causes, and skill is the least of them.
Nobody is listening
A cancellation call is the one call type almost no manager ever reviews. Sales calls get listened to because there is a leaderboard. Cancellations get processed and forgotten. If you have virtual assistants or an overseas team handling service calls, this is doubly true: they are often measured on handle time and ticket volume, and a fast, polite cancellation scores perfectly on both. The behavior you see is the behavior you measure, and most offices measure nothing here.
There is no script
Ask your CSRs what they are supposed to say when someone cancels. If the answer is "try to keep them," that is not a script. A rep with no script defaults to the path of least resistance, which is agreeing with the customer. Saying "no problem" is easier than asking why, and asking why feels rude if nobody has told you it is your job.
There is no incentive
Sales reps get paid on closes. Who gets paid on saves? At most companies, nobody. A save is more valuable than a new sale, since it has no acquisition cost, and it is the one outcome on the phones with no bonus attached. I am not saying you need a commission plan for retention. I am saying that if a save and a cancellation pay the same, do not be surprised when the office treats them the same.
What a save call should sound like
This is the structure we teach. It is five steps, it fits on an index card, and a new CSR can run it on day two.
1. Acknowledge
The customer called expecting a fight or a runaround. Take that off the table in the first sentence. "I can absolutely help you with that. Before I do, can I ask you a couple of quick questions so I make sure we take care of you the right way?" Almost everyone says yes, and you have earned the next two minutes.
2. Find the real reason
The first reason given is rarely the whole reason. "We are moving" sometimes means moving across town, which is a transfer and not a cancel. "It is too expensive" often means "I have not seen a bug in six months and I forgot what I am paying for." "We are going with someone else" in August usually means a door knocker offered a first-service deal yesterday. Ask one more question than feels comfortable. "Got it. Was there something about the service that fell short, or is it more about the cost?"
3. Offer the fix that matches the reason
This is where scripts fail if they only have one move. A price objection gets a frequency change or a loyalty rate, not a free service. A service complaint gets a free re-treat with a specific tech and a follow-up call, not a discount. A door-knocker offer gets a reminder of the guarantee and what the customer already has that the new company does not, like a tech who knows the property. If your reps have three fixes and know which reason each one matches, they will save more than reps with one big discount they throw at everything.
4. Pause instead of cancel
When the fix does not land, do not go straight to cancellation. "Rather than closing the account, what if I pause it through the winter and we check in with you in March? No charges in between, and your rate stays locked." A paused account is a customer you still have permission to call. A cancelled one is a win-back campaign, and those close at a fraction of the rate.
5. Confirm
Whatever the outcome, say it back. "So I have you paused until March 15, and you will get a text from us the week before." Or, if they are leaving: "I have cancelled the plan effective today, and your guarantee still covers you through the end of the current service period." The confirmation is what makes the outcome real in FieldRoutes and what makes the customer feel finished. Skip it and the pause becomes a dispute in April.
How to measure it from your call recordings
You can do this by hand for a month and learn more than any report has told you. It is tedious, which is why nobody keeps it up, but the first pass is worth doing yourself so you believe the numbers later.
Pull every recording from the last thirty days where a current customer asked to stop service. Do not start from the FieldRoutes cancellation list, for the reasons above. Start from the phone system, listen to service calls, and tag the ones that were cancellation requests. For each one, record four things in a spreadsheet:
- Who took the call. If your reps share a login, this is the moment you discover why that is a problem.
- Was a save attempted, yes or no. Be strict. "Are you sure?" is not a save attempt. Asking for the reason and offering something is.
- The outcome: kept, downgraded, paused, or cancelled.
- The reason category. Price, service issue, moving, competitor offer, no longer needed, other. Keep it to six or so or the data becomes mush.
After thirty days you have four numbers that matter. Save-attempt rate, which is the share of cancellation calls where anyone tried. Save rate, overall and per rep. The reason mix, which tells you whether your problem is pricing, a bad tech on one route, or a competitor blitz in one zip code. And a sixty-day check on the "saved" accounts to see how many are still active.
The save-attempt rate is the one to look at first. In most offices that have never measured it, it is the shocking number. You cannot coach a save rate up if half the calls never had an attempt. Fix the attempt rate and the save rate usually follows on its own, because it turns out a fair number of customers were open to staying and nobody asked.
Doing it automatically
The manual version works for a month. It does not work for a year, and the reps figure out within a week that you stopped listening. This is the problem Plaibook's retention dashboard is built for. Every service call is transcribed and tagged, so a cancellation request gets identified from what the customer said rather than from what the rep logged. Each one gets scored on whether a save was attempted, which steps of your save script the rep hit, the outcome, and the reason category. Nobody enters anything by hand.
The part that makes owners trust it is that FieldRoutes stays the source of truth. The transcript tells us a customer asked to cancel and a rep offered a pause. FieldRoutes tells us whether the account is actually still active, on what frequency, and whether it is still active sixty days later. When those disagree, FieldRoutes wins, and the disagreement itself is useful, because it usually means a rep marked something saved that was not. The result is a save rate you can put in front of the team, by rep and by reason, that reflects accounts and not intentions. More on how the scoring side works is on our call scoring page.
A note for door-to-door companies
If you sell door to door, this is the metric that decides whether the summer was profitable. You paid a rep to knock, you paid the first-service discount, and the account only pays you back over the following year. Every fall, when the competing crews are out and the customers who signed in June start getting their second and third bills, the cancellation calls spike. The offices that save 30% of those calls keep their summer. The offices that process them politely give it back. I have a separate page on what this looks like for door-to-door companies, but the short version is that retention is the second half of the sale, and it happens on the phone.
Start with thirty days of calls and a spreadsheet. Count the attempts before you count the saves. Then decide whether the problem is listening, scripting or incentive, because the fix for each one is different and only one of them is training.