Fixed quote after a free call

Google review automation for local service businesses, done by the rules

For a local service business, Google reviews decide who gets the call. We build a workflow that sends one review request with your Google review link after each completed and paid job, to every eligible customer the same way, alerts the owner to new reviews and drafts replies for approval. No gating, no incentives and nothing private in public replies. A typical build costs $1,000 to $2,500 per workflow and takes about three to four weeks.

The problem

Why local service reviews arrive only when something goes wrong

Happy customers rarely think to leave a review, and asking in person at the end of a job feels awkward. So reviews arrive in bursts, mostly when something went wrong, and the profile does not reflect the work.

Many review tools solve this the wrong way, sending happy customers to Google and unhappy ones to a private form. Google's policy prohibits selectively soliciting positive reviews and offering incentives, and the FTC's final rule bans conditioning incentives on review sentiment and suppressing negative reviews.

What we build

What our review request automation includes

One request per completed job

A short text or email with your Google review link after the job is complete and paid.

Same ask for everyone

Every eligible customer is asked the same way; no rating screen before Google.

Smart timing

Sent after completion at a sensible hour, never to customers with an open complaint, which go to the owner instead.

New-review alerts

The owner is notified of every new review, with low ratings flagged first.

Reply drafts

Polite reply drafts that thank the customer and never reveal job details, for the owner to approve.

Review report

A monthly email of requests sent, reviews received and average reply time.

Who does what

Automation does the chasing, people make the calls.

Every step is marked: what runs on its own, what a member of staff reviews and what stays with a person who decides.
  1. 01 Automated

    Job completed and paid

    The field service app marks the job complete and paid.

  2. 02 Automated

    Request sent

    The customer gets one request with your review link.

  3. 03 Automated

    Review detected

    New reviews are detected and the owner is alerted.

  4. 04 Office review

    Reply drafted

    A reply draft is prepared for the owner to edit.

  5. 05 Owner or office manager decides

    Public replies

    Every public reply and any follow-up with an unhappy customer is decided by the owner.

How it behaves

How Google review request automation behaves

What each person sees and what runs in the background, including what happens when something goes wrong.

What the customer sees

  • One short request after the job, with a direct link
  • No incentive, no rating screen first
  • A thoughtful reply from the owner

What the owner sees

  • Alerts for every new review
  • Reply drafts ready to approve
  • A monthly review report

What the automation does

  • Sends one request per completed job
  • Detects new reviews and drafts replies
  • Logs every request and reply

Edge cases and fallbacks

Customer has an open complaint
No request; the owner is alerted to resolve it first.
Repeat customer with several jobs
Asked at most once in a period you set.
Review mentions a safety or damage issue
Flagged to the owner immediately; the draft avoids admitting or denying specifics.
Google API or workflow outage
Requests queue; review detection catches up when access returns.

Architecture

Review requests for a service business at a glance.

The setup we usually start from. We adapt it to the phone system and practice software you already use.
Job done and paid Field service app n8n workflow Timing and rules Review request Text or email Google profile New reviews Reply draft Nothing private Owner Approves replies
  • Input
  • Logic and services
  • Output
  • AI step
  • People

How it flows

  1. 1 A job marked complete and paid starts the workflow.
  2. 2 n8n checks timing and open complaints, then sends one request with your review link.
  3. 3 New reviews on your Google Business Profile are detected and the owner is alerted.
  4. 4 A reply draft is prepared and the owner approves every public reply.

Project planner

How the project runs, phase by phase.

Typical durations for a first version. Your proposal lists the exact phases, dates and what you sign off at each step.

Google review requests & reputation project plan

Typical time to launch: about 3 weeks, then support

  1. 01

    Discovery

    2 to 3 days

    Current review habits, Google Business Profile access, job completion data and wording.

  2. 02

    Design

    2 to 3 days

    Request wording and timing, exclusions, alert rules and reply guidelines.

  3. 03

    Build

    About 1 week

    Completion trigger, requests, review detection, alerts, drafts and report.

  4. 04

    Shadow run

    About 1 week

    Requests go to a test list while the owner checks timing and wording.

  5. 05

    Launch

    1 to 2 days

    Switch on for completed jobs.

  6. 06

    Support

    Ongoing

    Wording updates and monitoring.

What it runs on

Real products only, connected through the access each vendor provides. See all integrations

n8n Google Business Profile API (reviews) Jobber, Housecall Pro or ServiceM8 (route confirmed per project) Twilio SMS and email Claude or OpenAI for reply drafts Slack or email alerts

Cost estimate

What it costs, line by line.

Estimates to plan with. Your fixed quote follows a free call, once we have seen your systems and volumes.
  • Discovery and design

    Wording, timing, exclusions and reply guidelines.

    $200 – $400

  • Build

    Requests, detection, alerts, drafts and report.

    $500 – $1,300

  • Integrations

    Field service software, Google Business Profile and messaging.

    $150 – $400

  • Testing and shadow run

    Test list run checked by the owner.

    $100 – $250

  • Launch and training

    Switch-on and owner walkthrough.

    $50 – $150

  • Total project estimate

    $1,000 – $2,500

Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. Review detection uses the Google Business Profile API where your account has access. Messaging and n8n are billed to you directly.

