Skip to main content

REVIEWS & REPUTATION · September 2026 · ~1 min read

The review request after the ticket closes: cadence for auto repair, salons, vets and CPAs

Google allows you to ask for reviews. It does not allow incentives, selective asking, or pressure while the customer is still on your premises. That last rule is why the request after the ticket closes is safer ground than the one at the counter. The timing below is our recommendation, not research.

01

What does Google actually permit?

Most of what businesses believe about this comes from other businesses. The policy itself is short and specific.

Merchants are expressly allowed to:

"Solicit or encourage the posting of content that does represent a genuine experience, without offering incentives to do so or attempting to influence the rating or the contents of the review."

Asking is fine. Asking everyone is fine. Three things are not.

Incentives. The policy names them: "Offer incentives - such as payment, discounts, free goods and/or services - in exchange for posting any review or revision or removal of a negative review." A free coffee for a review is the textbook case. Google's own tips page repeats it and puts a label on it: offering free or discounted goods in exchange for a review "is considered fake & misleading content and is strictly prohibited."

Selection. "Discourage or prohibit negative reviews, or selectively solicit positive reviews from customers." This is the gating rule, and it catches the most popular workaround in local marketing: a form that asks how the visit went, sends the happy ones to Google and routes the unhappy ones to a private complaint box. That is selective solicitation described exactly.

Pressure and direction. "When soliciting reviews, merchants should not require or pressure users to leave ratings or write reviews while on the premises, nor should they request that specific content be included."

02

Why does asking at the counter carry the risk?

Because the policy singles out that moment.

Read the sentence again: pressure "while on the premises." Handing a customer a tablet at the till, standing there while they type, is the situation the rule describes. A message sent after they have left is not.

This inverts the advice most businesses have been given. "Ask while they are happy and in front of you" is intuitive and it is the riskiest version of the request. The customer who has left can ignore you, which is precisely what makes the ask clean.

The policy also names two specific practices, and they are worth quoting because both are common:

"Merchants requesting that staff solicit a certain number of reviews"

"Merchants requesting that staff solicit reviews that include specific content, including content that identifies a staff member."

A review target for the front desk is not an aggressive reading of the policy. It is the example Google gives. So is asking customers to mention the technician by name, which many shops do believing it helps that person.

One more that catches people: content "based on a conflict of interest" is prohibited, and the policy includes "current or former employment, a contractual or consultory relationship." Staff cannot review their own employer. Neither can the agency running the marketing.

03

Where does federal law sit on top of Google's policy?

Google's policy is a platform's terms. The FTC's Rule on the Use of Consumer Reviews and Testimonials, 16 CFR Part 465, is law, and it has been in force since October 2024. The two overlap without being the same, and the difference is worth stating precisely, because most agency copy on this subject gets it backwards.

Google bans gating. The FTC bans the conduct next to it. There is no clause in Part 465 that says "do not solicit only your happy customers." What the rule does instead is close the exits. Section 465.4 makes it an unfair or deceptive practice to provide incentives "in exchange for, or conditioned expressly or by implication on, the writing or creation of consumer reviews expressing a particular sentiment." Those three words, or by implication, are the ones doing the work. Section 465.7(b) makes it a violation to display a filtered set of reviews on your own site while implying it represents most or all of what was submitted.

The clause worth knowing by heart, though, is the one that protects you rather than the one that catches you. Section 465.2(d) says the prohibitions do not apply to reviews that "resulted from a business making generalized solicitations to purchasers to post reviews or testimonials about their experiences."

Generalized solicitations to purchasers. That is the ask-everyone rule, written into federal regulation as a carve-out. Ask every completed job, do not condition on sentiment, do not script the content, and you are inside the safe harbour by construction.

Two more that catch small businesses in particular.

Section 465.5 governs insider reviews, and the trap is an omission rather than an act. An owner who asks staff to leave a review is liable where the resulting review carries no disclosure of the relationship and the owner "did not instruct that prospective reviewers disclose clearly and conspicuously their relationship to the business." Saying nothing is the violation. Between this and Google's conflict-of-interest rule, the practical answer is that staff should not be reviewing the business at all.

Section 465.7(a) covers the response to a bad review, and it changed the old playbook. It is a violation to use "an unfounded or groundless legal threat, a physical threat, intimidation, or a public false accusation" to prevent a review or get one removed. The boilerplate defamation letter fired at a one-star reviewer is now itself the exposure.

We are not putting a penalty figure in this article. The rule carries civil penalties for knowing violations, the amount adjusts annually, and we have not read the current-year adjustment. This is information, not legal advice.

04

When should the message go out?

Here is our recommendation, and we want to be clear about its status: this is operating judgement from running these systems, not a finding from a study. We have not read a source that establishes an optimal send time, and anyone quoting one to three decimal places is selling something.

The principle is simple. Send when the value of the work is most obvious to the customer, and that moment is different by trade.

