Who Follows Up on the Old Systems My Techs Find?

Who follows up on the old systems your techs find? Think about last Tuesday. One tech ran a no-cool call on a 15-year-old condenser with a rusted base and a compressor on its last legs. Another did a capacitor swap next to a furnace older than his apprenticeship. Both mentioned it to the customer in passing. Both said something like "you're probably looking at replacement in a year or two." Then they drove to the next job. Nobody wrote it down, nobody called that customer back, and when that unit quits on the hottest weekend of July, the customer will call whoever answers first. That is a replacement job you were standing in front of and let walk.

Why it lives in the tech's head and stays there

This is not a tech problem. A tech's job on a call is to fix the problem, keep the customer comfortable and get to the next stop. Noticing an old system is automatic for him. Recording it is extra work at the end of a long day, with no obvious place to put it. So it stays in his memory, and memory does not hold up. He might tell you about it in the shop on Friday. He might mention it to the dispatcher. More likely it fades by the time the next ten calls have stacked on top of it. Meanwhile the owner, spouse or office person who could actually follow up never hears about it at all. The information exists. It just never makes it to the person who can act on it.

Step one: decide what counts as a flag

You can do this without buying anything. Start by agreeing on what is worth flagging, so techs are not guessing. Keep it to a few things: the age of the unit (data plate or serial number), the brand and model, what condition it is in, and anything the customer said about it, such as noise, uneven rooms, rising bills or a repair they already paid for last year. Then give it a simple rating your techs can say in one word. Something like: fine, watch, or replace soon. "Watch" means it is old but running. "Replace soon" means you would not be surprised by a failure this season. Three levels is plenty. If a tech has to think hard about the label, it will not get used.

Step two: capture it before he leaves the driveway

The flag only counts if it is captured on the job, not at the end of the day. Pick one place where it goes and make it the same place every time: the ticket notes, a required field, a text to the office, whatever your shop already uses. The tech does not need to write a paragraph. Age, brand, rating, one line of what the customer said. Takes about a minute. Skip the pitch on the roof. A good line for the customer is: "This unit is getting up there. I'm making a note so we can check in with you before it becomes an emergency." That is honest, it is not pushy, and it gives you permission to call back later.

Step three: put one person on the follow-up

A list nobody owns is just a longer version of the problem. Name one person who owns the flagged systems: you, your spouse, the CSR or the dispatcher. Give them a regular slot, even if it is just an hour on a slow Thursday. When the schedule is thin, that list is the first thing you work. Sort it by rating first, then by age. Start with the "replace soon" units, then the "watch" units that have not been looked at in a year. The call is simple: "Our tech was out in the spring and noted your system is getting older. Do you want us to come take a look and give you numbers so you are not caught off guard?" For many customers, a replacement quote is a conversation worth having at a few thousand dollars; for a lot of installs it lands somewhere between $5,000 and $12,000 depending on equipment and the home. A free look or a tune-up in the $100 to $300 range is a lighter first step that gets your tech back inside the house.

Step four: keep the loop closed

Every flagged unit should end in one of three places: scheduled for an estimate, scheduled for a tune-up or maintenance visit, or a dated note to ask again later. If a customer says not this year, that is fine. Write down when to ask again. The mistake is letting the flag sit with no next step. Check the list monthly and look for units that have been flagged for a long time and never touched. Those are the ones you will be sorry about in August.

Where CallFundr fits in that flow

This is the exact pileup CallFundr is built for. It is more than an AI receptionist: it runs the whole loop of Answer, Capture, Dispatch, Update and Follow Up. The flag your tech finds is a Capture problem, because the information has to land on the customer's record instead of in someone's head. The slow-day calls are a Follow Up problem, because somebody has to work the existing customer base for maintenance, tune-ups, off-season work and replacement opportunities. CallFundr works that base so it does not depend on whoever remembers. Our page on replacement opportunity tracking shows how that flows.

Fitted around how your shop runs

Your techs do not all work the same way, and your office does not either. That is why Jim Martin, who ran an HVAC operation for 25 years, fits CallFundr around how each shop actually operates: the right system is built around the operation, not the operation around the system. The team stays in control. CallFundr backs up the owner, spouse, CSR or dispatcher, so jobs do not slip away when things pile up, and a 15-year-old unit does not slip away either. If you want to see how the full flow works, start with how it works.

So, who follows up on the old systems your techs find? Right now, it may be nobody. It can be a named person, a simple flag and a slow-day list, with CallFundr working the follow-up behind them. See how replacement opportunity tracking keeps those units from walking out the door.