Key Takeaways
- Timing is the single biggest variable in review conversion — requests sent within two hours of job completion consistently outperform those sent days later.
- A functioning review request workflow has five components: a trigger, a delay, a personalised message, a tracking mechanism, and a single follow-up cap.
- Automating the request removes the human memory problem, but the message itself still needs to feel personal to avoid low open rates.
- Suppression logic — skipping contacts who have already clicked or left a review — is what separates a professional workflow from a spam loop.
- Private feedback routing before the public review link reduces negative public reviews without violating Google's review policies.
Most service businesses lose their best reviews to bad timing. A customer ends a call satisfied, the engineer drives away from a completed job, or a client marks a project closed — and nobody asks for a review for three days, by which point the moment has passed. The result is a Google Business Profile with a handful of reviews that does not reflect the actual volume of happy customers the business serves. Building a structured review request workflow solves that problem at the process level, not the individual level.
This article explains how to design that workflow from trigger to tracking, what to include in each step, and where most businesses quietly lose reviews they should have earned.
If you're looking for expert help in this area, explore how our local SEO packages can drive measurable results for your business.
Why Timing Beats Volume in Review Requests
The instinct for most businesses is to send more review requests — bigger lists, more channels, higher frequency. What the evidence from real workflow deployments shows is that timing matters more than volume. A customer who just received a completed service confirmation is at their highest point of satisfaction. That window closes quickly. Ask them the next morning and you catch the tail end of it. Ask them three days later and you are asking them to recall a feeling they have largely moved on from.
This is not an abstract principle. Contractors, cleaning companies, and field service businesses that have rebuilt their outreach around a post-completion trigger — rather than a weekly batch email — report meaningful lifts in response rates without increasing the number of contacts they reach out to. The message is the same; the moment is different.
The Human Memory Problem
Manual review requests fail not because staff do not want to ask, but because the busiest moment — the end of a job — is also the moment when asking is easiest to forget. The job manager is already thinking about the next appointment. The customer-facing technician is packing equipment. Nobody is thinking about a Google review. This is why automation is not optional for a scalable workflow: it removes the dependency on human memory at exactly the moment human memory is least available.
The Five Components of a Review Request Workflow
A professional review request workflow is not a single email. It is a small system with five distinct components, each of which can fail independently. Understanding each one is what separates a workflow that compounds over time from one that fires occasionally and produces inconsistent results.
1. The Trigger
The trigger is the event that starts the workflow. For service businesses, the cleanest trigger is a job status change — specifically, a field in your CRM, job management software, or even a shared spreadsheet moving to "Completed" or "Closed". This is more reliable than a time-based trigger because it is tied to a real-world outcome, not a calendar event.
If your business does not use a CRM, a Google Form submitted by the technician at job close — feeding into a Google Sheet — is a workable low-cost alternative. The key is that the trigger is deliberate and human-confirmed, not assumed from an appointment time.
2. The Delay
A delay of one to three hours between trigger and send is the standard that field service businesses have arrived at through testing. Long enough for the customer to be home or settled; short enough that the job is still vivid. For B2B service businesses where the contact is a procurement manager rather than an end user, a delay of twenty-four hours is often more appropriate — immediately post-completion can feel transactional when the relationship is ongoing.
3. The Personalised Message
Generic review requests underperform because they feel like mass marketing — because they are. The minimum level of personalisation that improves open and click rates is: the customer's first name, the specific service or job type completed, and a direct link to your Google review page. That direct link matters. Sending someone to your homepage and asking them to find where to leave a review is friction that costs you reviews.
Your Google review link follows a predictable format: https://search.google.com/local/writereview?placeid=YOUR_PLACE_ID. You can find your Place ID via the Google Places API Place ID documentation. Build that link into your template once, and every automated message will send customers directly to the review compose screen.
4. Suppression Logic
This is the component that most basic workflow setups skip, and it is also the one that creates the most reputational risk. Suppression logic means that before any message sends, the system checks whether that contact has already received a request, clicked the review link, or submitted private feedback. If any of those conditions are true, the message does not send.
Without suppression, a customer who left a five-star review gets another request a week later. They feel harassed; they sometimes edit their original review downward. A spreadsheet-based system handles this with a simple conditional column. A CRM handles it with contact tags or workflow exit conditions. Either works — the logic just needs to exist.
5. The Single Follow-Up
One follow-up, sent three days after the original request to contacts who did not click, is a standard and reasonable practice. Beyond one follow-up, you are in diminishing returns territory and beginning to irritate people who have implicitly signalled they are not interested. The follow-up message should acknowledge that you sent a request previously — "I wanted to follow up on the note we sent after your recent service" — rather than pretending it is a first contact.
The Case for Private Feedback Routing Before the Public Link
One design decision that separates sophisticated review workflows from simple request blasts is a private feedback step before the public review link. The approach works like this: the initial message asks the customer to rate their experience on a simple one-to-five scale, or a binary "happy / not fully satisfied" choice. Customers who indicate satisfaction see the Google review link. Customers who indicate a problem are routed to a private feedback form that goes directly to the service manager.
This approach is not about suppressing negative reviews — that would violate Google's review policies, which prohibit selectively soliciting only positive reviews. It is about giving dissatisfied customers a faster, easier route to resolve their issue privately before they reach for a public channel out of frustration. Most dissatisfied customers do not want to leave a one-star review — they want someone to fix the problem. Giving them that path first serves both the customer and the business.
The important detail: the Google review link must remain accessible to all customers. The private feedback path is an additional option, not a gate.
Tools and Build Options for Different Business Sizes
The right tooling depends on what systems the business already uses, not on which review management platform has the best marketing. Below is a practical comparison by business type and existing infrastructure.
| Business Type | Existing System | Recommended Approach |
|---|---|---|
| Solo trader / small contractor | Google Sheets + Gmail | n8n or Zapier: Sheet row triggers Gmail send on status change |
| Multi-technician field service | Job management software (e.g. ServiceM8, Jobber) | Native integration or webhook to email/SMS tool |
| SME with a CRM | HubSpot, Salesforce, or similar | Workflow automation built natively within the CRM |
| Multi-location business | Reputation management platform | Dedicated tool (e.g. Birdeye, Podium, or GHL) with location routing |
For businesses using Jobber, the platform includes a built-in review request feature triggered by job completion — a reasonable starting point before building anything custom. For businesses with more complex needs, low-code automation tools such as n8n allow full control over suppression logic, multi-channel sends, and error alerting without the cost of an enterprise reputation platform.
SMS vs Email: Which Channel Converts
SMS open rates are substantially higher than email across most consumer-facing service categories. The trade-off is that SMS requires explicit consent in most markets and carries a per-message cost. For B2B clients, email remains the appropriate channel. For consumer services — trades, cleaning, healthcare, beauty — SMS sends to consented contacts routinely outperform email for review conversion. A hybrid approach that defaults to SMS where consent exists and falls back to email is the most effective design, provided your tooling supports the conditional routing.
What to Measure and What to Ignore
Most review workflow dashboards surface open rates, click rates, and review page redirects. Only one of those numbers is the one that matters for local SEO: published reviews. A redirect to your Google review page does not confirm a review was written. Track your actual Google Business Profile review count weekly, segment it by month, and compare the growth rate before and after you implemented the workflow. That is your proof of performance.
Open rate is useful for diagnosing subject line problems. Click rate is useful for diagnosing message or link problems. Neither tells you whether the workflow is generating the business outcome — more reviews — that it was built to produce.
Review Velocity and Local Ranking
Google's local ranking algorithm considers both the total number of reviews and the recency of reviews. A business with 200 reviews earned over five years and no new reviews in the last six months will be outranked by a competitor with 80 reviews earned recently, because recency signals ongoing relevance to Google's systems. A consistent review request workflow — one that generates a steady trickle of new reviews rather than occasional spikes — is more valuable for local ranking than any single campaign that produces a burst of reviews followed by silence.
FAQ
Is it against Google's policies to automate review requests?
No. Automating the request is permitted. What Google's policies prohibit is offering incentives for reviews, selectively only asking customers you believe will leave positive reviews, and posting fake reviews. A workflow that sends every customer a post-completion request — regardless of whether you expect a positive outcome — is compliant. The private feedback routing described above is also compliant, provided the Google review link remains accessible to all customers.
How many reviews do I need before local rankings improve?
There is no published threshold from Google, and any specific number cited as a target is directional rather than confirmed. What is consistent across local SEO case studies is that businesses with more recent reviews, higher average star ratings, and regular review velocity tend to appear more prominently in local pack results than businesses with stagnant review profiles. Focus on the rate of new reviews, not a fixed total target.
Should I ask for reviews on platforms other than Google?
For most local businesses, Google is the priority because Google Business Profile reviews are the primary driver of local pack visibility. Secondary platforms — Trustpilot, Yelp, industry-specific directories — matter for specific sectors (hospitality, healthcare, legal) where those platforms have genuine consumer trust. Build the Google workflow first; expand to other platforms only after that is producing consistent results.
What if a customer leaves a negative review despite the workflow?
Respond publicly within 48 hours, professionally and specifically. Do not be defensive, do not offer a refund in the public reply (take that conversation private), and do not repeat the complaint back in detail. A well-written response to a negative review is visible to every prospective customer who reads the review — it often does more for trust than the negative review does against it. Flag the underlying service issue internally and track whether it recurs.
What to Do This Week
The workflow does not need to be perfect on day one. It needs to exist. Here are the specific first steps to take before the end of the week:
- Identify your trigger point. What does "job complete" look like in your current system? A CRM field, a spreadsheet column, a form submission? Name it specifically — that is your workflow trigger.
- Find your Google Place ID using the Places API documentation and build your direct review link. Test it by clicking it yourself and confirming it opens the review compose screen.
- Write one message template. First name, job type, direct review link, one sentence explaining why reviews help the business. Keep it under 100 words for SMS compatibility.
- Set up a suppression list. Even if it is a manual column in a spreadsheet labelled "Review Requested (Y/N)", having it means you will not double-contact customers as the workflow scales.
- Choose your tool. If you have no automation in place, sign up for a free-tier account with n8n or Zapier today and connect it to your trigger source and your email or SMS provider. A basic workflow can be live within a single session.
The businesses that consistently outrank their local competitors on Google Maps are rarely the ones with the best service. They are the ones with the best systems for capturing proof of good service. A structured review request workflow is that system.
Related Reading
Written by
Indexed ResearchResearch team, Indexed · Reviewed by Anjan Luthra
The Indexed research team tracks how search and AI answer engines behave, tests what actually moves visibility, and publishes the reference material behind our client work.
What to read next
One email a week
How to turn search into revenue.
One idea a week from live client work — what we changed, what it was worth, and what you can take from it.
One email a week. Unsubscribe in one click.