On this page
What starts this workflow?
Inbound message received.
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 | Classify message intent | Generate an AI response | Tag intent-complaint |
| 2 | Tag intent-complaint | Add a contact tag | Is complaint? |
| 3 | Is complaint? | Route by a condition | Alert team of complaint |
| 4 | Alert team of complaint | Notify the team | Tag intent-booking |
| 5 | Tag intent-booking | Add a contact tag | Tag intent-question |
| 6 | Tag intent-question | Add a contact tag | Tag intent-unsubscribe |
| 7 | Tag intent-unsubscribe | Add a contact tag | Tag intent-referral |
| 8 | Tag intent-referral | Add a contact tag | End of this path |
How the branches work
Is complaint?
- Is complaint?.
- Otherwise: None.
The labels above come from the saved builder. Review the actual condition values in your own account before activation.
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.
