Industry packs are ready for eight industries. Start from journeys built for yours.Browse packs
JourneysUpdated 30 Oct 2026

Use goals and wait steps correctly

Waits control timing and goals control when a journey stops. Together they prevent duplicate and late messages.

AS
Written by Ananya Sharma
Lifecycle Marketing Lead
  • Published30 Oct 2026
  • Read time1 min
  • Length116 words
Share this guide

Wait steps

A wait delays the next step by a time, or until a time window opens, such as 9 am to 8 pm. A wait can also count from a date attribute, for example three days before a due date.

Goals

A goal is an event or a condition that ends the journey for a person. Set the goal to the outcome you want, such as order_placed. If someone reaches it while waiting, they leave the journey and receive nothing more.

Common mistakes

Forgetting the goal is the main one. A cart reminder without an order goal can message someone after they have bought. Another is a wait that ends at night; use a time window to avoid it.

Frequently asked questions

Can a journey have more than one goal?

Yes. Reaching any goal ends the journey.

What time zone do windows use?

The one you choose for the workspace or the journey.

Was this guide helpful?Your answer helps us improve our guides.

See your own customers in Flowfox this week.

Start a free workspace, connect a data source and send your first journey. Or book a guided demo.