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.

The Identity panel in Settings has two fields. They feed every extraction prompt the AI runs, so what you put here shapes how the AI thinks about your meetings.

​
Your name

This is the name the AI uses to recognise you in transcripts and notes. It serves a specific purpose: when the AI is extracting decisions and actions, it needs to know which voice in the room is the host. A meeting transcript with you asking “so we’re agreed on the June launch, right?” and someone else saying “yes, June it is”, the decision belongs to the meeting collectively, but you don’t want your question recorded as a decision. The AI uses your name to filter that out. If your name is blank, the AI defaults to “the meeting host”, which works but is less precise.

​
Your role context

This is the one-sentence answer to “what’s the AI doing this work for?”. It gets interpolated into the system prompt at the top of every extraction:
“You are a meeting analyst for [your role context]. Given a meeting transcript, extract structured engagement data…”
The more specific you are, the better the framing of every extraction. Compare:
GenericSpecific
a managera Customer Success Manager working with Fortune 500 SaaS accounts on retention and expansion
a designera Senior Product Designer at a B2B fintech, focused on payments UX and compliance flows
a founderthe founder of a 12-person devtools startup, in customer discovery for our first paid product
The specific version teaches the AI what to pay attention to, what jargon to expect, what categories of decision matter to your work. The generic version doesn’t help. It doesn’t have to be your literal job title, in fact, often shouldn’t be. “Senior Manager II” tells the AI nothing. “Engineering manager for the platform team responsible for auth, billing, and infra” tells the AI everything.

​
When to update these

Update them whenever your role substantively changes, you switch teams, take on a new portfolio, change companies. The fields aren’t stored on past engagements, they affect new extractions only. So an update changes the AI’s framing going forward without retroactively touching old saves.

​
Example

Your name: Bharat Rameshwar
Your role context: a Senior Customer Solution Advisor at SAP focused on enterprise BI/analytics customers and SAP Datasphere adoption
That’s enough. The AI knows who you are, what your domain is, and what kinds of decisions and actions matter to your work. Every extraction reads with that frame.