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.

Contacts is the people view of Runwita. Every attendee on every engagement becomes a contact automatically. You don’t manage the list, the engagements do.

​
Why a separate surface

Journeys are the spine of Runwita. But the same people show up across multiple journeys, and sometimes you want to think about them, not the journey. “When did I last talk to Priya?” “What’s Marcus working on right now?” “Show me everyone at Acme Corp.” The Contacts page answers those questions in one place.

​
The list view

Every person who’s appeared on at least one engagement, with:
  • Name, role, company. Editable inline if the AI’s extraction is wrong or stale.
  • Journey count. How many journeys this person shows up on.
  • Engagement count. How many engagements they’ve been in.
  • Last seen. The most recent engagement they appeared on.
Search by name, company, or role. Group by company to see the cluster of people you know at each org.

​
Multi-select and merge

Sometimes the same person enters Runwita twice with slightly different names: “Sam Patel” on one engagement, “Sam P.” on another, “S. Patel” on a third. The AI tries to consolidate but doesn’t always catch it. Select two or more contacts and a Merge action becomes available. Pick which contact to keep as the canonical record, the rest collapse into it. Engagement history, journey memberships, and actions all re-anchor to the kept contact. The merged-out records are gone, the relationships are preserved. This is destructive but reversible only via undo immediately after. After that, you’d need to manually split if you got it wrong, so check the merge target before confirming.

​
The detail view

Click a contact to see their full picture:
  • Hero with name, role, company. All inline-editable.
  • Stat row. Number of journeys, engagements, open actions, decisions made.
  • Journeys. Every journey this person has appeared on. Click to deep-link.
  • Engagements. Every engagement they were on, in chronological order. Click to deep-link.
  • Actions. Open and completed action items where this person is the owner.
The detail view is read-mostly. The fields you can edit are the identity fields (name, role, company). Engagement history isn’t editable from here, you’d edit the engagement itself.

​
When contacts go wrong

Two failure modes you’ll hit: Same person, multiple records. AI didn’t recognise the name variants as the same human. Use the merge flow above. The signal: two or more contacts with the same role at the same company. Wrong role or company. AI inferred the wrong title or affiliation from context. Click into the contact, edit the field inline, save. The fix sticks for all future engagements. The AI never overwrites a manually-edited field. Once you’ve set someone’s role, subsequent engagements won’t second-guess it.

​
What’s next

Journeys

How contacts get attached, via attendees on engagements.

Intelligence

Stakeholder analysis maps influence across the contacts on a journey.