Intern
What you actually do
Four tests: completed, too-early, unhappy, already-reviewed. Links correct. You are not designing a poster.
Library / Wire / Reviews are a journey after a completed job, not a QR panic at the register
GBP reviews compound local. The leak is asking at the wrong moment, from the wrong contact, with no suppression after they reviewed, and no route for a private complaint. Wire the ask to a completed job in GHL — visit three, install done, treatment finished — with an SMS that you can stop, and a negative path that does not start with 'please Google us'.
GBP reviews compound local. The leak is asking at the wrong moment, from the wrong contact, with no suppression after they reviewed, and no route for a private complaint. Wire the ask to a completed job in GHL — visit three, install done, treatment finished — with an SMS that you can stop, and a negative path that does not start with 'please Google us'.
The trigger is a completed outcome, not a feeling that 'we should get more reviews'. Dental recare, HVAC install, med-spa treatment, coaching session three — name it.
Wait until they have received the outcome. Asking while the truck is still in the driveway, or at the front desk when they are paying, trains fake reviews and angry ones.
One ask, one reminder, stop. Weekly blasts to the whole list 'please review us' is how you look desperate and how you ping people who already did.
Negative path: 'reply R and we will make it right' or a private form. Do not funnel complaints onto GBP on purpose.
Multi-location: the link must match the location field. The wrong GBP is how you decorate a competitor’s map.
Intern
Four tests: completed, too-early, unhappy, already-reviewed. Links correct. You are not designing a poster.
Operator
Reviews are a journey. Protect the trigger and the unhappy path. One primary listing. No whole-list blasts.
CEO
Local demand compounds on GBP. Asking the wrong people is a reputation leak. Completed-job write-in is the system.
GHL contact, completed-job stage or tag, review_asked_on, review_done flag, GBP link, SMS/email template, negative-feedback form (private), suppression, location if multi-site.
Job completed (named exit rule) → wait window → review ask SMS/email with GBP link
Reply 'done' or webhook if you have it → review_done; never ask again
Unhappy reply → private form/task, not a public link; owner human
No completed job → no ask. Checkout panic QR is not a stage
Exit rule: which stage or tag means 'ask is allowed'. Not inquiry, not booked, not paid-if-service-not-done.
Why: Asking leads for reviews is how you get one-star stories about sales.
Done when: Trigger written. A test contact in inquiry does not get the ask.
Wait N hours/days after completion. Max two messages. review_asked_on field. Stop on reply or on review_done.
Why: Unbounded asks are spam. Zero wait is panic.
Done when: A completed test gets message one after the wait, not instantly at checkout.
If multi-site, location on the contact chooses the link. Single site: one canonical URL, not a search query 'google us'.
Why: Search queries send people to the wrong listing.
Done when: Test contact for location A gets listing A.
Keyword or form: creates a task, notifies owner, does not send the GBP link. Close the loop in GHL.
Why: Public-first is how you manufacture one-stars you could have fixed.
Done when: A test 'unhappy' reply creates a task and no review SMS follow-up.
When you know they reviewed (reply, staff tag, or a tool), set review_done. Exclude from the journey forever for that location.
Why: Asking twice is how you annoy promoters.
Done when: A tagged reviewer is out of the next ask cycle.
Put a test contact in completed. Wait the window (or temporarily shorten in a test workflow). Confirm GBP link and location. Test unhappy keyword. Tag a reviewer and confirm suppression. Do not print new QR posters this week unless the journey is live.
A reputation SaaS, a postcard campaign, or 'review us and get $10' until the completed-job trigger exists. Paying for reviews on an unowned journey is how you also pay for complaints.
Front desk QR. Occasional blast to the whole list. Unhappy patients sent to Google. Multi-location links mixed. No review_done. GHL never knew the job finished. That is hope with a sticker.
Completed → wait → ask. Unhappy → task. Reviewer → suppressed. Wrong stage → no ask. Location A → listing A.
Desk QR catches whoever is standing there, including the frustrated. Completed-job + delay + unhappy path is an operating system. QR can exist as a backup, not the only move.
Tools still need a trigger from GHL. Without completed-job write-in, the tool is another blast engine.
One primary (usually GBP for local). A second channel is a second journey or you will double-ask. Pick.
This week
This week: completed trigger, wait, cap, location URL, unhappy path, suppression field. Pause list-wide review blasts.
A full calendar and an empty pipeline is two databases.
Read ↗A high score in a CSV is not a qualified opportunity.
Read ↗If the thank-you does not change the contact, the page was a brochure.
Read ↗If paid lives in Stripe and the opportunity is still open, reporting is theatre.
Read ↗Working notes
The minimum CRM, pipeline, and nurture spec before you add more pages. Request the file. It arrives by email — not a public dump, not a drip of slogans.
Email and WhatsApp stay open. A call is for installing the system — not for a tour of tools.