The Callback System: Turning Complaints Into 5-Star Reviews

It's Friday afternoon, the tech just finished a warranty call-back on a blower motor, and the customer is already on Google writing "they've been out three times and it's still not fixed." You don't find out until Tuesday, when someone happens to check the reviews — by then, three more potential customers have read it. That's not a bad-fix problem; it's a nobody-owned-the-follow-up problem. If you want the full review framework this fits into, start with the pillar guide on Google reviews for contractors, then come back here to build the callback half of it.

Why callbacks are your best review opportunity

A callback is a customer who already bought from you and already has a reason to talk. Most contractors treat callbacks as a cost — the warranty truck roll that eats the day. The contractors with 4.8-star profiles treat them as a review factory.

Concrete takeaway: callbacks are your highest-leverage review moment — a mid-complaint customer converts to 5 stars faster than any happy customer converts on their own. But only if you beat the industry's lazy 42-hour average.

Step 1: the callback log — one source of truth

The reason callback complaints rot into 1-star reviews is simple: nobody wrote them down. The tech heard the complaint on-site, told the dispatcher from the truck, and the memory died at 5 PM. So the system starts with a log — one place where every reported problem lives until it's closed.

Your log doesn't need to be fancy. A shared spreadsheet works; your FSM (field service management software — the app you run jobs and schedules through) or CRM (customer relationship manager — the system that holds customer records and communications) works better because the techs already live in it. Five fields, no exceptions:

• Customer name + job address — so anyone can find it
• Date and time reported — starts the 24-hour triage clock
• The problem in the customer's words — not the tech's diagnosis, the customer's complaint
• Who owns it right now — a name, never "the office"
• Priority level — A, B, or C, set by the triage rules below

Rule: no callback exists unless it's in the log. If a tech hears "hey, while you're here, the other unit is acting up again" on-site, that goes in before they leave the driveway. If the office hears it on a call, it goes in while the customer is still on the phone.

Concrete takeaway: create the callback log this week — five columns, one rule (if it's not logged, it doesn't exist). This single habit kills 90% of callbacks that spiral into public reviews.

Step 2: the 24-hour triage

A callback complaint has a shelf life. Every hour without acknowledgment, the customer's story hardens: "they don't care." Responding within an hour makes you 7x more likely to qualify a lead (Harvard Business Review, 2011) — and a callback customer is hotter than any new lead, because they already paid you. The rule: every reported problem gets a human acknowledgment within 24 hours, every Priority A problem within 2.

Triage is not the fix. It's three sentences: we heard you, here's who owns it, here's when you'll hear back next. Acknowledgment stops the clock on the customer's anger. Here's the script — keep it in your SOP (standard operating procedure — a step-by-step written checklist anyone can follow):

A note on texting compliance: before you send business texts, your number needs A2P 10DLC registration (A2P = application-to-person messaging; 10DLC = 10-digit long code — the carrier approval that lets businesses text from a local number; 1–7 day approval, roughly $15–$20 one-time). Include opt-out language in your first text, and respect TCPA quiet hours — no marketing texts before 8 AM or after 9 PM in the recipient's local time. This is general information, not legal advice.

Concrete takeaway: triage within 24 hours on every callback, within 2 hours on Priority A. Thirty seconds of messaging buys you the window to fix the problem.

Step 3: dispatch priority rules

Callbacks die in dispatch because they compete with paid work. A tech looking at a board full of jobs will always pick the paid job first — that's rational, and that's exactly why you need written priority rules that take the decision out of their hands:

• Priority A — safety or comfort critical: no heat, no cooling in extreme weather, gas or electrical issues, active water. Scheduled within 24 hours, ahead of non-emergency paid work; owner notified automatically.
• Priority B — real problem, no emergency: system running but noisy, minor leak, cosmetic issue, repeat-visit complaint. Scheduled within 3 business days.
• Priority C — perception or preference: customer doesn't like how something looks, questions about the invoice, "just checking" calls. Acknowledged in triage, handled within 5 business days.

Two rules keep this honest. First, the priority is set at triage time by the person who logs it, using the customer's words — never downgraded by dispatch to make the board look better. Second, the owner reviews the A list every morning. If an A sits unassigned, that's the day's first problem, before revenue.

Concrete takeaway: Post the three priority tiers at dispatch, and let the owner audit the A list daily. Written rules beat "use your judgment" every time.

Step 4: the recovery protocol

