When a Review Names Your Tech (Good or Bad)

"Mike was amazing — explained everything and the install looks great." Five stars, and your tech's name is right there in it. Or the other version: "The tech, I think his name was Dave, tracked mud through the house and barely spoke." Either way, a named review just made your response a personnel event. Handle it with a protocol, not your gut.

Named reviews are a special case inside the review engine. The standard response rules still apply — but the stakes are higher, because your team is reading your response too.

Case 1: The glowing named review

This is the easy one, and most owners still underplay it. A public, specific celebration does three jobs: it rewards the tech, it shows future customers that real humans work here, and it teaches the rest of the team exactly which behaviors get recognized.

Then the private half, which matters more than the public half:

• Tell the tech directly, same day. Forward the review or read it aloud. Specific praise from a real customer lands harder than any bonus.
• Say it in front of the team. The Monday meeting, the group chat — wherever your crew gathers. "Mrs. [Name] wrote that Mike explained everything before starting. That's the standard." You're not just rewarding Mike; you're defining excellence for everyone.
• Log it. Named praise goes in the tech's file (or your CRM's employee notes). When review season, raises, or promotions come up, you have a record of customer-verified performance.

Case 2: The critical named review

This is the hard one. The protocol has a public half and a private half, and they must never mix.

The public response — short, warm, no personnel discussion:

Notice what's missing: the tech's name, any defense, any detail. The public response is for future readers, and future readers want to see an owner who takes complaints seriously — not a trial of Dave.

The private half — in this order:

• 1. Call the customer first. Hear the full story before you talk to the tech. You need facts, not a reaction.
• 2. Talk to the tech privately — and lead with curiosity. "Mrs. [Name] wrote that the visit felt rushed and the house wasn't cleaned up. Walk me through that job." Some complaints are fair; some are misunderstandings; some reveal a training gap. You can't know which until you ask.
• 3. Coach the behavior, not the person. "The standard is shoe covers on, drop cloths down, and a 2-minute walkthrough at the end — that's what prevents this" beats "you got a bad review." The review is the symptom; the missing habit is the disease.
• 4. Close the loop with the customer. After the fix (the callback, the apology, the corrected work), the customer gets the follow-up — and potentially the updated-review ask from the recovery playbook.

What never to do

• Never name or blame the tech publicly. "We've spoken with Dave about this" in a public response humiliates your employee in front of the internet and tells future customers your team has problems. Handle people privately, always.
• Never punish from a single review. One named complaint is data; a pattern is a problem. The leaderboard's month-over-month view (see the per-tech leaderboard guide in this series) is how you distinguish them.
• Never ask the customer to remove the tech's name. It's their review of their experience. If the underlying issue gets resolved, many customers update the review themselves — that's the honest path.
• Never disclose personnel actions publicly. "Dave has been retrained" is nobody's business but yours and Dave's.

The pattern level: what named reviews tell you about the team

Zoom out quarterly and read your named reviews as a dataset:

• One tech collects all the praise: find out what they're doing and systematize it. Ride along, document the behaviors, teach them to the team. Excellence that lives in one person's head is a business risk.
• One tech collects all the complaints: that's a coaching plan (or a hiring decision) with a deadline. The reviews are telling you what your gut already knew.
• Nobody gets named: your ask isn't personal enough. Techs who introduce themselves by name and hand over the review card personally get named; anonymous service gets anonymous reviews. The fix is in the ask, not the team.

Training techs to earn named reviews

Named reviews don't happen by accident — they're the product of specific behaviors. Train the three that generate them:

• Introduce yourself by name, twice. At the door ("Hi, I'm Mike with [Business Name]") and at the walkthrough ("I'm Mike — here's what I did today"). Customers can't name a tech whose name they never heard.
• Narrate the work. The two-minute end-of-job walkthrough — what was wrong, what you did, what to watch for — is the single biggest driver of "he explained everything" reviews.
• Leave the card personally. The tech who hands over the review card with the 15-second ask gets named; the card left silently on the counter doesn't. The handoff is the habit.

Put all three on the job-completion checklist. Named reviews are a trained outcome, not a personality lottery.

A worked example

Example: a plumbing shop gets a 2-star review naming a tech: "[Tech] was rough with our old pipes and left a mess under the sink." The owner responds publicly within hours — apology, specifics, personal call promised, no mention of the tech. On the call, the customer describes the mess; the owner sends a senior tech back the next morning to clean up and inspect the work. Privately, the owner walks the named tech through the job: the tech had skipped the drop cloth because "it was a quick job." The coaching is about the standard, not the person — drop cloths on every job, no exceptions, and the 2-minute end-of-job walkthrough gets added to the completion checklist for the whole team. The customer updates to 4 stars, noting the owner's fast response. The review that started as a personnel crisis ends as a team-wide standard upgrade.

Related guides in this series

Named reviews are handled inside the review engine — the pillar post. For the full recovery sequence when the named review is negative, read the 3-star recovery playbook. For making named praise a regular occurrence, the per-tech leaderboard turns recognition into a system.

The done-for-you version

This post is System 4 from the Leveraged Owner Starter Pack — the done-for-you version with the full 5-step setup guide, every script, the worksheets, and complete setup guides for all 8 systems. The Starter Pack includes the named-review response templates for both cases.

Stats sourced as labeled: no third-party statistics used in this post; the worked example is illustrative, not a customer result.

Keep building your systems

Related guides from the Leveraged Owner blog: