Handling Warranty, Redo, and Callback Calls Without Killing Your Locksmith Schedule (2026)

Handling Warranty, Redo, and Callback Calls Without Killing Your Locksmith Schedule (2026)

Every locksmith has felt the small drop in the stomach that comes with a specific kind of call: "Hey, you cut me a key last week and now it's not working."

That call is not a new job. It is a redo, a warranty claim, or a callback — and how your shop handles it decides three things at once: whether you keep the customer, whether you protect the margin on a job you already did, and whether responding to it torpedoes the revenue-generating work already on today's board. Handled well, these calls are a loyalty engine. Handled badly, they are a slow leak of your most experienced tech's time and your shop's profit.

As of July 2026, the shops that have this dialed in are not the ones with the fewest redos — every locksmith has some. They are the ones with a process: a clear policy, a fast triage script, and a system that instantly knows the history of the original job. This guide is that process. We will cover how to triage a warranty or redo call in under two minutes, how to protect margin without nickel-and-diming a loyal customer, and how an AI receptionist captures the original-job details, routes the redo correctly, and books it into a slot that does not derail your new work.

Why redo calls are so dangerous to a schedule

A brand-new lockout is easy to slot: it is urgent, it pays, and everyone knows what to do with it. A redo call is treacherous precisely because it feels like it should jump the queue but often pays nothing.

They carry emotional weight. The customer is frustrated — they paid, and something isn't right. That frustration pressures whoever answers to promise "we'll get someone out today," which yanks a tech off a paying job.

They demand your best person. A redo on a transponder key or an immobilizer program isn't a job you hand to your newest tech. It goes to the experienced hand — the same person whose time is most valuable on new revenue.

They are unpriced by default. New jobs have a quote. Redos arrive with an implied "this should be free," and if nobody has the original-job facts in front of them, the person on the phone can't tell a legitimate warranty from a new problem the customer is trying to fold into an old ticket.

They interrupt. A redo call lands mid-day, mid-job, and demands an on-the-spot scheduling decision. Without a rule, that decision gets made emotionally — and emotional dispatching is how a two-truck shop ends up giving away an afternoon.

The fix is not to dread these calls. It is to strip the emotion and the guesswork out of them with a repeatable triage — the same discipline we apply to sorting emergency versus scheduled work.

The triage: sort every callback into one of four buckets

Not all "it's not working" calls are the same. The single most important skill is sorting the call — fast — into one of four buckets, because each one has a different owner, a different price, and a different urgency.

Bucket 1 — True warranty. Your work failed within your stated warranty window. A key you programmed stopped responding; a lock you rekeyed binds. This is on you, it is free, and it should be scheduled promptly but not necessarily by yanking a tech off a paying job the same hour.

Bucket 2 — Redo, shared cause. Something is off, but the cause is murky — the customer's second key was already worn, or the vehicle has an unrelated electrical gremlin. These need diagnosis before you commit to free. The right move is to schedule a look, not to promise a free fix sight-unseen.

Bucket 3 — New problem, old customer. The customer calls about their "key not working," but it turns out to be a different vehicle, a different key, or a brand-new issue. This is a new job wearing a warranty costume. It should be quoted and booked like any new job — warmly, because they're a repeat customer, but at a price.

Bucket 4 — Not your work at all. They had someone else do the original job, or they misremember who they called. Common, and worth catching early so you don't warranty a competitor's mistake.

The entire game is sorting fast and correctly. And the thing that makes sorting fast is having the original job's record — vehicle, date, service, tech, price, warranty terms — in front of whoever answers. Which is exactly where most shops fall down: the info is in someone's head, a paper ticket, or a text thread nobody can find mid-call.

Warranty vs. redo vs. callback: a working comparison

These three words get used interchangeably and shouldn't be. Here is the one comparison table in this guide, defining each and prescribing the handling.

Call type	What it means	Who pays	Right response
Warranty	Your work failed inside your stated warranty window	You (free)	Verify original job, schedule the fix promptly, log it
Redo (shared cause)	Result is off but cause is unclear or partly the customer's	Diagnose first	Book a look; decide free vs. paid after seeing it
Callback (new problem)	Repeat customer, but a genuinely new job	Customer	Quote and book like new work, with loyalty warmth
Not-our-work	Original job was done by someone else	N/A	Politely decline warranty; offer a fresh quote