TradeWhen we sendWhy then
Auto repairSame day, a few hours after collectionThe car is running better now. By next week it is just a car again
Salon and barberNext morningThey have seen it in their own mirror, and had one round of compliments
VeterinaryTwo to three days after a routine visit, longer after a procedureThe owner needs to see the animal is fine before they can feel good about the visit
CPA and bookkeepingAfter the filing confirmation, not after the invoiceRelief is the emotion you are asking them to write from, and the invoice is the wrong one

The veterinary and CPA rows carry the most judgement. After a procedure, a request that arrives before the owner knows the outcome is asking them to rate something unresolved, and it is the fastest route to a review about anxiety rather than care. After a filing, the invoice and the confirmation often arrive close together, and which one lands first changes the mood the review is written in.

05

How often should you ask, and how many times?

Once, then once more, then stop.

A second message three to four days later, if there is no review, is reasonable and gets a meaningful share of the total. A third is not. The customer has decided, and continuing to ask converts a neutral non-response into an irritation.

Ask every completed job. Not every customer, every completed job, and not a selection of them. This matters for the gating rule, it is the shape of the federal safe harbour, and it also matters for the outcome: a business that asks everyone gets a rating that reflects the business, which is the thing you actually want on the profile. A business that asks selectively gets a rating that reflects its selection.

Google is unsentimental about the mixed result, and says so on its own tips page: "Honest and balanced reviews can help potential customers decide. A mix of positive and negative feedback often feels more trustworthy."

For a trade with repeat visits, a salon or a vet, do not ask the same person every time. Once per customer per year is plenty and keeps the request feeling like a request.

06

What should the message say?

Short, plain, and with no instruction about content.

Name the specific job, because it helps the customer remember what they are writing about. Include the direct link. Say it takes a minute. Do not suggest what to mention, do not ask for five stars, and do not ask them to name the technician.

"Thanks for bringing the Civic in on Tuesday. If you have a minute, a Google review helps other drivers find us: [link]" is the whole thing. Anything longer is reducing the response rate and anything more specific is drifting toward the content-direction rule.

Send it however the customer already talks to you. A shop that texts about the car should text about the review, and a CPA who works over email should email.

One piece of friction to plan for: a customer has to be signed into a Google Account to leave a review at all. That is not a reason to skip anyone, but it does explain a share of the non-responses, and it is why the link matters more than the wording.

07

What would we do first?

If you are starting from nothing, the order is:

Fix who is asked before you fix when. If the current process is that the manager asks the customers who seemed happy, that is the gating problem and no amount of timing improves it. Move to asking on every completed job.

Put the link where the request is made. Most requests fail because the customer has to find your listing. Google's own guidance is to send people to a review link or a QR code generated from your Business Profile, which removes that step entirely.

Then set the timing by the table above, and only then start adjusting it.

Write down who owns the send. The most common failure we see is not policy, it is that the person who used to send them left. That is a systems problem rather than a marketing one, and it is covered in building a review system that survives a staff change.

Be honest with yourself

When you do not need this

If you have fewer than ten reviews, the cadence question is premature. Ask everyone from the last six months, once, and see where you land before designing a system.

If your reviews are already arriving steadily without a process, do not add one. A working informal habit is worth more than a formal system that nobody follows, and formalising it is how businesses accidentally introduce a target.

And if the recent reviews are poor, a faster request cadence makes the problem arrive faster. Fix the thing being reviewed first. More requests against an unresolved service problem is just a louder version of the same signal.

09

Where these numbers come from

There are no statistics in this article, deliberately. Three primary sources, all read in full on 7 September 2026, and every quoted rule is from one of them.

Google's prohibited and restricted content policy for Maps contributions supplies the solicitation rules, the on-premises sentence, the staff-target examples and the conflict-of-interest clause. Google's tips to get more reviews supplies the incentive label, the review link and QR code mechanism, the balanced-reviews line, and the signed-in requirement.

The federal material is from the text of the rule itself, 16 CFR Part 465, not from a summary of it. Sections 465.2(d), 465.4, 465.5 and 465.7 are each a paragraph or two, and the whole part reads in about fifteen minutes.

We have not cited a response rate, an optimal send hour, or a percentage lift from any cadence. We could not read a source for any of them, and this topic is full of numbers that trace back to vendor marketing rather than to data. Where this article gives timing, it is our recommendation from operating the systems, and it is labelled that way.

Related reading

On the timing question across the whole customer journey rather than by trade, when in the customer journey to ask for a review. On the wording, how to ask for a review without sounding desperate. On why the happy-path filter is a bad idea twice over, review gating is not allowed and also makes you rank worse.

For trades where the job ends at a site rather than a counter, asking for reviews at job completion in home services. For practices tracking this alongside everything else, the dental marketing metrics worth tracking monthly. The rest of our writing on this sits in Reviews and Reputation.

If you want a look at your current request process before you change it, email eric@seod.com and describe how it works today. We will tell you whether it has a gating problem, which is the one that matters.

If you would rather we built and ran it, that is part of Search visibility.

Written by

Eric Lee, founder of SEOD

Sixteen years running restaurant, retail and nonprofit operations before starting SEOD in 2016, with more than $54 million in annual P&L managed. He writes these because the same questions come up on the same calls.

More about Eric · How these are sourced

Call Eric Email Eric