> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tranthor.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Journeys

> Automate messaging with the Tranthor AI Journey Builder.

Journeys are the core automation primitive in Tranthor. The **AI Journey Builder** lets you visually create and manage messaging workflows that adapt to user behavior—no code required.

1. [Overview](#overview)
2. [AI Journey Builder](#ai-journey-builder)
3. [Journey Status](#journey-status)

## Overview

Journeys define *who* gets messaged, *when*, and *with what content*. Each journey starts with an [Entry Node](/resources/journey-nodes/entry) and ends with an [Exit Node](/resources/journey-nodes/exit). In between, you can arrange any combination of nodes to create rich, personalized experiences.

<Frame>
  ![Minimal Journey]()
</Frame>

By default, a new journey does nothing—until you add messaging logic with the AI Builder.

<Frame>
  ![Minimal Useful Journey]()
</Frame>

Tranthor’s AI Builder recommends nodes and paths as you design, optimizing your journey for engagement and compliance.

## AI Journey Builder

The AI Journey Builder provides an intuitive drag-and-drop interface, powered by Tranthor AI. As you build, it suggests the best sequence of nodes and highlights opportunities to personalize or automate.

**Journey Nodes:**

* [Entry Node](/resources/journey-nodes/entry): Define which users can enter and when.
* [Message Node](/resources/journey-nodes/message): Send personalized messages across channels.
* [Wait For Node](/resources/journey-nodes/wait-for): Pause until a user meets a condition (e.g., enters a segment).
* [Delay Node](/resources/journey-nodes/delay): Wait a specific amount of time before progressing.
* [Segment Split Node](/resources/journey-nodes/segment-split): Branch logic for different user segments.
* [Exit Node](/resources/journey-nodes/exit): Mark a user’s journey as complete.

<Frame>
  ![AI Builder Example]()
</Frame>

The AI can also auto-generate common journeys (e.g., onboarding, re-engagement, transactional), ensuring best practices and compliance.

## Journey Status

Journeys move through three statuses:

* **Not Started**: Draft state; users cannot enter.
* **Running**: Live; eligible users enter and progress automatically.
* **Paused**: Entry is halted; current users continue until a message step, which is skipped if not resumed.

<Frame>
  ![Journey Configure]()
</Frame>

**Not Started**

Journeys remain inactive until started.

**Running**

Users matching the entry node’s criteria are admitted and guided through the workflow.

**Paused**

No new entries. Users already inside proceed, but pending messages are skipped until the journey is unpaused.

> Let Tranthor’s AI Builder handle the details—focus on your goals, and quickly automate journeys from onboarding, to product adoption, to re-engagement.