Two rules make this table usable. First, never promise "free" on the phone for anything but a clear Bucket 1. "Let's get you on the schedule and take a look" protects you from committing to a free visit on what turns out to be a new problem. Second, write the policy down. A warranty window ("90 days on programming, 1 year on hardware," or whatever fits your work) that lives in your head is a policy you will apply inconsistently and lose money on. Industry bodies like the Associated Locksmiths of America (aloa.org) have long tied professionalism to clear, honored terms — a written warranty is both a margin tool and a trust signal.

Protecting margin without nickel-and-diming

The fear is that a strict warranty policy makes you look cheap and costs you the customer. The opposite is true when it's done with warmth. Here is how to protect the job's margin and keep the relationship.

Honor real warranty claims fast and without friction. When it's genuinely your failure, eating it quickly and graciously is the cheapest marketing you will ever buy. A customer whose problem you fixed for free, promptly, tells people. This is where reviews get made — and a systematic review process turns a well-handled redo into a five-star story instead of a one-star complaint.

Diagnose before you commit on the gray ones. For Bucket 2, "we'll come take a look" is not stalling — it is the honest answer. Half of "your key failed" calls turn out to be a worn spare, a different key, or a vehicle issue. Seeing it first is how you avoid giving away paid diagnostic time as a freebie.

Book new problems as new jobs — warmly. A repeat customer with a genuinely new issue should feel appreciated, not audited. "Good news — that's actually a separate job from the one we did, so here's what that runs, and because you're a returning customer we'll get you in fast." That keeps the margin and the goodwill.

Track your redo rate. If the same service keeps coming back, that's a training or a supplier problem, not a phone problem. You can only see the pattern if every redo is logged against the original job — another argument for capturing job history systematically rather than in scattered notes.

Margin protection isn't about being stingy. It's about applying a fair, written policy the same way every time, so you eat the ones you should and charge for the ones you should — without an argument at your service counter.

Where the schedule actually gets killed — and the fix

The real damage from redo calls isn't the free fix. It's the scheduling chaos they cause. A frazzled owner takes a redo call mid-job, promises to swing by "in an hour," and now the afternoon's paying work slides. Do that three times a week and you've given away a day.

The fix is to treat redos as scheduled work, not interrupts — with rare exceptions for a stranded customer whose warranty key just died. That means:

Slotting redos into designated windows. A daily or twice-weekly "redo and warranty" block keeps them from bleeding into revenue jobs. The customer gets a firm time; your paying board stays intact. Getting redos onto a defined slot is a scheduling discipline, not a favor you improvise.

Making the accept/decline decision on facts, not feelings. With the original job's record on screen — date, service, warranty terms — the "is this warranty?" question answers itself in seconds, and nobody over-promises to soothe a frustrated voice.

Never letting a redo call go to voicemail. A warranty customer who can't reach you doesn't just get frustrated — they escalate to a public review. Every callback needs a live, informed answer, which is precisely the gap an always-on answering layer fills.

This is where automating the front desk pays off twice: it protects the schedule and the relationship at the same time. Our overview of what to automate versus keep human in dispatch sits alongside this same principle — the phone triage is automatable; the judgment call on a gray-area redo can escalate to you.

How an AI receptionist handles warranty and redo calls

Here is where an AI receptionist earns its keep on exactly these calls, because the whole problem is information and timing.

It knows the caller. When a repeat customer calls, the system recognizes the number and surfaces their history — the vehicle, the last service, the date, the price. That is the single most important input to triage, and it's available instantly instead of living in someone's memory. The engine behind this is AI call handling that logs every interaction against the customer.

It captures the redo cleanly. It collects what's wrong, which vehicle and key, and when the original work was done, then classifies the call — likely warranty, likely new job, or needs-a-look — so the details arrive structured instead of as a frantic voicemail.

It routes correctly. A clear warranty gets flagged and slotted into your redo window; a genuinely new problem gets quoted from your price book like any new job using automated quoting; a gray-area call gets escalated to you with the history attached so you decide with facts.

