Plumbing
Service callback and warranty tracking field guide for contractors
Define a callback, separate it from a warranty claim, measure the callback rate by tech and type, code the root cause, and track what is under whose warranty so you bill right and recover the part.
Direct answer
A service callback is a return trip to redo work that should have been right the first time, on your dime. It differs from a warranty claim, where a part failed and the manufacturer owes the cost. Track the callback rate, classify callback versus warranty versus new problem, and claim the failed part. Your policy and the manufacturer terms control.
Key takeaways
- A callback is a return trip to redo work that should have been right the first time, on your dime; a warranty claim is a failed part the manufacturer owes.
- Acceptable callback rates run about 2 to 3 percent, top performers under 2 percent, weaker shops 3 to 8 percent; above 8 percent is a real problem.
- Three warranty clocks: your labor warranty (30 to 90 days on repairs, 1 year on installs), the manufacturer part warranty (1 to 10-plus years), and the manufacturer labor allowance.
- Code every callback before it closes with one of four root causes: workmanship, bad part, misdiagnosis, or rushed.
- Record model, serial, install date, and warranty term at install; no serial means no warranty claim, since manufacturers gate claims on serial and proof of install date.
What a callback is and why you track it
A callback is a return trip to fix work that should have been right the first time, on your dime. The truck rolls, a tech burns hours, and no invoice goes out at the end. It is not a new problem at the same address and it is not a part the manufacturer owes you. It is your work, coming back.
Untracked, a callback hides. It looks like a normal job on the board, the tech goes out, the customer is handled, and the only place the loss shows up is at year end when the labor numbers do not match the revenue. Tracking turns that hidden bleed into a number you can see, sort, and shrink. You cannot fix a callback rate you have never measured.
Warranty tracking is the parallel discipline, and it runs the other direction. A callback is money leaving because your work failed. A warranty claim is money you can recover, or a labor charge you can rightly bill, because a part failed under coverage. Knowing what was installed, when, and under whose warranty is what lets you bill correctly and claim the part instead of eating it. The two together, callbacks measured and warranties tracked, are what separate a shop that knows its quality and its costs from one that guesses. Pricing the original work is its own discipline, covered in the estimating guide, and a repair done right the first time starts with a real diagnosis, covered in the low-pressure guide.
A callback versus a warranty claim
These two get blurred constantly, and the blur costs money in both directions. A callback is your fault. The solder joint you sweated weeps, the trap you set leaks at the slip nut, the fixture you trimmed drips because the supply line never got snugged. Same issue, your workmanship, your cost to correct.
A warranty claim is a part that failed. The cartridge in a two-year-old faucet seizes, a water heater gas valve fails inside the warranty term, a recirc pump bearing goes. You installed it correctly and it ran fine, then the component itself failed. That is the manufacturer's defect, not your error, and the manufacturer owes the part and sometimes a labor allowance.
The test is simple to state and harder to be honest about: did the work fail, or did the part fail? Most shops define a callback as an error or omission by the tech, commonly inside 30 days of a service call or within the first year of an install. A part failure inside the manufacturer's term is a warranty claim. Classify it wrong and you either eat a cost the manufacturer owed you, or you bill a customer for your own mistake and lose them.
Why callbacks bleed the business
Callbacks hit three places at once, and the money is only the first.
The margin goes first. A callback is a free truck roll and free labor against a job you already closed. The fuel, the tech's hours, the parts to redo it, all of it comes straight off the profit of the original job, and sometimes off the next job the tech never got to because the day went to driving back. One callback can erase the margin on two or three clean jobs.
The quality signal is the second hit, and it is the useful one. A callback rate that climbs is telling you something is wrong upstream, in the training, the hiring, the parts you buy, or the schedule that has techs rushing. Read as data, a callback is the cheapest quality inspection you will ever get, because the customer ran it for free.
Trust is the third, and it is the slowest to come back. A customer who pays for work that fails does not call you for the next one, and they tell people. The callback you handle fast and free can actually keep that customer, because how you own a mistake says more than the mistake did. The callback you argue about loses them for good.
What is a good callback rate?
The callback rate is callbacks divided by jobs over a period, expressed as a percent. Industry surveys of residential service trades commonly put acceptable callback rates around 2 to 3 percent, with top performers running under 2 percent and weaker shops landing anywhere from 3 to 8 percent. Above roughly 8 percent is a problem you can feel in the bank account. Treat those figures as a benchmark, not a law, because how a shop defines and counts a callback moves the number as much as the actual quality does.
The headline rate is the least useful version of the number. The value is in the cut. Run the callback rate by tech and you find the one who needs retraining instead of blaming the whole crew. Run it by job type and you find the repair your shop is consistently getting wrong. Run it by part or brand and you find the cheap valve that is not actually saving you anything. A single company-wide percentage hides all of that.
Pair it with first-time fix rate, which is the share of jobs resolved on the first visit. A common target sits in the 70 to 80 percent range. The two move together: push first-time fix up and the callback rate falls, because the same disciplines, a real diagnosis, the right part on the truck, the work checked before the tech leaves, drive both.
Coding the root cause
A callback rate tells you how many. The root cause tells you why, and why is what you actually fix. Every callback gets a cause code before it closes, picked from a short list the office and the field both understand.
Four causes cover most of them. Workmanship is the joint that leaked, the fitting that was not square, the connection left loose. A bad part is a defective component that failed early, which often crosses over into a warranty claim. Misdiagnosis is the tech who fixed the wrong thing, swapped a part that was fine, and left the real fault in the wall. Rushed is the job that got squeezed by a schedule too tight to check the work, and it usually shows up as a cluster on the busiest weeks.
Coding is only worth doing if you act on the pattern. Three workmanship callbacks on the same tech is a training conversation, not a firing. A run of bad-part callbacks on one brand is a purchasing decision. A spike in rushed callbacks every time the schedule goes red is a dispatching and capacity problem, not a people problem. The code points you at the lever. Without it, every callback looks like bad luck, and you fix nothing.
Flagging the callback against the original job
The single move that makes everything else possible is flagging the work order as a callback and linking it to the original job. Not a fresh call typed in like any other. A callback, tied to the visit it came from.
Buried as a new call, a callback disappears into the schedule and your rate reads artificially clean. Worse, the tech who created it never sees it come back, the office never connects the two visits, and the cost looks like normal volume instead of rework. The link is what holds the original tech, the original work order, and the correction together so the pattern can surface.
This is where the tracking has to live in the system, not in a manager's memory or a sticky note. A field service tool like FieldOS lets you mark a work order as a callback and tie it to the parent job, so the original tech, the date, the cause code, and the redo cost all hang off one record. When you pull the callback report, every linked job is there with its cause, and the rate is real because nothing got buried as a new call. The discipline is cheap. The willingness to flag your own rework honestly is the hard part, and it is the whole game.
The three warranty clocks
Three different warranties run on every install, on three different clocks, and confusing them is how shops eat costs they did not owe. Know which clock you are on before you decide who pays.
Your labor warranty is the one you issue. It covers your workmanship, and on a service repair it commonly runs 30 to 90 days, while an install often carries a one-year labor warranty or longer depending on your policy and the local market. If the work fails inside that window, it is a callback and you cover it.
The manufacturer's part warranty covers the component against defects, and it runs far longer, anywhere from 1 year on small parts to 6, 10, or 12 years on a water heater tank, sometimes a lifetime on a faucet cartridge. That clock belongs to the equipment, not to your labor.
The third clock is the one most shops leave on the table: the manufacturer's labor allowance. Some warranties pay a set amount toward the labor to install a warrantied replacement, separate from the free part. It is usually a fixed dollar figure, not your full rate, and it is gone if you do not file for it. Read the actual warranty document, because these terms vary by manufacturer, by product line, and by whether the unit was registered.
| Warranty | Who issues it | Typical term | What it covers |
|---|---|---|---|
| Labor warranty | You | 30 to 90 days on repairs, 1 year on installs (your policy) | Your workmanship, the callback |
| Part warranty | Manufacturer | 1 to 10+ years (per product) | Defective component, replacement part |
| Labor allowance | Manufacturer | Tied to the part warranty | A set dollar amount toward install labor |
Your labor warranty versus the manufacturer's part warranty
Hold these two apart in your head and most billing questions answer themselves. Your labor warranty is a promise about your hands. The manufacturer's part warranty is a promise about their product. They fail differently and they pay differently.
When the work fails inside your labor window, that is a callback. You go back, you fix it, you charge nothing, because you sold the job and the workmanship is yours. When the part fails inside the manufacturer's term but your install was sound, that is a warranty claim. You claim the replacement part from the manufacturer, and the labor is either billable to the customer or partly covered by a labor allowance, depending on the warranty and what you told the customer up front.
The trap is the overlap early in a job's life. A faucet that drips a week after install could be your trim work or a defective cartridge. Diagnose which before you decide who pays. If it is your work, eat it. If the cartridge is genuinely defective, claim it. Guessing in the customer's favor every time trains your shop to absorb the manufacturer's defects, and guessing in your own favor every time loses customers. The diagnosis is what keeps you honest and whole at the same time.
Recording the equipment history
Warranty tracking only works if you wrote down what you installed when you installed it. Record the equipment, the model and serial number, the install date, and the warranty term, attached to the property and the customer, on the day the work is done. Six months or six years later, that record is the difference between claiming a part and eating it.
The serial number is the piece everyone skips and everyone needs. Manufacturers gate warranty claims on serial number and proof of install date, and the labor-allowance forms ask for the model and serial of both the failed unit and the replacement. No serial, no claim, and you find that out on the phone with the manufacturer while a customer waits.
This is exactly the kind of detail that belongs in the system, not in a folder of install paperwork nobody can find. A field service tool that keeps an equipment history on the property record puts the water heater you set, with its model, serial, install date, and warranty term, right there at the next visit. The tech pulls up to a no-hot-water call and already knows the tank is four years into a six-year warranty before the truck stops. That is the moment the record pays for itself, and it only exists if someone captured it the first time.
Claiming the part and the labor allowance
When a part fails under warranty, claim it. The cost of that replacement belongs to the manufacturer, and a shop that quietly buys a new part off the shelf and installs it is donating money to the supplier. This is recoverable cost, and over a year it adds up to real dollars.
The claim runs on documentation. Manufacturers want the model and serial of the failed unit, proof of the original install date, the defect, and on a labor claim, your invoice for the work performed referencing both the old and the replacement unit. Miss a field and the claim stalls. This is why the equipment history matters: a complete record turns a claim into a form you fill out in minutes instead of an afternoon of phone calls and digging.
File the labor allowance when the warranty offers one, even though it rarely covers your full rate. A partial recovery beats zero, and the difference between the allowance and your real labor cost is a number worth knowing, because it tells you what the warranty job actually costs you to perform. Some shops bill the customer the gap above the allowance, which is fair when the customer was told the labor was not free under the part warranty. What you do not do is perform warranty labor for nothing and never file. That is leaving money on the manufacturer's table by default.
Who pays for a callback?
Classify the visit first, then bill it, and the three cases each pay differently.
A true callback is no charge. Your work failed inside your warranty, so the correction is on you, full stop. Billing a customer for your own mistake is the fastest way to turn one bad joint into a lost account and a review that costs you the next ten calls.
A warranty part is a split. The part comes free from the manufacturer, and the labor is either billed to the customer or filed against the labor allowance, depending on the warranty and what the customer agreed to. The honest version sets the expectation up front: the part is covered, the labor to swap it is not always covered, here is what that costs.
A new problem is a new job, and you bill it. A customer whose water heater you serviced last month calling about a leaking toilet in the other bathroom is a new call, diagnosed and invoiced like any other. Being honest enough to find a genuine new problem and bill it is as important as being honest enough to eat a real callback. Eat the callbacks you own, claim the parts you are owed, and bill the work that is genuinely new. The whole skill is putting each visit in the right bucket before the invoice goes out.
Is it a callback or a new problem?
Before any of the billing logic works, you have to answer one question honestly: is this the same issue you were already there for, or a genuinely new one?
Same issue is a callback. You cleared a kitchen drain and it is backing up again in two weeks, that is the same fault, and the odds are you cleared the clog without finding the cause. The grease is still in the line, or the belly in the pipe is still there, and the snake bought you ten days. New problem is a different fault. You replaced a wax ring and the customer calls about low pressure at the kitchen sink. Different fixture, different system, different call.
The honest read is occasionally against you and occasionally for you, and a real pro calls it both ways. The customer who insists the new leak under the sink is your fault when you only ever touched the water heater needs to see, calmly, that these are unrelated. The customer who thinks they owe you for a re-clear that is plainly your incomplete first visit gets it free. The record of what you actually did on the original visit is what settles it, which is one more reason the original work order has to be specific about scope. Vague notes turn every gray area into an argument you lose.
Feeding callbacks back to training
Callback data is worthless if it dies in a report. The point of coding the root cause is to send it back to the place that fixes it, which is usually training and process, not punishment.
Run the callback report by tech and the workmanship patterns stand out. One tech with repeat solder failures needs a morning at the bench, not a write-up. A tech whose callbacks are all misdiagnosis needs help with the diagnostic process, maybe a checklist or a ride-along, because they are fixing symptoms and missing causes. The data names the gap so the training hits the right thing instead of a generic toolbox talk nobody needs.
Some patterns are not about the tech at all. If every tech is generating the same callback on the same task, the problem is the standard, the part, or the procedure, and the fix is a shop-wide change to how that job gets done. If the callbacks cluster on the weeks the schedule was overloaded, the fix is capacity and dispatching. Used this way, the callback rate becomes a continuous quality program that costs you nothing extra, because the customers already paid for the data by experiencing the failures. The only question is whether you read it.
Owning the callback fast and free
How you handle a callback decides whether you keep the customer. The failure already happened. What is still in your control is the response, and the response is what they remember.
Own it fast and own it free. A callback handled the same day, with no argument about who pays, can leave a customer more loyal than a job that went perfectly, because they have now seen what you do when something goes wrong. That is the part of your reputation you cannot buy with advertising. The shop that says we got it wrong and we are on our way keeps the account. The shop that makes the customer prove it, or slides a charge onto a mistake, loses them and earns the review that warns everyone else.
Speed matters as much as the free part. A callback that drags for a week, with missed windows and a customer chasing you, does the damage even if you eventually fix it for nothing. Flag callbacks as priority in the schedule, get them handled, and close the loop with the customer. The cost of doing that is small against the lifetime value of an account and the cost of replacing it.
Tracking warranty expiration to stay ahead of it
A tracked warranty earns its keep past the claims desk. It is a sales and service signal, because knowing when coverage runs out tells you when to reach out before the customer has a cold-water emergency.
When you can see that a water heater is in year five of a six-year warranty across your customer base, you have a list of conversations worth having. Offer the planned replacement before the tank fails on a Sunday and floods a finished basement. Offer the service agreement that catches the failure early. The customer who replaces on your schedule, with the old unit's warranty understood, is a far better outcome than the one who calls a competitor in a panic when the tank lets go.
This is straightforward to run when the equipment history lives in the system. A field service tool that holds install dates and warranty terms on the property record can surface the units coming up on expiration, so the proactive call is a report you pull, not a memory you hope someone has. Pricing the replacement and the agreement is the estimating side of the work, covered in the estimating guide. The tracking is what tells you who to call and when, which is the part most shops never operationalize and leave to luck.
The numbers worth watching
Three metrics turn callbacks and warranties from a feeling into a managed cost.
Callback rate, sliced. The company number is the headline, but the rate by tech, by job type, and by part is where the decisions live. Watch the trend, not just the month, because a rising rate is an early warning that something upstream has slipped before it shows in the revenue.
Warranty recovery dollars. Track what you claimed back from manufacturers in parts and labor allowances over the year. A shop that has never measured this is usually shocked at how much it has been absorbing, because every uncaptured claim felt small in the moment. The number gives the warranty discipline a payoff you can see.
Cost of callbacks. Put a real dollar figure on rework: the truck rolls, the labor hours, the redo parts, and the opportunity cost of the jobs those hours could have served. The figure is sobering on purpose. Industry estimates have put a 5 percent callback rate at six figures of annual loss for a mid-size shop, and while your number depends on your volume and rates, the order of magnitude is why this is worth measuring at all. Once the cost of callbacks is a line you watch, the case for the training and the diagnosis time that prevents them makes itself.
When the failure is not yours
Not every return visit is a callback, and a shop that reflexively eats every one trains its customers to expect free work it never owed. When the failure is genuinely not your fault, document it and bill it fairly.
Customer-caused failures happen. The disposal that jammed on a chicken bone, the supply line a homeowner cranked until it cracked, the cleanout cap someone left off. That is a new service call, not a callback, and the photos you take are what let you bill it without an argument. Pre-existing conditions are the same. If you flagged the corroded galvanized branch on the original visit and the customer declined to address it, the leak that follows is the condition you warned about, and your note proves it.
A bad part is the in-between case, and it is the one to get right. The component failed, but not because of your work, so it is a warranty claim against the manufacturer, not a callback against you and not a charge against the customer for your error. Diagnose it as a defect, claim the part, and bill or allowance the labor. The thread through all three is documentation. Photos, the original scope, and a clear note are what let you bill fairly and hold the line when a customer assumes every return is free.
Keeping it in the system, not in someone's head
All of this falls apart the moment it lives in memory. The callback that nobody flagged, the warranty nobody recorded, the labor allowance nobody filed, these are not failures of intent. They are failures of where the information lives. If it is in a tech's head or a manager's recollection, it is already gone.
The information has to sit on the records it belongs to. The callback flag belongs on the work order, linked to the original job. The warranty belongs on the equipment, on the property record, with the serial and the install date. The cause code belongs on the callback so the report can find the pattern. Track it there and the metrics are a report you pull, not a project you launch each time someone asks how the shop is doing.
This is what a field service tool like FieldOS is for: the work order carries the callback flag and the parent link, the property carries the equipment history and the warranty terms, and the reports turn both into the callback rate and the warranty recovery number without anyone rebuilding it from paper. The tool does not fix your quality. It makes your quality and your costs visible enough that you can. The shop that runs this from one system knows its callback rate by tech on a Tuesday. The shop that runs it from memory finds out at year end, when it is too late to change the year.
Commercial and new-construction warranty periods
Commercial and new-construction work carries a contract warranty that is different from your standard service labor warranty, and the contract controls. A new build commonly comes with a one-year correction period during which you return and fix defective work at no cost, plus a punch list at substantial completion that has to be cleared before final payment.
Those contract callbacks are still callbacks, and they still belong in your tracking. The punch item you missed and the warranty-period leak you return for are rework against the original job, and coding them the same way you code a service callback tells you whether your install crews are as clean as you think they are. A new-construction division with a heavy punch list and a busy first-year warranty period has a quality problem the contract is quietly absorbing.
Read the contract for the term and the scope, because they vary by project and by the general contractor. Some carry warranty obligations well past the one-year correction period for specific systems, and the bond or retention may be tied to clearing the warranty work. The estimating side of pricing this work, including how you carry the warranty risk in the bid, sits in the estimating guide. The tracking side is the same as service: log it, code it, and learn from the pattern.
What to document, and who pays
The classification decides the money, so the record has to make the classification defensible. For every return visit, capture the scenario, who pays, and the action, and tie it back to the original work order. The table below is the decision in one view.
Behind every row is the same supporting record: what you did on the original visit, the equipment model and serial, the install date, the warranty term, and photos of the condition you found. That record is what turns a who-pays disagreement into a thirty-second answer, and it is what a manufacturer requires before it will honor a claim.
| Scenario | Who pays | Action |
|---|---|---|
| Your work failed, same issue, inside your labor window | You | No charge, fix it, code the root cause |
| Manufacturer part failed under part warranty | Manufacturer for part, customer or allowance for labor | Claim the part, bill labor or file the labor allowance |
| New, unrelated problem at the same address | Customer | Diagnose and bill it as a new job |
| Customer caused the failure | Customer | Document with photos, explain, bill fairly |
| Pre-existing condition you flagged and they declined | Customer | Show the prior note, bill the repair |
| New-construction punch or warranty-period item | You, under the contract | Correct per the contract, log and code it |
Common mistakes
- Never measuring the callback rate, so rework stays a year-end surprise instead of a managed number.
- Burying callbacks as new calls, which hides the rate and breaks the link to the tech and the original job.
- Eating warranty parts off the shelf instead of claiming them from the manufacturer.
- Billing a true callback to the customer, which loses the account and earns the review.
- Eating a genuinely new problem as a free callback, which gives away billable work.
- Keeping no equipment history, so the next tech has no serial, no install date, and no claim.
- Coding no root cause, so the pattern never reaches training and the same callbacks repeat.
- Skipping the labor allowance, so warranty labor gets performed for free by default.
Field and office checklist
Want this checklist to run itself on every job — with photo proof and a signed record crews can hand the customer? That's FieldOS.
Standards, terms, and references
There is no single code that governs callbacks and warranties the way the plumbing code governs an install. The terms come from three places, and each one controls its own piece.
The manufacturer's warranty document controls the part coverage, the term, and whether a labor allowance exists and how to file it. These vary by manufacturer and by product line, and many require the unit to be registered, so read the actual document for the equipment you installed rather than assuming a standard term. Your own labor-warranty policy controls what you cover and for how long, the 30 to 90 days on a repair or the year on an install being common starting points you set to your market and your confidence in the work. On commercial and new-construction jobs, the contract controls the warranty and correction period, and it overrides your standard policy.
Three habits carry the whole subject. Measure the callback rate, and slice it by tech and type so the number points at a fix. Classify every return as callback, warranty, or new problem before you bill it, because the classification is the money. And claim the warranty part and the labor allowance every time, because the manufacturer's defect is not yours to absorb. Get those three right and the rest is bookkeeping.
Terms and definitions
The same ideas go by different names across shops and software, so the vocabulary is worth pinning down.
A callback is also called a recall or a comeback. A warranty claim is sometimes called a warranty job or a warranty ticket. First-time fix rate is the complement of the callback story, the share of jobs closed on one visit. The labor allowance is sometimes called a labor reimbursement or a labor credit on the manufacturer's forms.
- Callback / recall / comeback
- A return trip to redo your own work that failed, on your dime, inside your labor warranty
- Warranty claim
- A request to the manufacturer to cover a part that failed under its warranty term
- Callback rate
- Callbacks divided by jobs over a period, expressed as a percent, best sliced by tech and type
- First-time fix rate
- The share of jobs resolved on the first visit, which rises as the callback rate falls
- Labor warranty
- Your guarantee on your workmanship, commonly 30 to 90 days on repairs and a year on installs
- Part warranty
- The manufacturer's coverage of a component against defects, from 1 to 10 or more years
- Labor allowance
- A set dollar amount some manufacturers pay toward the labor to install a warrantied replacement
- Root-cause code
- The reason a callback happened: workmanship, bad part, misdiagnosis, or rushed
FAQ
What is a callback in field service?
A callback is a return trip to redo work that should have been right the first time, on your dime. The truck rolls and a tech burns hours, but no invoice goes out. It is your workmanship failing inside your labor warranty, not a new problem and not a part the manufacturer owes.
What is a good callback rate?
Industry surveys of service trades commonly put acceptable callback rates around 2 to 3 percent, with top performers under 2 percent and weaker shops at 3 to 8 percent. Above roughly 8 percent is a real problem. Treat the figure as a benchmark, and slice it by tech and job type to act on it.
What is the difference between a callback and a warranty claim?
A callback is your work failing, so you fix it free inside your labor warranty. A warranty claim is a part failing under the manufacturer's term, so you claim the replacement from the manufacturer and bill or allowance the labor. The test is whether the work failed or the part failed. Diagnose it before you decide who pays.
How do you reduce callbacks?
Measure the callback rate, code the root cause of each one, and feed the patterns back to training, parts purchasing, and scheduling. A real diagnosis, the right part on the truck, and checking the work before leaving drive first-time fix up, which pulls callbacks down. Fix the cause, not the symptom on the report.
Who pays for a callback?
You do, when it is a true callback, because your work failed inside your warranty. A warranty part comes free from the manufacturer with labor billed or allowance-filed. A genuinely new problem is a new job you bill. Classify the visit correctly first, because billing a real callback loses the customer.
How do you calculate callback rate?
Divide callbacks by total jobs over a period and express it as a percent. The company-wide number is the headline, but the value is in slicing it by tech, job type, and part. Pair it with first-time fix rate, since the two move together as your diagnosis and workmanship improve.
Can I claim labor from a manufacturer warranty?
Sometimes. Some manufacturer warranties pay a set labor allowance toward installing a warrantied replacement, separate from the free part. It usually covers a fixed amount, not your full rate, and it is gone if you do not file. Read the warranty document, and submit the invoice with the model and serial of both units.
How long should my labor warranty be?
Common starting points are 30 to 90 days on a service repair and a year on an install, set to your market and your confidence in the work. The longer your labor warranty, the more callbacks you absorb, so price the risk into the job and write the term down so a customer dispute has an answer.
What do I do if a part fails under manufacturer warranty?
Confirm it is a part defect, not your install, then claim the replacement from the manufacturer using the model, serial, and install date. File the labor allowance if the warranty offers one, and bill the customer any labor gap you disclosed up front. Do not buy the part off the shelf and absorb a cost the manufacturer owes.
How much do callbacks cost a service business?
More than most owners realize, because each one is a free truck roll, free labor, redo parts, and the jobs those hours never served. Industry estimates have put a 5 percent callback rate at six figures of annual loss for a mid-size shop. Your number depends on volume and rates, which is why measuring the cost is the first step.