In this SOP we’ll go over a new feature in HighLevel’s “Workflows”, which is a beta feature used to create client journey flows based on triggers and conditions. This feature is what’s coming to “revolutionize” the digital marketing industry using GHL, according to many experts in GHL. “Triggers” and “Campaigns” may become obsolete by the end of this year if Workflows continues enhancing their features.
- To access “Workflows”, make sure you click on the tab for Workflows under “Opportunities”.
- Once you’ve created one and provided a trigger that initiates the workflow, you’ll be able to provide your first actions.
- The “If/Else” step allows you to split a workflow journey into paths, based on conditions:
– such as if the contact has a specific tag,
– based on current month (ex: December/holiday),
– has the contact replied to a message from this workflow?,
– or did they enter this workflow via workflow trigger #1 or workflow trigger #2 (meaning the triggers you’ve specified at the beginning of the workflow).
- If you want to send a lead/contact different messaging, whether or not they have a specific tag, we can explore an example.
In the example above, we can see that the first workflow trigger is when a contact clicks a “Redeem Offer” trigger link.
- The first step is an “If/Else” condition, that checks to see if the contact already has a tag for “offer_pending”.
- If they do have that tag, they go down the “YES” path, removing that “offer_pending” tag, and replacing it with an “offer_redeemed” tag and then sending them an email letting them know that they’ve successfully redeemed the offer.
- However, if the contact did not have the “offer pending” tag, they would have gone down the “NO” path. An email would be sent saying that the offer had been redeemed.
For the “If/Else” conditional, we need to make sure to define the two segments (yes / no paths) like the following, for example when a customer replies:
Make sure to add “Wait” steps, in order to clearly define your client journey path.
Another powerful example for “If/Else” condition, is to use it for splitting the journey based on what workflow trigger brought them into the workflow.
Let’s say we have a workflow that sends a dentist an email after an appointment, asking how the appointment with that contact went, and the email contains a trigger link for each of the possible outcomes, such as: “Showed and bought”, “No show” and “Showed but didn’t buy”.
We need to figure out which link the dentist clicked, and we can do so by using the If/Else condition.