Monthly running costs you pay directly

Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.

  • Twilio SMS (US): About $0.0083 per message segment plus carrier fees (Twilio's published US pricing).
  • n8n and AI usage: n8n Cloud from about €20 a month (Starter, billed annually) or self-hosted; reply drafts billed per use.

What pushes cost up

  • Systems without an API, or with integration access that must be requested from the vendor
  • Writing data back into your core system rather than only reading from it
  • Several locations, brands or very different processes to support
  • Custom apps, dashboards or a voice line on top of the workflows

What keeps cost down

  • One location and one clear process to start with
  • Cloud software with a documented API
  • Using tools you already pay for instead of adding new ones
  • Approved wording and sample data ready at the start
Get a fixed quote

Privacy and consent

Rules we design for, with the sources.

General information to plan with, not legal advice. Your counsel or data protection adviser confirms what applies to your practice.

Google: no review gating or incentives

Google prohibits selectively soliciting positive reviews, discouraging negative ones and offering payment, discounts or free services for reviews.

Source: support.google.com

US: FTC rule on reviews

The FTC final rule bans fake reviews, incentives conditioned on sentiment, review suppression through threats or intimidation and undisclosed insider reviews.

Source: www.ftc.gov

US: review request texts

Requests go only to customers of completed jobs, on a registered A2P 10DLC number with opt-outs honoured.

Source: www.twilio.com

How we deliver

Agile delivery, in 1 to 2 week sprints.

We deliver in short Agile sprints using Scrum, so you see working software every one or two weeks instead of waiting for a big reveal at the end.

Every sprint

  1. 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
  2. 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
  3. 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
  4. 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.

How scope stays under control

Product backlog
Every feature, fix and question in one prioritised list you can see at any time.
Acceptance criteria
Plain-language conditions for "done" on each item, agreed before work starts.
Change requests
New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
User acceptance testing (UAT)
Before launch your team tests the real workflow against the acceptance criteria and signs off.

Tools we use

Jira, ClickUp or Trello for the backlogSlack or Microsoft Teams for updatesGitHub for code and version historyLoom or a live call for demos

Project manager / Scrum master

Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.

Business analyst

Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.

Automation engineer

Builds the n8n workflows, integrations, AI steps and error handling.

Backend developer

Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.

Frontend / mobile developer

Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.

QA engineer

Tests every workflow against the acceptance criteria, including edge cases and failure paths.

DevOps engineer

Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.

Who does what at each phase

Free call
Project manager, business analyst
Understand the problem, check it is worth automating and outline a rough range.
Discovery
Business analyst, automation engineer
Map the current process, systems and data, and agree success measures.
Design
Business analyst, automation engineer, backend developer
Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
Sprints
Automation engineer, developers, QA
Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
UAT and launch
QA, DevOps, project manager
Your team tests and signs off, we switch on, monitor closely and train the team.
Support
Automation engineer, DevOps
Stabilisation window, then optional monthly care with monitoring and changes.

A point of contact

One person who can answer questions and approve decisions, with about an hour a week during the project.

Access

Admin or API access to the systems involved, created as separate accounts with the least access needed.

Sample data

Real but non-sensitive records (or de-identified ones) so we can design and test against reality.

Approved wording

Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.

Vendor agreements

Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.

Time for testing

A few hours from the people who will use the system, for the demos and user acceptance testing.

Working system

Workflows, integrations and any apps running in your accounts, under your keys.

Documentation

Workflow specification, data-flow map, run book and exported workflow files.

Training

A walkthrough for the team and a short recorded video for new starters.

Handover

All access, credentials and code handed over; you can keep us or take it in-house.

Stabilisation window

Fixes for anything that does not meet the agreed acceptance criteria after launch.

Support options after launch

  • No plan

    You run it yourselves after the stabilisation window and contact us when you need a change.

  • Monthly care

    Monitoring, error alerts, small changes and updates each month, with an agreed response time.

  • Priority care

    Faster response times for business-critical workflows and a monthly review call.

How a project moves through our team

Free call PM and analyst Discovery Process and data Design Spec and backlog Sprints Build, test, demo Your review Accept or adjust UAT and launch Sign-off, go live Support Monitor and improve
  • Input
  • Logic and services
  • People
  • Output
  • Data

How it flows

  1. 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
  2. 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
  3. 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
  4. 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.

FAQ

Google review requests & reputation questions, answered.

It means automatically asking customers for a Google review after a completed job, and alerting you to new reviews. Done properly, every customer is asked the same way with no incentives.

No, and you should not want it to. Google prohibits selectively asking for positive reviews, and the FTC rule bans incentives tied to sentiment. We exclude only customers with an open complaint, who go to the owner to resolve first.

We draft replies; the owner approves every public reply. Drafts thank the customer and never confirm details of the job or the address.

We trigger requests from job completion in your field service software, using the route your plan supports. Some of those tools have their own review features; we use them where they fit.

We generate your direct Google review link and put it in the message. A QR code version can go on invoices and van signage.

Requests sent, reviews received, average rating over time and average time to an approved reply.

Free 20-minute call

Want this for your local service?

Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.

Book a free 20-minute call