Skip to main content

Common Journey Patterns

Proven journey structures you can adapt as starting points for your own flows.

Welcome / onboarding series​

Trigger: Event "user_created"
  → Welcome email (immediate)
  → Getting started guide (day 1)
  → Feature tutorial (day 3)
  → Success story (day 7)
  → Check-in email (day 14)

Welcome after a newsletter signup​

Trigger: Event "message.subscribed" (channel = email, scope = channel)
  → Welcome email (immediate)
  → Best sellers (day 2)

message.subscribed fires once when a person becomes subscribed - from a store newsletter, a checkout box, a form, the API or a preference page (The Subscribed event). Add a condition on source (for example store_newsletter) to welcome only one kind of signup; scope = channel keeps a signup that also joins a list from entering twice. Imports and a store's first sync never trigger it.

Abandoned cart​

Trigger: Event "added_to_cart" with no purchase in 1h
  → Wait 1 hour
  → Email: "You left items in your cart"
  → Wait 24 hours
  → SMS: "Items still available + 10% off"
  → Wait 48 hours
  → Email: "Last chance"

Win-back​

Trigger: Audience "inactive_30_days"
  → "We miss you" email
  → Wait 3 days
  → Branch: Returned?
    Yes → Exit
    No  → Personalized offer
  → Wait 7 days
  → Final "last chance" message

WhatsApp support bot​

Trigger: WhatsApp inbound
  Conditions: text contains "help" OR "support"
  → Send WhatsApp reply: "Hi {{ user.firstName }}, how can we help?"
  → Wait Until: user response (24h)
    Responded → Branch: Message contains "order"?
      Yes → Send order status template
      No  → Forward to support team
    No response → Send follow-up