Skip to main content
You don’t create a journey in Runwita. The journey creates itself, on the back of the first engagement you process. This is intentional: journeys without engagements are empty filing cabinets, and Runwita refuses to encourage that. The only thing you do directly is feed the Inbox. The first time the AI processes a transcript or note that doesn’t match any existing journey, it suggests a new one. You confirm or rename. The journey is born with its first engagement already attached.

​
What a journey is

A journey is a customer, a project, an initiative, anything you’ll have multiple engagements about over weeks or months. “Maplewood Inn, digital ordering rollout”. “Internal, Q3 hiring plan”. “Year 11 Lit students, semester two reading scheme”. The journey is what gives every engagement somewhere to land, and what lets topics persist across them.

​
How a journey gets created

1

Drop something into the Inbox

A transcript file, a pasted email, notes typed in directly. See Prerequisites for the three ways to feed the Inbox.
2

Click Process with AI on the inbox item

The AI reads the content and extracts a structured engagement: title, date, summary, sections, decisions, actions, attendees, topics.
3

Review the journey suggestion

On the Review screen, Runwita matches the engagement against your existing journeys. With no journeys yet, it suggests creating a new one and pre-fills a customer and a use case based on what it read.
Review screen showing the AI's new-journey suggestion with pre-filled customer and use case
4

Confirm or rename, then save

Edit the customer and use case if the AI’s guess is off. Click Save. The journey appears in the Journeys list with this engagement already on its timeline.
From here, every subsequent engagement that mentions the same customer or use case will match into this journey automatically. The matcher gets sharper as the journey accumulates context.

​
What the journey gives you

A new journey is mostly a container, but it unlocks four things as engagements stack up:
  • A landing page for the journey itself, with the customer name, use case, and (eventually) a summary written by the AI.
  • Topic tracking, threads of discussion that span multiple engagements, with their own status (open, blocked, decided, resolved). See Topics.
  • Decisions and actions, every decision and follow-up across every engagement on the journey, in one timeline.
  • People, the stakeholders who keep showing up. Runwita pulls them out of attendees and gives you a relationship map per journey.
You won’t see most of this until the journey has two or three engagements. The first one creates the journey; the second starts to show patterns.

​
A naming tip

When you confirm or rename a new journey, spend ten seconds on the use case field. It becomes part of the journey’s identity for the AI matcher. Vague labels like “Engagement” or “Working sessions” make future matching harder. Specific labels like “Phase 2 rollout” or “Renewal and expansion conversations” give the matcher something concrete to work with when the next engagement arrives.

​
What’s next

Capture your first engagement

The full Inbox to journey loop, end to end.