Review Request Automation Without Review Gating

Most businesses ask for reviews when someone remembers to — usually after a job that went especially well. The result is a review profile that reflects memorable jobs rather than typical ones, and long gaps where nothing arrives.

Automating the request fixes the consistency problem. It does not, and should not, try to influence what people write.

What review request automation means

An event in a system you already run — a job marked complete, an invoice paid, an appointment finished — triggers a single request to that customer, with a direct link, logged against their record.

That is the whole mechanism. The value is that it happens every time, on schedule, without depending on anyone's memory.

What should trigger the request

The trigger should be an event that reliably means the work is genuinely finished. Pick the one your team actually updates.

Trigger	Suits	Watch out for
Job marked complete	Home services, trades	Only reliable if technicians update it consistently
Invoice paid	Any business invoicing after work	Delay can be long; may arrive after the memory fades
Appointment completed	Clinics, salons, consultants	Check no-shows do not count as completed
Onboarding finished	Agencies, SaaS, ongoing services	Only where there is a clear milestone

Timing

The window that works is: long enough that the customer has experienced the result, soon enough that they still remember it.

Work type	Suggested delay	Reasoning
Quick repair or callout	Same day to next day	Outcome obvious immediately
Standard service or appointment	1–2 days	Enough to be sure it worked
Installation or larger project	3–7 days	They need to live with it first
Recurring or contract work	After a defined milestone	Not after every visit

One reminder is reasonable if the first request goes unanswered — around three to five days later, on the same channel, and then stop. Two requests is the ceiling.

SMS versus email

SMS gets opened, and for trades and appointment businesses it usually performs better because the customer already has a message thread with you. Keep it to one message with a direct link, and only send where you have a basis to text that number.

Email carries more context and suits B2B or higher-value work where a considered review is more likely. It is also easier to make clearly optional.

For most local service businesses, SMS for the request and email for the reminder is a reasonable split.

Direct review links

Send people straight to the review form, not to your profile page. Every extra step loses a proportion of the people who intended to write something.

Google Business Profile provides a shareable review link from the profile dashboard. Use that rather than a search URL, and test it on a phone — that is where nearly all of these are opened.

Review gating, and why to avoid it

Review gating is the practice of asking customers how their experience was first, then only sending the public review link to the ones who answer positively — routing unhappy customers to a private feedback form instead.

It is widely marketed, and it conflicts with Google's policy. Google's contribution policies prohibit merchants from:

"Discourage or prohibit negative reviews, or selectively solicit positive reviews from customers"

The same policy also prohibits offering "incentives – such as payment, discounts, free goods and/or services - in exchange for posting any review," and states that 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."

What it does permit is straightforward:

"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."

So the compliant version is simple: ask everyone, ask the same way, link them to the same place, and do not try to steer what they say.

Handling negative feedback properly

Not gating does not mean ignoring dissatisfaction. It means separating two things that gating deliberately conflates.

Ask for feedback and ask for reviews as different things. A post-job satisfaction check is a legitimate operational tool. Use it to find problems, route them to someone who can fix them, and improve. Just do not use the answer to decide who gets the review link.

Give staff a suppression switch. If a job went badly, was disputed, or ended in a complaint, the technician or office should be able to block the automated request for that job. That is not gating — you are not filtering by predicted sentiment, you are declining to solicit from someone in an unresolved dispute, which is a reasonable operational decision.

Fix things before asking. If a job needed a return visit, the request should fire after the return visit, not before.

Responding to reviews

The automation ends when the request is sent. Responding is human work and it matters:

• Reply to negative reviews calmly, factually, and without arguing details in public. Offer to take it offline.
• Reply to positive ones briefly — it signals an attentive business to everyone reading.
• Do not dispute reviews reflexively. Removal requests only apply to genuine policy violations, not to reviews you disagree with.

Workflow

Job marked complete in CRM / job system
  ↓
Check: is this eligible?
  ├─ Job disputed / complaint open   → SUPPRESS, notify manager
  ├─ Staff suppression flag set      → SUPPRESS
  ├─ Customer opted out of messaging → SUPPRESS
  ├─ Review already requested        → SUPPRESS (no duplicates)
  └─ Eligible → continue
  ↓
Wait the configured delay for this work type
  ↓
Re-check eligibility (a complaint may have arrived meanwhile)
  ↓
Send ONE request — same message, same link, every customer
  ↓
Log against the contact: requested_at, channel
  ↓
Wait 3–5 days
  ↓
Review left, or customer replied?
  ├─ YES → STOP. Log outcome. Notify the team
  └─ NO  → one reminder, then STOP permanently
  ↓
Mark contact as "review requested" — never ask again for this job

The re-check before sending is worth building. Complaints often arrive in the gap between job completion and the scheduled request.

Avoiding duplicates and handling returning customers

Duplicates are the most common complaint about these systems. Flag the contact when a request is sent, and check that flag before sending anything. A customer with three jobs in a year should not receive three requests.

Returning customers who have already reviewed you should generally not be asked again. If you do ask after a substantial gap and a distinctly different job, make it clearly about that new job — and make it rare.

Measuring it

Metric	What it tells you
Requests sent	Whether the process is running at all
Eligible jobs with no request sent	Where the trigger is failing
Reviews received in the period	The outcome
Requests → reviews ratio	Whether timing and channel are working
Suppression rate, with reasons	Service quality signal worth reading
Average rating over time	Direction of travel

The most useful diagnostic is the second row. If 200 jobs completed and 120 requests went out, the gap is your real problem — not the message wording.

Report requests and reviews as measured facts. Avoid claiming a specific revenue effect from review volume; that link exists but is not something most businesses can isolate.

AI Automation & CRM WorkflowsWe connect your CRM, job completion trigger, and review request process — with suppression rules and no gating.→

Related reading: AI Automation for Home Service Companies and Google Business Profile Checklist.

Frequently asked questions

When is the best time to ask for a review?

After the customer has experienced the result but while it is still fresh — same day for quick repairs, a few days for larger installations. Test within that range rather than treating any single number as correct.

Is review gating actually against the rules?

Google's contribution policies prohibit selectively soliciting positive reviews and discouraging negative ones. So yes, the practice conflicts with the policy — regardless of how commonly it is sold as a feature.

Can we offer a discount for leaving a review?

No. Google's policy explicitly prohibits offering incentives such as payment, discounts, or free goods in exchange for posting a review.

What if we get a negative review?

Respond calmly and publicly, offer to resolve it privately, and fix the underlying cause. A well-handled negative review is more reassuring to readers than an unbroken run of five stars.

How many requests before we stop?

One request and one reminder. Beyond that you are pressuring someone who has already decided not to write anything.

---

If reviews arrive in bursts rather than steadily, ask us to connect your job completion trigger to a review request process — including the suppression rules that keep it appropriate.