Delivery Leak · The Unowned Callback
The Warranty Silence: Give the Customer's Callback an Owner
In This Article
Imagine this at your Billings plumbing shop. A customer calls back about a job you already finished — the water heater's making noise again, or the fix just didn't hold. Whoever answers says, "I'll have someone call you back," and hangs up. Nobody writes down who "someone" is.
The office sent the message along. The tech's on another job. "They said they'd call back." Who actually owes this customer an answer?
Here's the fix, in one line: a warranty complaint isn't closed when the message gets passed along — it's closed when one named person stays on it until the customer has an answer. Below is the card that gives that job a name, and keeps it there until someone else explicitly accepts it.
The job is closed. The complaint isn't.
Follow the message instead of the job. The customer reports the problem to whoever picks up — call it the office. The office does the right first move: they pass it to the tech who did the original work. That's where it usually stops being anyone's job in particular.
The office assumes the tech will call once he sees the note. The tech, between jobs, assumes the office already told the customer someone's coming. Both of them did something. Neither of them owns the customer's next update. The message traveled. Responsibility didn't.
This is a different gap than the Handoff Leak, which covers a sales promise getting lost on the way to the crew before a job starts. This is what happens after the work is finished and something comes back — the complaint has nowhere built-in to land.
What's actually at risk beyond the repair

A warranty callback isn't just about the one repair. Depending on how it's handled, it can touch whether this customer calls you for the next job, whether they mention you to a neighbor, and whether the story they tell is "they made it right" or "they never called back." None of that is guaranteed either way — but it's the part that's actually on the line, not just the cost of a return visit.
That's worth sitting with, because keeping a customer you already have is the cheap side of the math compared to winning a new one: acquiring a new customer can cost five to 25 times as much as retaining an existing one (Harvard Business Review, Amy Gallo, 2014). That range is general — it isn't a measured cost of a specific unanswered callback — but it's a reason an open complaint deserves more attention than "we'll get to it."
Curious what a repeat customer is worth to you specifically? The Customer LTV Calculator runs that number from your own figures — no detour required here, just worth a look separately.
The callback ownership card
The fix isn't a new piece of software. It's one card — a sheet, a shared doc, a clipboard, whatever you've already got — with a fixed set of fields, and one rule that makes it work:
Callback Ownership Card
- Original job
- What was done, and the customer's description of the problem now.
- Callback owner
- The one named person responsible for the customer's next update — not necessarily the person fixing it.
- Next action & update time
- What happens next, and exactly when the customer hears something — even if the answer is "still checking."
- Technical assessment
- Who's looking at the actual problem, if that's a different person than the owner.
- Backup contact
- Who updates the customer the moment the owner can't reach them at the agreed time.
- Latest contact, status, outcome
- When the customer last heard from you, where it stands, and — once there is one — the documented result.
The operating rule: sending a message doesn't transfer ownership. Accepting it does. Nobody gets to consider the complaint handled by forwarding it — the next person has to actually take the card.
Acknowledging a complaint doesn't establish warranty coverage or promise a free repair — the card tracks who's responsible for talking to the customer, not what you owe them. That part still gets decided on its own merits.
Watch it move through the process

Back to the opening call. Instead of just relaying a note, whoever answers fills out the card and names themselves the owner until someone else explicitly accepts the handoff. The tech gets the technical question, not the whole problem — and the owner still checks back with the customer at the agreed time, whether or not the tech has an answer yet.
If the tech's on another job all week, the backup contact gives the update instead — triggered the moment the owner can't reach the customer at the agreed time, not whenever someone happens to remember: "still looking into it, here's when we'll know more." If the customer doesn't pick up when you call, that's a logged attempt and a pending next action, not a resolved file.
A scheduled visit means the complaint is moving. It stays open. The named owner keeps the next update on the calendar and stays responsible until someone else accepts the handoff. Once the repair is actually complete, record the result and tell the customer. If it's still disputed, record that too — don't mark it fixed just because a visit happened.
This pairs with the Callback Leak, which covers what to do once you're logging why redo visits keep happening — that's the pattern-finding half. This is the half that makes sure the customer isn't left wondering while you find it.
If it's already a review
Sometimes the complaint goes public before anyone owns the callback privately. That's a separate problem worth solving on its own terms — responding well in public doesn't substitute for actually fixing the underlying issue, and fixing the issue doesn't erase a bad review that's already up. The Review Response Playbook covers the public-reply scripts; the one stat worth knowing here is that 88% of consumers say they'd use a business that responds to all its reviews, versus 47% for one that doesn't respond at all (BrightLocal, 2022 Local Consumer Review Survey). That's about stated willingness to consider a business, not a guarantee the review gets taken down or the customer comes back — but silence in public is its own kind of warranty silence.
Frequently Asked Questions
Take the complaint, name one person responsible for the customer's next update, and have that person agree to a specific next action and a time to check back in — before anyone hangs up. That named owner coordinates the technical assessment (even if someone else performs it) and stays on the file until the customer has a documented outcome: fixed, or a clear, still-open next step. The repair might take a few calls. The ownership shouldn't change hands without someone explicitly accepting it.
Whoever owns the callback, not necessarily whoever fixes the problem. Those are different jobs. The owner's job is keeping the customer informed and making sure the technical side actually happens; the tech's job is the repair itself. A lot of warranty silence happens because everyone assumes "the tech will call" or "the office will call" — and a job can be technically correct, and uncoordinated, at the same time.
The callback owner updates the customer anyway. Unavailability is a reason the technical answer is delayed — it's not a reason the customer hears nothing. A backup contact exists for exactly this: the moment the owner can't reach the customer at the agreed time, the backup gives the update instead, without needing the original tech on the phone.
A shared card or a sheet with a short, fixed set of fields works fine: the original job, the complaint, who owns the callback, the next action and when, who's handling the technical side, a backup contact, and the latest status. The tool matters less than the habit of one named person reviewing every open item on it regularly, so nothing sits quietly without anyone noticing.
Only once the repair is actually complete and the customer has been told the outcome — or, if it's still disputed, once that disagreement has been recorded too. Forwarding the message isn't resolved. A scheduled visit isn't resolved either; that's progress, and the file stays open with a named owner until there's an actual outcome to report.
Picture that same opening call again, a month from now. This time, whoever answers can see who owns the complaint and when the next update is due. "They said they'd call back" has a name attached to it.
If your website also makes your contact details hard to find, you can see what the one-page website includes. GrowthLeaks' one-page website offer is $97 setup plus $10/month hosting; domain registration is quoted separately and paid annually upfront.