Dispatch scheduling

How to reduce plumbing callbacks and recalls

Define and count callbacks, sort them into root-cause categories, add a leave-site check and run a weekly review that fixes causes without blaming techs.

AssistCall research teamPublished Reviewed by Faruque Amin, VP of Sales and Marketing7 min read

On this page
  1. Callback, recall, warranty visit: agree on the words
  2. Count them properly
  3. Sort every callback into a root cause
  4. Why callbacks deserve the attention
  5. The two-minute leave-site check
  6. Run a weekly callback review
  7. Feedback that techs accept
  8. Build skill where callbacks cluster
  9. Jobs that deserve a second look
  10. How the office handles the callback call
  11. Example: a month of callbacks, sorted
  12. Connect callbacks to the rest of the board
  13. Frequently asked questions
  14. References
Dispatch scheduling: How to reduce plumbing callbacks and recallsArticle coverDISPATCH SCHEDULINGHow to reduce plumbingcallbacks and recallsAva for PlumbersInsightsDispatch scheduling: How to reduce plumbing callbacks and recallsArticle coverDISPATCH SCHEDULINGHow to reduceplumbing callbacksand recallsAva for Plumbers

Key takeaways

  • Agree on one definition and window, such as a return visit for the same issue within 30 days, and count every one.
  • Sort each callback into a root cause: workmanship, diagnosis, parts, communication or customer factors.
  • A two-minute leave-site check catches many leaks before they become callbacks.
  • Water damage claims average $15,400[1], so a failed repair can cost far more than the return trip.

Callback, recall, warranty visit: agree on the words

Shops use these words loosely, and that makes the problem impossible to measure. Pick definitions and write them down. A common set: a callback is any return visit for the same problem at the same address within a fixed window after the original job, often 30 days. A recall is a callback where the original work failed. A warranty visit is a callback covered by your labor or a manufacturer's warranty. A new problem at the same house is not a callback, even if the customer calls it one.

The window matters. Too short and you miss slow leaks that show up three weeks later; too long and you count unrelated failures in an old system. Thirty days for most service work and longer for installs is a reasonable start. Whatever you choose, use it the same way every month.

Count them properly

Callback rate is callbacks divided by completed jobs in the same period, measured by job type and by tech. Flag the original job in the system when a callback is booked, so the two are linked. Without the link you cannot see who did the first visit, what was done or which parts were used.

Do not let the CSR decide alone whether a return visit is a callback. The CSR records the customer's description and links it to the earlier job; the service manager classifies it after the return visit, when the cause is known.

Sort every callback into a root cause

Example: root-cause categories for plumbing callbacks
CategoryTypical examplesWhere the fix lives
WorkmanshipFitting not fully tightened, poor solder joint, supply line kinkedLeave-site check, tech coaching, ride-alongs
DiagnosisCleared the clog but not the cause; replaced the wrong componentCamera use, diagnostic checklists, lead tech review
PartsDefective cartridge, cheap supply line, wrong replacement partSupplier choice, stock list, warranty claims
CommunicationCustomer expected a full fix after a temporary repairWritten job notes, clear explanation before leaving
Customer or system factorsWipes flushed again, old pipe failing next to the repairCustomer education, honest notes about system condition

Sorting often shows that workmanship is only part of the story. Diagnosis and communication failures turn up regularly, and they are fixed in the office and the training plan as much as on site.

Why callbacks deserve the attention

The return trip is the visible cost. The bigger risk is water. The Insurance Information Institute reports the average homeowners claim for water damage and freezing was $15,400 (2019 to 2023)[1], and that 1.6% of insured homes had a water damage or freezing loss each year in 2018 to 2022, second only to wind and hail[1]. A connection that weeps inside a wall is a callback that may come with an insurance adjuster.

Share of insured US homes with a loss each year, by causeInsurance Information Institute, annual average 2018 to 2022.
Share of insured US homes with a loss each year, by causeBar chart. Wind and hail: 2.8%; Water damage and freezing: 1.6%.Wind and hailWind and hail: 2.8%2.8%Water damage and freezingWater damage and freezing: 1.6%1.6%Share of insured US homes with a loss each year, by causeBar chart. Wind and hail: 2.8%; Water damage and freezing: 1.6%.Wind and hailWind and hail: 2.8%2.8%Water damage and freezingWater damage and freezing: 1.6%1.6%

Source: Insurance Information Institute, 2019-2023[1]

Show the data
Cause of lossInsured homes with a loss (%)
Wind and hail2.8%
Water damage and freezing1.6%

Callbacks also cost reputation. Pew found 54% of people who read online reviews pay more attention to extremely negative ones[2]. A customer who had to take a second day off for the same leak is exactly who writes them.

$15,400

Average homeowners insurance claim for water damage and freezing, 2019 to 2023[1]

The two-minute leave-site check

The cheapest callback prevention is a short routine before the tech packs up. Make it a checklist in the field app, not a memory test.

  1. Run the fixture or system under normal use for at least two minutes.
  2. Dry every connection you touched with a paper towel, run again, and check the towel.
  3. Check for drips under the sink, behind the toilet or at the water heater fittings with a flashlight.
  4. Confirm shut-off valves are fully open and not weeping at the stem.
  5. For drains, run water through every connected fixture, not just the one that was clogged.
  6. For water heaters, confirm temperature setting, venting and relief valve discharge before leaving.
  7. Photograph the finished work and the connections.
  8. Explain to the customer what was done, what was not, and what to watch for.