It books without derailing new work. Redos land in a designated slot on your calendar, not jammed into the middle of a paying afternoon — because the system schedules by your rules, not by whoever sounds most upset.

It never sends a warranty customer to voicemail. Nights, weekends, and mid-job overlaps are all answered live, so a frustrated customer never gets the silence that turns into a one-star review.

The net effect: the emotional, unpriced, interrupt-driven call that used to derail your day becomes a structured, correctly-classified, properly-slotted task — handled without pulling your best tech off revenue. See how it's tailored to the trade on the AI receptionist for locksmiths page.

The bottom line

Warranty, redo, and callback calls are a permanent part of locksmithing — you will never get to zero, and you shouldn't want to, because a well-handled redo is one of the strongest loyalty and review drivers you have. What kills shops isn't the redos themselves; it's handling them emotionally, without the original-job facts, and letting them barge into paying work.

Fix it with three things: a written warranty policy, a four-bucket triage that sorts every callback fast, and a system that surfaces the customer's history the instant they call so the sort is made on facts. An AI receptionist supplies the last two automatically — it knows the caller, classifies the redo, quotes genuine new work, escalates the gray areas, and books everything into slots that protect your revenue. The redo call stops being the drop in your stomach and starts being just another well-run part of the day.

Frequently asked questions

What is the difference between a locksmith warranty call and a redo?

A warranty call is when your own work failed inside your stated warranty window and the fix is free, while a redo is a broader term for any return visit whose cause may be shared with the customer or the vehicle and needs diagnosis before you commit to free. The practical rule is never to promise free over the phone on anything but a clear warranty; for everything else you book a look and decide after seeing it. Sorting the two correctly is what protects both the customer relationship and your margin.

How do I handle a redo call without losing money?

Handle it by applying a written warranty policy the same way every time: honor genuine failures fast and free, diagnose the gray-area calls before committing, and book genuinely new problems as new quoted jobs even for repeat customers. The margin leak comes from over-promising "free" on the phone without the original job's facts in front of you. Tracking your redo rate against the original job also reveals whether a recurring failure is really a training or supplier issue rather than a phone one.

Can an AI receptionist tell a warranty call from a new job?

An AI receptionist recognizes the returning caller's number, surfaces their original job history, and captures what is wrong and which vehicle and key, then classifies the call as likely warranty, likely new job, or needs-a-look. Clear new problems get quoted from your price book, clear warranty claims get flagged and slotted, and genuine gray areas get escalated to you with the history attached. That structured handoff replaces the frantic voicemail that used to leave you guessing.

How do I stop redo calls from wrecking my schedule?

Treat redos as scheduled work slotted into a designated daily or twice-weekly window rather than as interrupts that pull a tech off a paying job. The chaos comes from taking a redo mid-job and promising to swing by in an hour, which slides your revenue work. With the original job record on screen the accept-or-decline decision is made on facts in seconds, and an always-on answering layer means no warranty customer ever hits voicemail and escalates to a public review.

What does an AI receptionist for handling callbacks cost?

TheKeyBot runs on flat monthly plans: Core is $500/month for 500 AI minutes with 45¢ per minute overage, Pro is $750/month for 1,000 minutes at 40¢ overage and is the most popular, and Elite is $1,200/month for 2,500 minutes at 35¢ overage. Every plan logs customer history, classifies warranty versus new-job calls, quotes from your price book, and books into your calendar 24/7 in English and Spanish. Full pricing is at https://www.thekeybot.com/pricing.

Should a locksmith put a warranty policy in writing?

Yes — a written warranty window such as 90 days on programming and a year on hardware is both a margin tool and a trust signal, because a policy that lives only in your head gets applied inconsistently and loses money in on-the-spot arguments. Clear, honored terms are also what industry bodies tie to professionalism in a trade that fights a bait-and-switch reputation. Writing it down lets whoever answers the phone apply it the same way every time.

Sources

1. Associated Locksmiths of America — professionalism and clear consumer terms: https://www.aloa.org/
2. Federal Trade Commission — consumer protection guidance for service trades: https://www.ftc.gov/
3. Harvard Business Review — research on customer effort, loyalty, and service recovery: https://www.hbr.org/