Fixing the problem is only half the job. The recovery protocol is what happens around the fix — and it's what separates "fine, they fixed it" from a 5-star review:

• Arrive on time to the second visit. The first impression already went wrong; the second visit is a re-first-impression. Text when en route.
• Name the failure out loud. The tech's script: "I know this is the second trip for the same issue, and that's not acceptable. Here's what we're doing differently this time." Defending the first visit kills the review.
• Fix it completely, then over-deliver once. Tighten the thing adjacent to the problem. Clean the filter while you're there. One visible extra, documented on the work order.
• Follow up 24–48 hours after the fix. A call or text from the office: "Just checking everything is running right since the tech was out." This call is the review trigger in Step 5.

Concrete takeaway: the recovery protocol is four moves — on-time arrival, owning the failure, one visible extra, and a 24–48-hour check-in. Skip the check-in and you skip the review.

Step 5: the review ask after a successful fix

Here's where the system pays off. When the check-in comes back clean — customer says it's running fine, they're satisfied — you ask for the review. And here's the critical compliance point: you ask everyone, satisfied or not. You never filter unhappy customers out before the review ask. Filtering unhappy customers before asking for a review is called review gating, and it violates Google's policy. You also never pay for or incentivize reviews in ways that violate Google policy — no discounts-for-stars, no gift cards tied to a review.

So the ask goes to every callback customer once the fix is confirmed — same channel, same wording. The ones who are thrilled write 5 stars. The ones still unhappy will tell you — and then you fix it again instead of finding out on Google. That's not gating; that's a feedback loop. Here's the ask:

Send it within 24 hours of the satisfied check-in, while the relief is fresh. And track it — add two fields to the log: "review asked (date)" and "review received (date)." That closes the loop from complaint to review.

Concrete takeaway: ask every resolved callback customer for a review within 24 hours of the clean check-in — everyone, no filtering. Same ask, same wording, every time.

Worked example: the Friday blower motor

Example: An HVAC company replaces a blower motor on a Wednesday. Friday the customer calls: the house is warm again. The dispatcher logs it — name, address, "warm air again after blower motor replacement," reported Friday 2:14 PM, Priority A, owner: the dispatcher. Triage text goes out at 2:31 PM. The tech arrives Saturday at 8:05, finds a pinched wire the first tech missed, says so out loud, replaces the wire, and cleans both filters while the panel's off. Monday the office texts the check-in. Customer: "Running great, actually cooler than before." Review ask goes out Monday morning. Review posted Monday afternoon: 5 stars, mentioning "second visit," "showed up early," "fixed it right this time."

That's the whole system in one story: log, triage, priority rules, recovery protocol, check-in, review ask. Five fields and four scripts — no new hire required.

Concrete takeaway: trace one of your recent callback complaints through this system and find where it broke. That's your install plan.

The one-page callback SOP

Here's the whole system as a checklist you can hand to your dispatcher tomorrow morning:

• Log it — every reported problem enters the callback log while the customer is still on the line. Five fields, no exceptions.
• Triage it — acknowledgment within 24 hours, within 2 hours for Priority A. Triage is not the fix; it's the "we heard you."
• Prioritize it — A/B/C rules decide the schedule, not dispatch gut feel. Owner audits the A list daily.
• Recover properly — on-time arrival, own the failure, one visible extra, 24–48-hour check-in.
• Ask for the review — everyone resolved gets the same ask within 24 hours. Never filter, never incentivize.
• Close the loop — log the review asked/received dates. The entry closes when the review loop closes, not when the truck rolls.

Related guides in this series

This post is part of Pillar C, the 5-Star Review Engine series — the pillar post covers the full Google review playbook for contractors, and this callback system is the piece that handles unhappy customers before they become public complaints. For the other half of the response playbook, see How to Respond to Negative Google Reviews (Without Sounding Defensive), and for what to do with the reviews your callbacks earn, see Tech Commissions on Reviews: The Pay Plan That Fills Your 5-Star Pipeline.

The done-for-you version

This post is System 4 from the Leveraged Owner Starter Pack — the done-for-you version with the full step-by-step SOP, every script, the worksheets, and screen-by-screen setup instructions for all 8 systems.

Stats sourced as labeled: BrightLocal 2026 (review statistics); Harvard Business Review 2011 (response-time qualification); 2026 benchmark studies of 250K+ inbound leads (42–47 hour response average)

Keep building your systems

Related guides from the Leveraged Owner blog: