Personal project
A review request sent at the right moment.
After a completed service the customer gets a short question about how it went. A happy one receives a direct link to leave a Google review. An unhappy one reaches an internal list before they post publicly.
The problem it solves
Google reviews are among the strongest factors when choosing a local business, and most satisfied customers never leave one, because nobody asked, or asked two weeks too late. Unhappy customers do the opposite: they write straight away and in public.
Built with
- n8n
- Google Business Profile API
- Airtable
Related service
Automation and AI agentsHow it works
- 1The system detects that a service finished and waits a set period
- 2The customer gets one short rating question, not a ten-field form
- 3A high rating leads to a ready link for leaving a Google review
- 4A low rating opens a question about details and lands on an internal fix list
- 5Items on that list become tasks with deadlines, not notes nobody remembers
What I would refine for a client
There is one thing to be careful about and I will say it plainly: filtering who even sees the Google link can breach Google's own policy. In a client version everyone gets the link, and the split exists only so a complaint reaches support faster than it reaches the internet.
Do you have a similar process?
Describe it in a few sentences. I will tell you whether it can be automated and what it would cost — including when the answer is that it is not worth it.