On this page
What starts this workflow?
Tagged review-ask.
The workflow, step by step
The table shows the saved connections. Branches are alternative paths, not a single sequence that every contact follows.
| Step | Action | What it does | Next step |
|---|---|---|---|
| 1 | How did we do? | Send a text message | Wait 1 days |
| 2 | Wait 1 days | Wait before the next step | Happy client? |
| 3 | Happy client? | Route by a condition | Send to public review |
| 4 | Send to public review | Send a text message | Native review request |
| 5 | Native review request | Request a review | Alert team · unhappy client to recover (None branch) |
| 6 | Alert team · unhappy client to recover (None branch) | Notify the team | End of this path |
How the branches work
Happy client?
- Happy client?.
- Otherwise: None.
The labels above come from the saved builder. Review the actual condition values in your own account before activation.
Review request setup
Do not filter public review invitations by sentiment or score. Replace any happy-only invitation path with the same neutral review invitation for all eligible customers before using this draft.
Connect it to your business
- Import into a test sub-account and keep the workflow unpublished.
- Connect the trigger to your actual form, calendar, pipeline or contact tag.
- Review the messages and replace all business, booking and review placeholders.
- Connect any sender, phone number, team member or external integration used by the steps.
- Test each branch, replies, contact restrictions and repeat enrollment with contacts you control.
Get the library
Start GoHighLevel through the RocketLauncher partner link and join the community for snapshot access and setup help. This draft must pass its setup and execution checks before activation.
Affiliate link: we earn a commission if you subscribe.
