The 30-Day Check-In: Catch the Problem Before the One-Star Review

A new review notification lands on your phone while you're eating lunch in the truck. You tap it half expecting a nice one. One star. "Cabinet door came loose about a week after you left, called twice, never heard back." The job was a month ago. You'd honestly half forgotten it.

Here's the part that stings. You'd have fixed that door in ten minutes. A screw backed out, it happens, it's nothing. But you never got the chance, because the customer never called you. They stewed for three weeks, then they typed.

That gap is the whole problem in one story. The distance between "something's a little off" and "I'm telling the internet" is usually a few weeks of silence, and hardly anyone picks up the phone to mention a small thing. A short check-in a few weeks after the job closes that gap. It catches the loose fixture while the fix is still cheap, private, and yours.

Why a quiet gripe beats a public one

When a customer tells you directly, you get to be the good guy. You call back, you swing by, you tighten the screw. The story they tell their neighbor turns into "and they came right back out, no fuss." That can beat a job that went perfectly, because it shows you stand behind your work.

Tell that same thing to Google instead, and you've lost all of it. The fix is still ten minutes, except now it's ten minutes plus a public reply, plus those stars sitting there for the next person who's comparing you to the other guy. Same screw. Completely different price tag.

Nothing about a check-in makes problems happen less often. It just changes where they land. You're moving the complaint off the review page and into your own inbox, where you can actually do something about it.

Match the timing to the work

The right moment depends on what you did, not on a tidy round number. Thirty days is a fine default, but the real aim is to ask after the work has had a chance to show a flaw, and before the customer has written you off.

Think about when your kind of job tends to reveal trouble:

Installs and repairs (cabinets, fixtures, appliances): two to four weeks, once it's been used every day and anything loose has had time to work itself loose.
Outdoor work (decks, paint, concrete, roofing): after the first real rain or the first cold snap, which might be next week or next month.
Short shelf-life services (a haircut, a detail, a massage): a few days, while they still remember how it felt.
Big projects (a remodel, a landscape): check at two weeks and again after a season, since different problems show up on different clocks.

You don't have to make this call every time. Set the delay once for each type of job, and let the timing ride on something you already track, the completion date sitting in your scheduler or your invoice.

Make it a plain yes-or-no

Your check-in should be the easiest text the customer gets all week. One question, answerable from a stoplight. Something like: "Hi Dana, it's Mike from Smith Plumbing. Quick check, is the new water heater still running the way it should? Just reply yes or no."

Keep it human and keep it short. You're not running a survey. A long form with star ratings and comment boxes gets ignored, and worse, it reads like homework from a company instead of a note from the person who did the work.

Resist the urge to pile on. No coupon, no newsletter signup, no "and if you're happy, would you mind leaving us...". Mixing in an ask is exactly how an honest quality check starts to smell like marketing, and people can smell it from a mile off.

Route the "no" to you, let the "yes" close itself

Most replies will be some flavor of "yep, all good," and those don't need you at all. The machine can log the reply, mark the job closed, and move on. You never see them, which is the whole point. Your attention isn't the thing that scales, so don't spend it on good news.

It's the "no" (or the "well, actually") that matters, and it should land in front of you the second it arrives. A text, a flagged email, a buzz on your phone, whatever you'll actually notice. Then a real person, probably you, picks up the phone and makes it right.

One simple rule of thumb for what the system does with each reply:

A clear yes: log it, close the job, say nothing to you.
Any no, or anything you can't cleanly read as a yes: flag it to you right away, with the customer's name, the job, and their exact words.
No reply at all: one gentle nudge after a few days, then let it rest. Silence usually means fine, and nobody likes being pestered.

Now the honest limit. A machine can tell "no" from "yes" and route it, and that handles most of the traffic. What it can't do is read "it's fine, I guess" and hear the problem hiding in the tone. That read is yours. Set the system to flag anything that isn't a clean yes, and lean toward looping yourself in. A false alarm costs you a two-minute call. A missed one costs you a star. Machines run the relay; you keep the judgment.

Keep it separate from the review ask

This is quality control, full stop. It is not the moment to ask for a Google review, and the two should never ride in the same message. They have opposite jobs. The check-in asks "did we mess anything up?" The review ask says "glad that went well, would you tell people?"

Run them in the right order and they feed each other. The check-in catches an unhappy customer in private and hands you the chance to fix it. Only after someone's told you they're happy does it make any sense to ask them to say so in public. Ask everyone for a review, no matter how the job landed, and you're basically handing the one annoyed customer a microphone.

So sequence it. Check in first. Fix whatever needs fixing. Then, for the folks who said all good, let the review ask go out a little later as its own separate note.

Worth setting up this week

None of this needs anything fancy to get going. Pick one job type and build out from there.

Pick your most common job and choose one delay for it (two weeks, four weeks, after the first rain). Just one. You can tune the rest later.
Write the one-line message in your own voice, with your name and the customer's. Read it out loud. If it sounds like a company wrote it, cut words until it doesn't.
Decide where a "no" lands so you can't miss it. Your phone as a text, most likely, not an inbox you open on Sundays.
Set the "yes" replies to log and close themselves. Then promise yourself you won't go looking at them.
Run it by hand on last month's jobs first, so you trust the timing and the wording before you let it go automatic.

Once it's humming, it runs quietly in the background: one text a few weeks after each job, the quiet yeses closing themselves, the rare no buzzing your phone while there's still time to fix it for the price of a screw. That's the sort of relay we build for small shops at TellRobots, the repetitive part handled so the part that needs a human, the call, the fix, the relationship, stays with you.