Review Generation for Clients: A Compliant Review Request Playbook

Timing and channel: the backbone of white label review generation

The single biggest lever in any review request program isn't the message — it's timing. Ask too soon and the customer hasn't formed an opinion yet. Ask too late and the experience has faded, or they've moved on. For most local businesses, the window is narrow: a few hours to a few days after the service, purchase, or appointment is when recall and willingness to act are both highest. Building this timing into a repeatable, per-client workflow — rather than relying on a front-desk employee to remember — is most of what a white label reputation management program is actually doing behind the scenes. If your agency hasn't formalized that setup yet, our guide on white label reputation management walks through the broader structure this request workflow plugs into.

Channel choice depends heavily on the business type, which is why a one-size-fits-all script rarely works across a mixed client roster.

Service businesses (contractors, cleaners, auto repair, home services)

These clients have a clear, singular moment to trigger from: job completion. Email works well because the customer has usually already exchanged email with the business for invoicing or scheduling. SMS converts faster for time-sensitive trades — a plumber or HVAC tech finishing a same-day call — because the visit is still fresh and a phone link is easier to tap than an email is to open later. Trigger the request within a few hours of job completion, tied to the invoice or job-closed event in whatever system the client already uses.

Retail, hospitality, and walk-in businesses

Walk-in businesses — restaurants, salons, retail stores — don't always capture an email or phone number at the point of sale, which is where physical prompts (covered below) carry more of the weight. When you do have contact information, from a loyalty program, online order, or reservation system, SMS sent within a few hours of the visit tends to outperform email for this group, since the decision window is short and attention spans around a casual purchase are shorter still.

Multi-location and franchise clients

For clients with multiple locations, the request needs to route to the correct Google Business Profile for the specific location the customer visited — not a generic corporate listing. A review requested for the wrong location either bounces or, worse, posts against the wrong profile and has to be cleaned up later. Build the location mapping into your request workflow once, per client, rather than improvising it each time a request goes out.

Message templates that ask everyone the same way

Every template below follows the same rule: it asks for a review, full stop. It doesn't ask "was everything perfect?" before deciding whether to show the review link, and it doesn't vary in tone based on anything other than the client's brand voice. The same message, sent the same way, goes to every customer who completed a service or purchase — that consistency is what keeps the program compliant, as covered in the compliance section below.

Email templates

Template A — post-service, direct ask:

Subject: How did we do, [Customer First Name]?
Hi [Customer First Name],
Thanks for choosing [Business Name] for your recent [service type]. We'd really appreciate it if you could take a minute to share your experience on Google — it helps other [city/area] customers find us and helps our team know what we're doing right.
[Leave a Google Review — button/link]
Thank you,
The [Business Name] Team

Template B — recurring customer, lighter touch:

Subject: Got a minute for [Business Name]?
Hi [Customer First Name],
You've been a customer of ours for a while now, and we'd love to hear what you think. If you have 60 seconds, a Google review would mean a lot to our small team.
[Leave a Review — link]
We read every one — thank you for your support.
[Business Name]

SMS templates

Template C — short, service-based:

Hi [Customer First Name], it's [Business Name]. Thanks for having us out today! If you have a moment, we'd love a quick Google review: [link]. Reply STOP to opt out.

Template D — casual, retail/hospitality:

Thanks for stopping by [Business Name] today! Mind leaving us a quick review? [link] Means a lot to our team. — [Business Name]

Keep variables to a minimum — the point of a template is that it's identical for every recipient. If a client wants a warmer or more formal voice, adjust the template once for that client and keep it consistent, rather than editing message-by-message based on who's receiving it.

QR codes and in-person asks for physical locations

For businesses with a physical storefront, a printed or digital QR code closes the gap that email and SMS can't reach: customers who never gave contact information at all. A QR code on a receipt, table tent, invoice, or at checkout routes straight to the review form, and it has the advantage of being available to literally everyone who walks through the door — which is the compliance-friendly default, since there's no selection happening at all.

In-person verbal asks ("if you enjoyed your visit, we'd appreciate a Google review — there's a QR code on your receipt") are fine as a general prompt offered to every customer, but they get risky fast if a staff member starts using judgment about who to say it to. Train staff to either say it to everyone or not say it at all — never to size up a customer's mood first. Google's policy explicitly bars merchants from requiring or pressuring customers to leave a review while still on the premises, so if a client has a shared checkout kiosk or iPad for this purpose, that flow needs to move to a takeaway QR code or a follow-up text instead.