Run a weekly callback review

  1. Pull the list

    Every callback from the past week, linked to its original job, with photos and notes from both visits.

  2. Classify each one

    The service manager assigns a root cause category, after talking to the tech who returned.

  3. Look for patterns

    Same tech, same job type, same part, same supplier or same CSR booking? Patterns matter more than single events.

  4. Pick one fix

    Choose one change for the coming week: a checklist item, a stock change, a training topic or a script line.

  5. Check last week's fix

    Did the callbacks it targeted fall? If not, try a different fix rather than repeating the same speech.

Keep the meeting short and the tone factual. Fifteen minutes is enough for most shops.

Feedback that techs accept

Callbacks become a blame game quickly, and techs who feel blamed hide problems. A few habits help:

  • Talk about the job, not the person: 'this connection failed' rather than 'you did it wrong'.
  • Show the photos from both visits and ask the tech what they would do differently.
  • Share callback rates by tech privately; share categories and fixes with the whole team.
  • Credit the techs who catch problems on the leave-site check, so finding issues is seen as good work.
  • Pay attention to workload. A tech running five jobs a day with no slack will cut corners at the end of each one.

Build skill where callbacks cluster

Plumbers typically learn through a 4- or 5-year apprenticeship[3], and apprentices usually receive about 2,000 hours of paid on-the-job training each year[3]. That means many shops have a wide skill spread on the same board. Use the callback data to aim training: if newer techs produce most diagnosis callbacks on drains, pair them with a lead for camera work; if they produce workmanship callbacks on water heaters, add a lead review of photos before they leave the site.

Jobs that deserve a second look

Some job types tend to produce more callbacks than others. Give them extra attention on the leave-site check and in the weekly review:

  • Repeat drain calls at the same address, where the clog was cleared but the cause, such as roots, a belly in the line or grease, was never seen.
  • Cartridge and valve replacements on older or uncommon faucet brands, where the replacement part is close but not exact.
  • Water heater installs where venting, gas connections or the expansion tank were adapted to fit an older space.
  • Temporary repairs done to stop a leak at night, which the customer may later remember as the full fix.
  • Toilet repairs on old fixtures, where one new part strains the next old one.

For each of these, decide what extra step the tech takes: a camera pass, a photo of the vent run, a written note that a repair was temporary, or a quote for replacement left with the customer.

How the office handles the callback call

The call itself shapes how the customer feels about everything that follows. The CSR should listen, apologize for the trouble without admitting fault before anyone knows the cause, and book quickly, ideally with the original tech unless the customer asks otherwise.

Script: 'I'm sorry it's acting up again. Let me pull up the visit from last week. I'd like to get someone back out quickly. I can have Dev there tomorrow morning, or a different tech this afternoon. Which would you prefer?'

Never pressure a customer about the review they might write. The FTC's rule on consumer reviews bans unfounded legal threats, intimidation or other tactics to suppress negative reviews[4]. Fix the problem and let the result speak.

Example: a month of callbacks, sorted

Example (fictional): a seven-truck shop counts 22 callbacks in a month against roughly 480 completed service jobs. Sorted, nine are diagnosis (mostly drains where the clog returned), six are parts (one batch of faucet cartridges), four are communication (customers expected a permanent fix after a temporary patch) and three are workmanship.

Example, continued: the shop adds camera inspection as a standard offer on repeat drain calls, returns the cartridge batch to the supplier and adds a line to the job notes template: 'Temporary repair: yes or no.' The next month's count falls, mostly in the categories it targeted.

Connect callbacks to the rest of the board

Callbacks are first-time fix failures that happen after the tech leaves. The intake and parts work in dispatching for first-time fix prevents some of them, and the priority rules in the dispatch priority matrix decide how fast a callback gets back on the board. Most shops put an active leak callback ahead of new routine work, because the customer already trusted you once.

Frequently asked questions

What counts as a plumbing callback?

A return visit for the same problem at the same address within a set window after the original job, often 30 days for service work. A new, unrelated problem at the same house is not a callback.

What causes most plumbing callbacks?

It varies by shop, which is why you should sort each one into a root cause. Diagnosis misses and communication gaps are often as common as workmanship problems.

Should the original tech go back on a callback?

Usually yes, so they see what happened and can fix it, unless the customer asks for someone else or the original tech lacks the skill the problem now needs.

Do callbacks get charged?

Decide your policy in advance and state it on invoices: workmanship failures within your warranty window are normally free, new problems are billed as new work.

References

  1. Insurance Information Institute (2019-2023). Facts + Statistics: Homeowners and renters insurance (opens in a new tab) โ†‘

  2. Pew Research Center (2016). Online Reviews (Online Shopping and E-Commerce) (opens in a new tab) โ†‘

  3. U.S. Bureau of Labor Statistics (2025). Occupational Outlook Handbook: Plumbers, Pipefitters, and Steamfitters (opens in a new tab) โ†‘

  4. Federal Trade Commission (2024). Federal Trade Commission Announces Final Rule Banning Fake Reviews and Testimonials (opens in a new tab) โ†‘

Book a demo

See Ava handle your calls.

Book a short demo. Weโ€™ll walk through your calls and workflow, and agree what Ava should take care of.

Book a demo