Your rating drifts down even when the work is good, because the physics are unfair: a delighted customer forgets you by dinner, an annoyed one writes the review from your parking lot.
What it does
When a job is marked done, the workflow waits a couple of hours, then texts the customer: how did we do today, one to ten? High scores get a warm thank-you and the Google review link while the goodwill is fresh. Low scores ping you immediately with the details, so the problem gets fixed while it is still a conversation instead of a public one-star story, and the customer hears from a human the same day.
One honesty note: Google’s rules do not allow asking only happy customers for reviews. This workflow asks everyone for feedback first and routes the unhappy ones to you fast, which is both compliant and better business. The save is not hiding the bad score; it is fixing the thing the same afternoon.
How it works
A sheet trigger fires when a job flips to done. After the delay, Twilio sends the score request. Inbound replies come back through a webhook, get matched to the job by phone number, and branch: 9 or 10 gets the review invite, anything lower alerts you on Slack and tells the customer the owner will call today. Every score lands back in the sheet, so you also get a running quality number per crew.
Setup
- Import the workflow file into your n8n instance.
- Connect the jobs sheet (or the one-tap form your crew marks jobs done with).
- Connect Twilio for the feedback texts and point its inbound messaging at the workflow's webhook.
- Paste your Google review link and your private feedback link into the two marked nodes.
- Mark a test job done with your own number and try both a 10 and a 6.
The template runs on n8n, any recent version, cloud or self-hosted. Every place that needs one of your accounts is marked with a note inside the workflow.
Get the workflow
Rather have this running in your business without touching a single node? That is the actual job. Write to hello@nurho.net or start with the ROI calculator to see if it is even worth automating.