Journey flows are campaign step sequences, a different concept from
SuperDialog’s conversation-graph flows, which drive turns inside a single
conversation. See SuperDialog for that engine.
The primitives
Tasks are the unit of work inside Execution. A call step does not reimplement
calling - it dispatches a task to the
Calling Engine unchanged, the same
Make Call task you can dispatch
directly today. The journey adds the before and after: when to place the call,
and what its outcome means for the next step.
On the spine
A journey is attached to one entity. It reads the entity’s context when choosing a branch, dispatches interactions through Transport as tasks, and consumes the structured outcome each interaction produces to decide the next step. Every journey transition - started, step completed, waiting, signaled, exited - emits an event, so the rest of your system can react without polling.What stays hidden
The workflow engine underneath - Temporal-style durable execution, timer persistence, retry semantics, replay - is deliberately not exposed. You define flows in terms of steps, waits, and signals; how a journey survives a restart or holds a three-day timer is Unpod’s problem, not a queue you operate.Status
In build. The journey engine - waits, outcome branching, and human approval steps - is shipping in the open. Call steps are real today: dispatch them as tasks and inspect runs. Approval steps ship with the journey engine alongside Teams & Policies.Go deeper
Outcomes
The structured results journeys branch on.
Agent Workforce
The workers that execute call and action steps.
Events
Every journey transition, emitted once.
Make Call task
Dispatch a call as a task today.
Runs API
Inspect task executions.