Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.runwita.com/llms.txt

Use this file to discover all available pages before exploring further.

Before Runwita can do anything intelligent for you, it needs at least one journey. A journey is just a customer, a project, an initiative, anything you’ll have multiple meetings about over weeks or months. The journey is what gives every meeting somewhere to land. You don’t need to plan your whole journey graph upfront. Most people end up with a handful of customer journeys, one or two internal ones (your team, your manager), and they grow the rest by need. Start with one.

​
Create a journey

1

Open Runwita and find the Journeys list

The left sidebar has Home, Inbox, Journeys, Contacts. Click Journeys. The first time, it’s empty.
TODO: screenshot of empty Journeys list
2

Click 'New journey'

Top right of the Journeys page. A small dialog opens.
TODO: screenshot of new journey dialog
3

Name the customer and the use case

Two fields. Customer is the external party. Use case is what you’re doing for or with them. Some examples:
  • Customer: Maplewood Inn, Use case: Digital ordering rollout
  • Customer: Internal, Use case: Q3 hiring plan
  • Customer: Acme Corp, Use case: Renewal conversation
Keep both short. They’re the labels you’ll see on every engagement attached to this journey, and they’re what the AI uses to match new meetings into the right thread later.
4

Save

The journey appears at the top of the list. That’s it, you’re done.

​
What the journey gives you

A journey is mostly a container at this point, but it unlocks four things:
  • 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 meetings, with their own status (open, blocked, decided, resolved).
  • Decisions and actions, every decision and follow-up across every meeting 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 at least two or three engagements. The first meeting populates it; the second starts to show patterns.

​
A naming tip

The customer and use case fields together become the journey’s identity for the AI matcher. When you process a meeting later, the AI looks at the meeting content and tries to pick the right journey from your list. If two journeys have similar names (Acme Corp, Renewal and Acme Corp, Q4 expansion), the matcher works much better when the use case spells out the actual subject. Vague use cases like Engagement or Working sessions make matching harder.

​
What’s next

Capture your first meeting

Now that you have a journey, run a meeting through the extraction pipeline.