Skip to content
BizBinder
Early access open Get early access

Templates

Callback and guarantee scripts, for the visit after the job is finished

Seven messages for the return visit — booking the look, confirming a free fix inside your guarantee, pricing one that isn’t covered, claiming a failed part against its supplier, and naming damage that wasn’t from your work — fill in your details once at the top of this page and every script below rewrites itself.

A callback rarely announces what it is before you’ve looked. These seven scripts cover the exchange end to end: booking the visit without promising anything yet, confirming a free fix once you know it’s covered, pricing a visit that isn’t, claiming a failed part against its own supplier, naming damage that plainly wasn’t from your work, quoting the repair as a fresh job, and invoicing a chargeable visit against the job it belongs to.

Fill in your name, your business, and the client’s name once at the top of this page, and every script below updates to match. None of these commit you to anything on their own — go and look first, every time, before you send any of them.

Scripts

Script 01 · Replying to a report of failed work

Text

Hi [Client name], thanks for letting me know — I’ll come and take a look before we decide anything. Are you free [day/time]?

Why it works Booking the visit first, before promising a free fix or naming a price, gives you a chance to actually see the problem before you commit to either.

Script 02 · Confirming the visit is covered, and free

Email

Subject: On the issue at your place

Hi [Client name], I’ve had a look, and this is inside the guarantee on the original work — no charge for the visit or the fix. I’ll [what you’re doing to sort it] on [date]. [Your name]

Why it works Naming the guarantee explicitly, rather than just quietly doing the work, is what makes “free” read as a promise kept, not a favor.

Script 03 · Telling the client the visit is not covered, with the reason and the price

Email

Subject: What I found, and what it needs

Hi [Client name], I’ve had a look. This one’s outside what the original guarantee covers — [wear and tear, or the actual reason]. Happy to sort it, priced as a new job: [Amount] for [what’s involved]. [Your name]

Why it works Naming the specific reason, not just “not covered,” gives the client something concrete to weigh instead of a flat no.

Script 04 · A part has failed — claiming it against the supplier

Email

Subject: The part that failed at your place

Hi [Client name], The issue is the part itself, not the work fitting it — I’m claiming it against [supplier/manufacturer] under their own warranty rather than covering it under mine. That can take [rough timeframe]. I’ll keep you posted. [Your name]

Why it works Separating a part’s own warranty from your workmanship guarantee stops one quietly turning into an unpaid claim on the other.

Script 05 · The damage was not caused by your work — the evidence, plainly

Email

Subject: What I found on today’s visit

Hi [Client name], I’ve had a look, and this isn’t from the original work — [what you actually found, plainly]. Happy to quote fixing it as a separate job if you’d like it sorted: [Amount]. [Your name]

Why it works Stating plainly what you found, rather than just denying responsibility, gives the client a reason they can check for themselves.

Script 06 · Quoting the repair as a new job

Email

Subject: Quote for the repair

Hi [Client name], Here’s the quote for sorting [issue]: [Amount], covering [what’s included]. This is separate from the original job, since it’s outside the guarantee — let me know if you’d like me to go ahead. [Your name]

Why it works Quoting it like any other job, rather than folding it into a vague “I’ll sort it,” keeps the price and the guarantee both honest.

Script 07 · Invoicing a chargeable callback

Email

Subject: Invoice [Invoice #] for the return visit

Hi [Client name], Invoice [Invoice #] is attached for the return visit — [Amount], referencing the original job it follows on. Due [Due date]. [Your name]

Why it works Referencing the original job on the callback invoice keeps the two connected, in case the client asks why this one isn’t covered.

Questions

Should every callback get a free fix?
Only one that’s genuinely your work and still inside your stated guarantee. Treating every callback as automatically free trains clients to expect a free visit for anything, guarantee or not.
What if I’m not sure whose fault it is yet?
Book the look before you say anything about cost. “I’ll come and check” commits you to nothing, and you can send the right script once you’ve actually seen it.
How do I avoid sounding like I’m dodging responsibility?
Say plainly what you found, not just that it isn’t covered. A specific reason reads as an honest assessment; a flat refusal reads as an excuse.

Want the original job on hand when you reply?

You still write and send these yourself — BizBinder doesn’t track your guarantee period or decide whether a callback is covered. What it does keep is the original job, its date, and its invoice, so when a callback comes in, you’ve got the record in front of you instead of digging for it.