Workflow Action - Go To

Overview

The Go-To event allows you to jump contacts from one place to another in Workflows. This action enables you to direct contacts to specific points in the workflow based on certain criteria or triggers. By using the "Go To" action, you can streamline your workflows, ensuring that contacts receive tailored experiences based on their interactions or behaviours. Action NameGo ToAction DescriptionUsing the "Go To" action you can send a contact to another action in the workflow.

This action is useful when you want to send the contact through another branch or sending the contact back to few actions if a certain condition is not met. A point to remember is that the "Go To" action can only be added as a last step of a workflow or a branch. It can't be added between actions. How to ConfigureStep-by-Step GuideNavigate to Workflow Actions: Access the automation or workflow settings in your platform.

• Choose a Workflow Action: Select "Go To" from the list of available actions.
• Name Your Action: Enter a descriptive name for the trigger, such as "Go to Wait action."Save: Click on Save button.
• Configure: All the actions will be highlighted and you can click on the action where you want the contact to proceed.

De-link - Now what if you want to change the action which was selected earlier. Click on the "Disconnect GoTo" icon under the Go To action and then you can select another action where you want the contact to proceed.

Example

Sending Emails to customers who have purchased the itemsScenario: An online retailer wants to re-engage customers who have not purchased the items and don't want to send an email to the customers who have already bought.

• Trigger Setup: Trigger: Abandoned CheckoutName: Abandoned CheckoutFilters: Duration (minutes): 10 (trigger the workflow if the cart is abandoned for more than 10 minutes)Cart Value: Greater than 50 (trigger the workflow only if the cart value exceeds $50)Workflow Actions: Email Notification: Send a personalized email to the customer, reminding them of the items left in their cart and offering an incentive (e.g., discount).
• Wait: Wait for 1 dayIf/Else: Add if else condition to check if the user has "Purchased" tag.

The contact will go through the first branch if the tag is present and the None branch if tag is not present.

• Email (Branch 2): Send another email to the contact reminding them of the abandoned cart.
• Wait (Branch 2): Add a wait step with a condition if tag added is "Purchased"Go To (Branch 1): Add a Go to action that will take the contact directly to the wait step in the second branchOutcome: This automation helps recover potentially lost sales by re-engaging customers who abandoned their carts and do not send an email to the customers who have already purchased the items.