Handling unhappy customers without gating the review

This is the part of the workflow where agencies most often get into trouble, usually with good intentions. The instinct is to protect the client's public rating by giving unhappy customers an "off-ramp" before they reach Google — a satisfaction survey that quietly routes four- and five-star respondents to the public review link while sending one-, two-, and three-star respondents to a private form instead. That pattern is called review gating, and it is explicitly against the rules. It doesn't matter whether the filtering happens through a human, a script, or a survey branch — if who gets asked publicly depends on predicted sentiment, it's gating.

The compliant pattern looks different: every customer gets the same public review request, sent the same way, on the same timing, regardless of how the service went. A private feedback option can exist alongside that request — a line in the same email offering to flag an issue directly with the business, or a separate "tell us more" channel — but it has to be an addition, never a substitute. A customer who had a bad experience should be free to use the private channel, the public one, both, or neither; the business just can't be the one deciding for them by hiding the public link.

In practice, this means your workflow sends the public review request to 100% of eligible customers, and separately offers a "something not right? Let us know directly" option that doesn't gate anything — it's just another way for a customer to reach the business, running in parallel rather than in sequence. For the actual handling of the negative reviews that do land publicly — tone, timing, what to say and what to avoid — our guide on responding to negative reviews covers that in depth, and pairs well with this playbook once requests start generating a full mix of ratings.

What Google and the FTC actually say about review solicitation

It's worth being precise about this rather than working from folklore, because the rules have teeth now. Google's own prohibited and restricted content policy bars reviews that aren't based on a genuine experience, and separately prohibits offering any incentive — payment, discounts, free goods or services — in exchange for posting, editing, or removing a review. Google is also explicit that businesses may encourage customers to leave a review of a genuine experience, but may not attempt to influence the rating or the content of what gets written, and the policy further bars merchants from asking staff to solicit reviews that mention specific content, including a staff member's name.

On the federal side, the FTC's final rule on fake and deceptive reviews, in effect since October 2024, prohibits businesses from buying reviews, from using reviews by people who didn't actually have the experience they describe, and from conditioning compensation or incentives on a review expressing a particular sentiment. The rule's text on incentivized reviews doesn't literally name "review gating," but the FTC has said directly that selectively inviting only customers expected to leave positive feedback — while steering everyone else to a private channel — can still violate the FTC Act's general ban on unfair or deceptive practices if it results in a more positive public review set than would otherwise exist. Civil penalties for knowing violations run into the tens of thousands of dollars per violation, per client, across a roster.

The takeaway for every account team: no survey branch, satisfaction gate, or staff judgment call should ever determine who receives the public review request. Build the workflow so that's structurally impossible — one customer list, one send, every time. For the broader process this ask sits inside — intake, routing, reporting — see our guide on building a customer review management process.

Measuring request-to-review conversion across clients

Once requests are going out consistently and compliantly, the next job is knowing whether they're working — and whether that answer differs by client. The core metric is conversion from request to posted review, worth tracking at three stages rather than collapsing it into one number:

Across a client roster, these numbers are rarely identical, and that's useful information rather than noise. A contractor client with a four-day average time-to-review might benefit from an SMS follow-up two days after the initial email; a restaurant client with a low click-to-post rate might need a shorter, more direct template. You don't need a Tailwind-specific analytics feature to track any of this — the same reporting cadence you already use for other client KPIs works fine, as long as you're pulling the same three numbers for every client so comparisons mean something.

What you shouldn't do with this data is quietly narrow who gets asked. A low conversion rate is a reason to improve the message, timing, or channel — never a reason to start asking a more favorable slice of customers. The moment "optimizing conversion" means "asking fewer unhappy people," the program has drifted back into gating with a metrics-driven excuse attached.

Running this well for one client is a few hours of setup. Running it for twenty clients, each with different business types, channels, and compliance edge cases, is where most agencies decide they need a platform built for exactly this rather than a spreadsheet and a shared inbox. If that's where you are, our reputation management for agencies page walks through how Tailwind handles multi-client review requests, client-branded touchpoints, and reporting in one place — and once review volume picks up, the next workflow problem is usually replying to all of them, which our companion guide on AI review replies for agency clients covers in detail.