Go To action

Overview

In Stack, the “Go To” event is a powerful tool for navigating contacts through your workflows. It allows you to seamlessly direct contacts to specific points within a workflow based on certain criteria or triggers. By utilizing the “Go To” action, you can create more efficient workflows, ensuring contacts receive personalized experiences tailored to their interactions or behaviors.

Action Name

Go To

Action Description

The “Go To” action enables you to redirect a contact to another point in the workflow. This is particularly useful when you want to reroute a contact through a different branch or revisit previous actions if certain conditions aren’t met. Note that the “Go To” action can only be added as the last step of a workflow or branch and cannot be placed between actions.

How to Configure

Step-by-Step Guide

1. Navigate to Workflow Actions:

   • Access the automation or workflow settings in Stack.

2. Choose a Workflow Action:

   • Select “Go To” from the list of available actions.

3. Name Your Action:

   • Enter a descriptive name for the action, such as “Go to Wait action.”

4. Save:

   • Click the “Save” button.

5. Configure:

   • All actions will be highlighted. Click on the action where you want the contact to proceed.

De-link

If you need to change the previously selected action, click on the “Disconnect GoTo” icon under the Go To action. Then, select another action where you want the contact to proceed.

Example

Sending Emails to Customers Who Have Purchased Items

Scenario: An online retailer aims to re-engage customers who have abandoned their carts and avoid sending emails to those who have already made a purchase.

Trigger Setup:

• Trigger: Abandoned Checkout
• Name: Abandoned Checkout
• Filters:
  • 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 reminding the customer of the items left in their cart and offering an incentive (e.g., discount).
• Wait: Pause for 1 day.
• If/Else: Add a condition to check if the user has a “Purchased” tag. Contacts with the tag proceed through the first branch, while others follow the None branch.
• Email (Branch 2): Send another email to remind the contact of the abandoned cart.
• Wait (Branch 2): Add a wait step with a condition if the tag added is “Purchased”.
• Go To (Branch 1): Add a Go To action to direct the contact to the wait step in the second branch.

Outcome: This automation helps recover potentially lost sales by re-engaging customers who abandoned their carts while ensuring emails are not sent to those who have already completed their purchases.

How to Use the Go-To Action

1. Add a Go-To Event: Start by inserting a Go-To action into your workflow where you want the redirection to occur.
2. Connect the Events: Simply draw a line from the Go-To event to the target event you want your contacts to jump to.

And that’s it! With these simple steps, you can efficiently guide contacts through your workflow, ensuring a smooth and customized journey.