How to Automate Google Reviews for Any Local Business

Google reviews are one of the clearest ranking signals in local SEO. Google’s own documentation confirms that quantity, recency, and response rate all factor into local search rankings. A business collecting reviews consistently outranks a business with better reviews that stopped growing.

The problem is that review collection is friction-heavy. Staff forget to ask. Customers intend to leave a review and never do. The moments of peak customer satisfaction — right after a job is done, when a problem is solved — pass without action. By the time someone thinks to follow up, the goodwill has faded and the customer has moved on.

Automating Google reviews removes that friction entirely. The request goes out at exactly the right moment, personalized to the customer and the service, without requiring anyone on staff to remember anything. Here’s how to build that system.

The Principle: Trigger at Peak Satisfaction

The single most important variable in review request conversion is timing. Send the request too early and the service isn’t complete. Send it too late and sentiment has cooled. The optimal window is within 2–4 hours of a completed transaction — when the experience is fresh and emotion is highest.

For most local businesses, that trigger event already exists in their software stack: a job marked complete in a field service app, an appointment status updated in a booking tool, a payment confirmed in a POS system. Whatever the business already uses to track completed work is your trigger point.

The automation builds on top of that trigger. The moment it fires, a personalized review request email is generated and queued. No manual step required.

Why Email Works Better Than You Think

There’s an assumption in local marketing that SMS outperforms email for review requests. For raw open rates, that’s often true. For actual review completion, the gap narrows significantly — and email has meaningful practical advantages.

Email is simpler to build, easier to comply with, and free to send at scale. There are no carrier filtering issues, no per-message costs, and no opt-in requirements beyond standard CAN-SPAM compliance (which transactional emails from a known sender already satisfy). The Gmail API is well-documented, integrates natively with Make.com and n8n, and every business already has a Gmail or Google Workspace account.

More importantly: a well-personalized email from a real business address, referencing the specific service just completed, achieves 10–20% end-to-end review conversion. That’s comparable to the best-case SMS results — without the compliance overhead and cost.

Build it in email. Ship it. The outcome is the same.

The 3-Email Sequence

The review automation system that consistently performs best uses three emails sent over one week.

Email 1 — Day 0 (sent within 2 hours of job completion): Thank you, no ask.

The first email is purely a thank you. No review link, no ask. This is intentional. Leading with appreciation rather than a request sets a warmer tone, establishes that you’re a business that cares, and primes the customer for the request that follows.

Use Claude to generate this email dynamically from the job completion data:

Write a warm, 3-sentence thank you email from [BUSINESS NAME] to [FIRST NAME]
for completing a [SERVICE TYPE] today. Staff member: [STAFF NAME or "our team"].
No review ask. No links. Tone: genuine small business, not corporate.

Email 2 — Day 3: The direct ask.

Three days gives the customer time to live with the result. The AC is running, the drain is clear, the teeth look better. Satisfaction at Day 3 is often higher than immediately post-service. This is where the review request goes — confident, direct, brief, with the Google review link prominent.

Target length: 60–80 words. Include one sentence explaining why reviews matter to a small local business. Link text: “Leave us a Google review” — nothing clever, just clear.

Email 3 — Day 7: The final nudge.

One more email, explicitly framed as the last one. Two sentences maximum. Easy to ignore without guilt. This email drives roughly 25–30% of total reviews generated by the sequence — don’t skip it.

Keep the Day 7 subject line light: “Last note from us, [First Name]” consistently outperforms anything more formal.

Building the Automation in Make.com

Make.com is the fastest path to a working review automation system without writing custom code. The scenario structure:

Module 1 — Webhook trigger. Set up a custom webhook URL in Make.com and configure your CRM or booking platform to POST to it when a job is completed. Most platforms (Jobber, ServiceTitan, Square, Acuity, Mindbody) support this natively or via Zapier-style integration.

Module 2 — Claude API call. Use the HTTP module to call the Anthropic API with your Day 0 email prompt, injecting the customer name, service type, and staff name from the webhook payload. Store the generated subject and body.

Module 3 — Gmail send. Connect the business’s Google Workspace account via OAuth2 and send the Day 0 email immediately.

Module 4 — Data store entry. Log the customer’s email address, first name, job details, and sequence status to a Make.com data store or Google Sheet.

Module 5 — Scheduled Day 3 send. A second scenario runs daily, checks the data store for entries where Day 3 email hasn’t been sent and the job completed 3 days ago, generates the review request email via Claude, and sends via Gmail.

Module 6 — Day 7 nudge. Same pattern as Module 5, firing 7 days after job completion.

Total build time for an experienced Make.com user: 3–4 hours. For someone new to the platform: 6–8 hours. The template is reusable across clients.

What to Customize Per Business

The system runs the same for every client, but five variables need to be configured per deployment:

Google review link. Get the direct review URL from the Google Business Profile (search the business → click “Write a review” → copy URL) and put it through Bitly or a similar shortener for click tracking. This is the most important field — a broken or missing link kills the entire sequence.

Business name and type. Feeds into every Claude prompt. “Mesa Family Dentistry” and “dental practice” produce very different email copy than “Elite Plumbing” and “plumber.”

Service catalog. Map the service type labels from the CRM to human-readable descriptions that Claude can use. “SVC_TYPE_004” needs to become “air conditioning tune-up” before it goes into the prompt.

Sending address. Use a Google Workspace address that matches the business domain — reviews@businessname.com or hello@businessname.com. Emails from a matching domain address have better deliverability and look more legitimate than a generic Gmail account.

Tone instruction. A single line in each prompt: Tone: friendly and professional, like a family-owned business or Tone: concise and direct, like a busy trade contractor. This prevents the copy from feeling off-brand.

Real Results Benchmarks

With this three-email sequence deployed correctly:

Email open rate: 45–60% (transactional, from a known sender, referencing a recent interaction)
Review link click rate: 25–35% of openers
Review completion rate: 40–55% of clickers
Overall conversion (jobs → published reviews): 10–20%

For a business completing 25 jobs per week, that’s 2–5 new Google reviews every week. In 90 days, a business that had 22 reviews can have 50+. In six months, 80–100. That trajectory transforms how the business appears in local search and dramatically improves map pack performance.

The businesses that see the highest conversion rates are those where the Day 0 email genuinely sounds like it came from a person. The more specific the copy — mentioning the actual service completed, the staff member by name, a detail about the job — the higher the click-through on the Day 3 request.

Common Setup Mistakes

Sending the review ask in Email 1. Counterintuitive, but it lowers overall conversion. The warm-up email matters. Keep it as a pure thank you.

Using a personal Gmail address. Emails from yourname@gmail.com look like individual outreach at first, but at volume they trigger spam filters. Use a business domain address.

Not testing the sequence end-to-end before launch. Send the entire 3-email sequence to yourself across 7 days before deploying to a live client. Catch the formatting issues, the broken links, the wrong business name, before a real customer sees them.

Forgetting to handle the “no staff name” case. When the staff field is null, the prompt fallback should produce “our team” — not a blank space or the literal word “undefined.”

The Compounding Effect

A review automation system doesn’t just improve rankings in the short term. It builds a durable competitive advantage. A business with 200 reviews at 4.6 stars has social proof that a competitor with 30 reviews can’t match in the sales conversation, on the website, or in the map pack.

Reviews are one of the few SEO assets that visibly differentiate two otherwise-equal businesses to a real human making a real decision. The ranking benefit is real. The conversion benefit is real. The cost of building the system is a one-time investment that pays indefinitely.

Download the pSEO Playbook →