Wendell Pruitt looks at 118 reviews and a 4.9 rating. “If the work is good, customers will leave a review.” After twenty-seven years of referrals, asking can feel like begging for something the work should earn.
Good work does not send the request.
Wendell is our illustrative six-truck owner in Lancaster County, not a client case study. He has added three reviews in ninety days. His technicians keep showing up, explaining the repair and charging what they quoted. Much of that experience never becomes visible to the next homeowner.
The answer is not to ask his crew to become salespeople. It is to give a completed visit one more routine step, with someone responsible for making it happen.
Who should get the review request?
Write the eligibility rule before choosing software: send the same neutral invitation after each completed service, maintenance or installation visit when you have an appropriate contact channel and the customer has not been asked recently.
Define “recently” for your process. A ninety-day household cooldown is a reasonable starting rule to test, not a Google requirement. It prevents a maintenance visit and two follow-up visits from creating three requests. Apply it to everyone, whatever they said about the work.
Use operational exclusions: no permission for the proposed channel, invalid contact information, a duplicate visit within the cooldown, or a customer who has declined further requests. Record the reason. “Probably won't give us five stars” is not an exclusion.
Google's review policy prohibits selectively soliciting positive reviews, discouraging negative ones and offering incentives for reviews. It also prohibits pressuring people to review or requesting particular review content. An initial satisfaction survey that reveals the public review link only to happy customers creates exactly the wrong process.
Wendell's objection becomes smaller once the rule is clear. He is not asking the office to identify his biggest fans. He is making the same invitation available to people whose experience he has already worked to earn. The broader question of how many reviews an HVAC company needs starts making more sense when the request process is visible.
Who sends it, and when does it leave the office?
Name an owner and a backup. In a small shop, the owner may initially check the queue; the person handling completed work may send the messages. Assign those roles deliberately. Do not assume “the office” means someone has the task.
Use the completed-visit record as the trigger. Confirm that the customer knows what was completed and has received the normal closeout information. Then send the invitation by the next business day, during your normal customer-contact hours. This is a proposed operating rhythm, not a proven conversion threshold.
A complaint does not change who gets the public link. If a completed visit has an unresolved issue, continue service follow-up separately and apply the same request timing. Do not make access to the review page depend on the customer first declaring the problem resolved.
An automated system can draft or send the invitation when those rules are satisfied. The named person still checks failed messages, duplicate records and exceptions. A short daily queue is enough to start: completed visit, eligible or excluded, channel, request time, owner.
For Wendell, this changes the assignment without changing the service. His technicians do not have to stand in a kitchen waiting for a review. The completed visit reaches a queue, and the queue belongs to somebody.
Which channel and wording make the next step easy?
Use the customer's permitted, preferred channel. A short text can work when that is an agreed way to communicate. Email is appropriate for customers who use it. A printed QR code can offer another route without requiring someone to act while your technician watches.
Copy the correct profile's direct review link and test it on a phone. Google's review help describes using a link or QR code and notes that reviewers need a Google Account. A person who does not want to sign in should not be pushed through a workaround.
Use a neutral message:
Hi [first name], thank you for choosing [company] for your recent HVAC visit. If you'd like to share your experience, you can leave an honest review here: [review link]. Your feedback helps other homeowners. Thank you, [sender name].
Do not add a requested star rating, a list of keywords, a technician's name the customer must mention, or an offer in return. Keep a separate, ordinary way to contact the office for help. That support route should be available to every customer, alongside the same public review opportunity.
Three winters ago, the homeowner on Ridge Road nearly missed Wendell altogether. Her father-in-law's handwritten envelope finally supplied his number. Wendell had installed that furnace in 1998. The link has a modest job: help a current customer's experience travel beyond the people already holding an envelope.
What happens when most people do not reply?
Treat silence as silence. It does not establish that the work was poor, the customer is unhappy or the request needs a more forceful message.
Choose a simple limit: one initial invitation and, if appropriate, one reminder four business days later. That interval is a starting process choice, not an industry benchmark. Stop if the customer declines, has already reviewed, or no longer wants that channel used. Where you cannot reliably match a posted review to the recipient, check the reminder list manually or skip the reminder rather than repeatedly guessing.
A reminder can say:
Hi [first name], one follow-up to our review invitation for your recent visit. If you want to share your experience, the link is [review link]. If you've already reviewed us, thank you. No action is needed otherwise. [Company / sender name].
Then close the request cycle. Do not keep extending it because the customer has not posted. A bounced email calls for correcting contact information through normal service communication, not chasing the person across every channel you can find.
This is the part Wendell can recognize as ordinary courtesy. Asking once, perhaps reminding once, and accepting the customer's choice is a different activity from demanding praise. The limit belongs in the process so nobody has to improvise it on a slow Friday.
Which numbers show whether the system is running?
Separate completed visits, eligible requests, requests sent, successful delivery and new public reviews. A link click is not a posted review. A new review may also arrive without your invitation, so do not present every public review as a tracked result of a particular message.
Here is a separate planning example, not Wendell's job history. Assume 100 completed visits. Twenty fall within the neutral duplicate/cooldown rule, leaving eighty eligible requests. Fifty are sent, and forty-five are delivered.
- Request coverage is 50 ÷ 80 = 62.5%.
- Delivery success is 45 ÷ 50 = 90%.
- Thirty eligible requests were never sent, and five sent messages failed delivery.
The immediate repair is clear without forecasting a single new review. Find why those thirty requests never left the queue and why five failed. Compare new public reviews over a consistent period, but keep attribution uncertainty visible.
Review process completion with the responsible person. Do not give technicians quotas for posted reviews or make their pay depend on five-star feedback. They cannot control whether a customer writes, what rating appears, or how quickly a platform publishes it.
Wendell can name 118 lifetime reviews. That number cannot tell him whether yesterday's eligible customers received an invitation. His three reviews in ninety days are a reason to inspect the process, not a forecast of what the repaired process will produce.
What do you do with criticism once the requests go out?
Keep service recovery separate from collecting public feedback. Read the concern, check the job record and contact the customer through the normal support process. Do not bargain for a changed rating or make resolving the problem conditional on removing a review.
In a public reply, acknowledge the issue you can verify and offer a practical next step. Leave private job details out. Then follow through. A short, specific response is more useful than an argument about who remembers the visit correctly.
Track repeated patterns alongside the requests. If arrival delays keep appearing, inspect your team's true weekly capacity. If homeowners repeatedly misunderstand the visit or fee, check what your website promises. Feedback should improve the next experience, not just change the profile's appearance.
That protects what matters to Wendell: the work. He does not need to defend a flawless account of every visit. He needs the next customer to see an honest business that listens and does what it says it will do.
A review request gives the customer a choice. A system makes sure the office remembers to offer it.
What should be ready before the next completed visit?
Put six things on one page: eligibility and cooldown rules, a named owner and backup, the completed-visit trigger, a tested review link, the initial message and optional reminder, and the rules that stop further contact.
Test the whole path with a dummy job record. Does the correct link open? Does the message identify your company? Can the owner see a failed delivery? Does a declined request suppress the reminder? Can a complaint receive support without changing access to the public link?
At the end of the first week, audit the queue against completed visits. Fix missing steps before adding more automation. Then consider how current, genuine customer proof supports your Google Business Profile and what homeowners look for when hiring. No request schedule guarantees a ranking position.
For Wendell, picture the Ridge Road envelope beside that one-page process. It represents years of trust passed between people. His next step is smaller than a campaign: the next eligible completed visit receives the same honest invitation, whoever the customer is.
The customer still decides what to write. The office finally has a way to remember to ask.