One text, seven days after the job, that catches the small problem before it becomes a 1-star review — and turns the silent majority of happy customers into your review pipeline. The wording, the reply triage, and the recovery playbook.
System 8 from the Leveraged Owner Starter Pack
The water heater you installed last Tuesday has a slow drip at the fitting. The customer noticed it on day three. She didn't call — she figured she'd "keep an eye on it." On day twelve she'll Google your business name, click "write a review," and type a 2-star story about the leak you never knew existed. A single text on day seven — "everything working well?" — would have surfaced the drip on day seven, gotten a tech out on day eight, and turned the story into a 5-star review about responsive service. The check-in is the safety net at the end of the job lifecycle pillar: the last chance to catch a problem while it's still fixable quietly.
Day one is too soon — the customer hasn't lived with the work yet, and everything feels fine through the halo of completion. Day thirty is too late — small problems have hardened into grievances, and the grievance has already been told to neighbors. Day seven is the sweet spot: long enough for the customer to have used the system, noticed the drip, heard the noise, or felt the uneven cooling — but recent enough that the fix still feels like good service rather than damage control. It also sits in the perfect gap in your post-job sequence: summary text at completion, invoice within the hour, review ask at day two or three, check-in at day seven. Each message has its own day and its own job.
The check-in must feel like a person caring, not a system polling. One question, the tech's name if possible, and an explicit invitation to report small stuff:
Hi [First Name], [Tech Name] from [Business Name] checking in — it's been about a week since [we installed your water heater]. Everything working well on your end? Even small stuff — a drip, a noise, anything that doesn't seem quite right — I'd rather hear about it now while it's easy to fix. Just reply here. — [Business Name]
"Even small stuff" is the load-bearing phrase. Customers don't report small problems because they don't want to bother you — they need explicit permission to mention the drip. Without that phrase, the check-in gets "all good!" replies from customers who are quietly watching a leak. With it, you get the truth.
A variant for jobs where the customer wasn't home or the work was external (roofing, outdoor electrical):
Hi [First Name], [Your Name] from [Business Name] — a week since [the roof replacement], wanted to check in. Noticed anything since we've been gone — a shingle scrap we missed, a gutter question, anything at all? Reply here and we'll take care of it. — [Business Name]
Every reply falls into one of three buckets. Triage them the same day — the check-in creates an obligation to act on what it finds:
Bucket 1 — "All good!" (the majority). Thank them warmly and close the loop. If they haven't left a review yet, this is your second and final review ask — the satisfaction is confirmed, the timing is perfect.
Great to hear, [First Name]! Thanks again for trusting us with it. If you have 60 seconds, an honest Google review would mean a lot — here's the link: [review link]. Either way, we're here if you ever need us. — [Business Name]
Bucket 2 — Small issue (drip, noise, question). Acknowledge immediately, schedule the fix within 48 hours, and frame it as warranty service — because it is. The speed of this response is the entire ballgame: a small issue fixed in 48 hours becomes a loyalty story; a small issue acknowledged and scheduled "sometime next week" becomes the review you were trying to prevent.
Thanks for telling me, [First Name] — that's exactly what this check-in is for. I'll have [Tech Name] out [tomorrow / Thursday] to take care of [the drip] — no charge, that's on us. Does [morning / afternoon] work better for you? — [Business Name]
Bucket 3 — Real problem (not working, major concern). Escalate immediately: owner or manager calls within the hour, same-day or next-day visit scheduled, and the de-escalation framework takes over from there. The check-in did its job — it surfaced the problem while you can still own the solution. A customer with a real problem who gets a call within the hour thinks "they take this seriously." The same customer discovering it themselves at day fourteen thinks "they don't care."
About half your check-ins will get no reply. Don't chase them — one check-in is the system; two is pestering. But do log the non-response pattern: customers who don't reply to the check-in and didn't leave a review are your quiet middle — satisfied enough not to complain, not engaged enough to advocate. They go into the reactivation pool for the seasonal campaigns, where the next touch is value (a checklist, a maintenance reminder) rather than another ask. The check-in's job with them is done: no news is acceptable news.
The check-in asks about satisfaction — and then, for happy customers, includes a review link. This is not review gating as long as the review ask goes to every customer equally regardless of their answer. The line you must never cross: using the check-in replies to decide who gets the review link. If Bucket 2 and Bucket 3 customers never see a review ask but Bucket 1 always does, you've built a filtering system — and filtering unhappy customers before the review ask violates Google's policy. The safe structure: the review ask goes out to everyone at day two or three (before the check-in), and the check-in's Bucket 1 message is a reminder, not the first ask. Same ask, same link, everybody. Never pay for reviews or offer incentives for them — also a Google policy violation. This is general information, not legal advice.
The check-in is a pure automation candidate: job status → "complete" starts a 7-day timer → timer fires the template with the customer's name, the job description, and the tech's name merged in. The only manual part is the triage — and triage is fast because the buckets are pre-defined. Set up the notification so replies to check-in texts hit the office inbox with priority tagging; a Bucket 3 reply sitting unread for a day defeats the entire purpose. One page of setup guide covers the three buckets, the response templates, and the escalation rule. The system runs itself; humans handle only the replies that need humans.
The 7-day check-in is the safety net at the end of the Full & Calm Calendar pillar — confirmations, arrival windows, dispatch updates, and the job summary carry the customer through the job, and the check-in makes sure nothing went wrong after you left. It's also the feeder for the review engine: the happiest customers, identified at exactly the right moment.
The full setup guide, all four copy-paste scripts (including the owner notification), the "Your Numbers" missed-call worksheet, and the step-by-step setup guide — free, no catch. Fix your missed calls this week.
Stop missing calls and chase reviews on autopilot: the AI Automation Starter Pack is $27 one-time: https://leveragedowner.com/starter-pack/
This post is System 8 from the Leveraged Owner Starter Pack — the done-for-you version with the full step-by-step setup guide, every script, the worksheets, and click-by-click setup instructions for all 8 systems. The check-in templates, the three-bucket triage responses, and the automation trigger setup are pre-written and ready to install.
Stats sourced as labeled: no statistics used in this post.
Related guides from the Leveraged Owner blog:
HVAC summer maintenance reminder campaign: the pre-summer booking push that fills June with tune-ups — filter reminders, offers, and capacity smoothing.
Plumber winter email campaign: the December pipe-freeze prevention sequence that books calls before pipes burst — helpful content that fills January every year.
You don't need to write setup guides — you can talk them. The voice-memo method for documenting business processes: record, transcribe, clean up, done in 30