The Callback Tag: how to track callbacks and warranty returns

The three moves

The Callback Tag is a simple way to track callbacks and warranty returns so each one teaches you something instead of just costing a free truck roll. It has three moves, in this order:

1. Tag it. Every return visit is tagged to the original job it came from, with a few fixed fields.
2. Check the steps. The service manager checks each step the tech followed on that first visit, finds the one that was skipped, and fixes the step, not the person.
3. Watch the clock. Every new install gets a manufacturer registration deadline on a tracker, because some warranties depend on it.

Below are the tag fields to copy, the step check and the registration tracker.

Who this is for

HVAC, plumbing and electrical companies that do return visits at no charge, whether they call them callbacks, recalls or warranty calls, and that install equipment with manufacturer warranties. If you can't answer "which installs came back last quarter, and why?" in a minute, start here. It's the same work Cortex describes under warranty and callbacks.

Why the tag matters

You'd think a callback means a bad tech. ServiceTitan's contractor playbook points somewhere else: most recalls result because of a process issue, and every time one happens you should check each step the technician followed. The same playbook notes that most businesses treat problems within 30 days of a service call, or within one year of an install, as recalls. You can only see the process issue if the return visit is linked to the first job. Otherwise each callback looks like a new, unrelated call.

Some software already does the linking. In ServiceTitan, a recall job is a return visit for a problem that persisted after a completed job; it is automatically no-charge, marked with an R next to the bill-to name, and links back to the original job. Only completed jobs can be recalled. If your software doesn't have this, a field on the job and a shared spreadsheet do the same thing.

What you need first

• A way to link a new job to an earlier one (a recall job type, a parent job field, or the original job number in a custom field).
• A written checklist for your common job types (install, repair, maintenance). The step check compares against it.
• A service manager (or owner) who reviews tags once a week.
• The registration rules for the equipment brands you install.

Tag it (move 1)

Every return visit gets these tag fields, filled in by the CSR when it's booked and finished by the tech on site:

Tag field	What goes in it
Original job number	The job this visit came from
Original date and tech	When it was done and who did it
Job type	Install, repair or maintenance
Days since original	Counted from the original completion date
Customer's words	What the customer said is wrong, in their words
What the tech found	The cause, one line
Step that failed	The checklist step (filled in by the service manager)
Charge	No charge, or billed with a reason
Parts used	Parts and cost, even when no charge

Two rules: a return visit inside your recall window always gets a tag, and a tag is never deleted. If it turns out the callback was a new, unrelated problem, the tag stays and says so.

Check the steps (move 2)

Once a week, the service manager opens every new tag and the original job side by side, and walks the checklist for that job type. The question is "which step was skipped or done differently?", not "who messed up?".

A worked example, with demo data: an AC install on June 12 comes back on July 2 with "no cool, warm air". The install checklist has four steps: set the line set and pull a vacuum, charge to the manufacturer's spec, check the charge after a 15-minute run, and walk the homeowner through the thermostat. The notes show step 3 wasn't done. The fix is to make step 3 a required item in the install sign-off, for every tech. That's what "fix the step, not the person" means.

When the same step shows up on two or more tags in a month, it goes to the next team meeting. An AI agent can do the sorting: it reads new tags, matches each against the checklist, groups repeats and drafts the weekly summary for the service manager to review. It never changes a checklist or blames a tech by itself.

Watch the clock (move 3)

The quietest warranty problem isn't a callback at all. It's an install that was never registered. Trane, for example, offers its Registered Limited Warranty only for products registered within 60 days of installation, covering parts for 10 years in most cases; products registered late or not at all get the Base Limited Warranty, in most cases 5 years on parts. Neither covers labor. Lennox also requires equipment to be registered within 60 days of installation for existing homes, or of closing for new construction, with exceptions in places like California and Quebec where registration requirements aren't allowed. Rules differ by brand, product and state, so check each brand you install.

The registration tracker (one row per install):

Field	Example (demo data)
Job number	3920
Customer and address	Brandt residence
Brand, model, serial numbers	Trane outdoor unit and coil, serials from the job photos
Install date	Jun 12
Registration deadline	Aug 11 (60 days)
Who registers	Office, or customer with your help
Registered on	date
Confirmation saved	link or file

Sort the tracker by deadline every Monday. Anything within 14 days of its deadline and not registered goes to the top of the office's list. An agent can fill the tracker from completed install jobs and draft a reminder for the office, which a person approves before anything goes to the customer, the way Cortex keeps a person in charge of every send.

What to watch out for

• Untagged returns. A tech who swings by "while in the area" creates an untracked callback. The tag rule covers those too.
• Blame. If tags turn into a scorecard for techs, they stop getting filled in. Review steps, not people.
• Missing serials. Registration needs model and serial numbers. Make a photo of the data plate a required step at install.
• Labor. Manufacturer parts warranties don't pay for your labor on the return visit. Track parts and labor on every tag so you see the real cost.

How to tell it's working

Each month, look at three things: how many return visits came in, how many had the same failed step as an earlier tag, and how many installs passed their registration deadline unregistered. The second number tells you whether fixes are sticking; the third should be zero. For help setting this up inside your own software, start with your free AI Operations Audit.