Journeys or Conversations: Which Should You Build?

Build a journey first when your hub promises a specific outcome. Journeys guide users through your method; Conversations provide open-ended support and follow-up around the work users have done.

What a journey is for

A journey takes users toward a defined result through milestones and steps. You decide the sequence, the questions, and the guidance that helps them produce useful work, such as a strategy, plan, or script.

Users don't have to figure out what to ask next. Your method gives them a path.

What a Conversation is for

A Conversation is an open-ended AI chat shaped by your expertise and instructions. There isn't a fixed sequence of steps to complete.

Conversations can use a user's journey progress and read saved step outputs. That makes them useful for discussing, refining, or applying work the user has already done.

See What Are Conversations?.

Why we recommend journeys first

A new user may not know what to ask an open chat. Let them produce something first. Then a Conversation can become "let's work on what you just built" rather than "ask me anything."

You can sequence what appears in the hub in three ways:

• Conversation Settings → Prerequisites: select the steps users need to finish and mark them required. Until those requirements are met, the Conversation doesn't appear in their Conversations list.
• Conversation Settings → Visibility: set conditions for that individual Conversation, such as progress, tags, offers, or dates.
• Conversations → Page Settings → Visibility: set conditions for the whole Conversations section.

Prerequisites currently hide unavailable Conversations from the list; users don't see a locked card or a list of missing steps there.

See How Visibility Rules Work.

When a Conversation-first hub makes sense

Some hubs are designed for ongoing advice or support for people who already have work to discuss. If that open-ended access is the product, Conversations can come first.

Create your Conversations, turn on Published, and leave off prerequisites you don't need. See Create a Conversation.

Make it a deliberate choice. If your hub promises a defined outcome, lead with the journey.

A quick way to decide

• Is there a result you want users to reach through a process you control? Build a Journey.
• Is it support, follow-up, or thinking through existing work? Build a Conversation.
• Not sure? Start with the journey. You can add Conversations later.