Same neutral review link, every time.
The Birdeye-inspired pattern, reimplemented with original copy: every eligible customer receives the same public review option, regardless of sentiment. Low-rating feedback also triggers a private service alert.
What triggers this workflow
CRM event fires when an eligible job is marked complete and the agreed cooling-off window has passed.
Source: Job-complete CRM event
Workflow steps
- Twenty CRM + n8nEligibility checkCustomer opted in to receive messages; job marked complete; cooling-off passed.
- Listmonk + TwilioSend neutral requestSame neutral SMS or email with the same public review link.
- Listmonk + TwilioReminder (optional)One polite reminder if the customer hasn't engaged after the agreed window.
- ChatwootPrivate alertLow rating triggers a private alert — additional, never a replacement.
Tools used
Human handoff
The private alert always reaches a person
The same public review link goes to every eligible customer. The private service alert is additional — it goes to the operations lead, with the customer's history attached.
- Customer reports a service issue
- Customer is a repeat or high-value client
- Rating drops below the agreed threshold
Try it in your browser
Edit the sample inputs, choose a branch, and see what the workflow produces. The sandbox runs offline — no accounts touched, no messages sent.
Try it in your browser
Edit the inputs, pick a branch, and see what the workflow produces. Runs entirely in your browser — no messages are sent, no accounts are touched.
1. Job completed
Job "exterior repaint" marked complete for Hannah. Same public review link for all eligible customers.
2. Branch handling
Hi Hannah, thanks for choosing Coastline Painting for your exterior repaint. If you have a moment, a Google review helps other locals find us → coastline.example/r/abc — Coastline Painting
Every eligible customer gets the same link, regardless of sentiment. Low-rating feedback also routes to a private service alert — additional, never a replacement.
Sample data only. Numbers, names and messages are placeholders for illustration. Wire the live workflow separately using the setup notes below.
n8n workflow template
n8n template — LGM 04 Review Request (SIMULATED, inactive). Ships with active: false — no live integrations are wired. See the setup section below for the wiring checklist, and download the JSON to inspect or import it.
Setup for production
Wiring it for production
Live deployment needs the job-complete event, consent flags and a single review link.
- Wire the job-complete event as the trigger; add a cooling-off window (default 24h).
- Define the same public review link for all eligible customers.
- Set the rating threshold for the private-alert branch (default 3/5).
- Document the reminder cadence (default one reminder after 7 days).
Production prerequisites
- Same public review link agreed internally
- Consent flags maintained in Twenty CRM
- Operations lead on call for private alerts
Nothing here runs by default. Configuration has to be in place before any live send, booking or contact write.
Questions
Does this filter out negative reviews?
No. Every eligible customer gets the same public review link. The private alert is additional; it never hides, delays or replaces the public path.
What about Google review policy?
We follow Google's review solicitation policy and Australian Consumer Law — same neutral request, no incentives, no sentiment-based filtering.
More demos you can run in your browser
Review Request Automation across the platform
Want this review request automation workflow running on your stack?
Pick the demo you're curious about or describe your own. We'll come back with what a real deployment looks like for your business — the workflow, the prerequisites, the people involved.