> ## Documentation Index
> Fetch the complete documentation index at: https://docs.inklyai.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Sessions

> Read what happened on any visit to your demo — the conversation, the path, and what the agent worked out.

**Sessions** is the list of individual visits. It is the most useful screen in the product, and the one people underuse.

A chart tells you that a screen loses people. A transcript tells you why.

## The list

The list shows **identified** visits, newest first — who it was, how long they stayed, and how far they got. Someone who left at the welcome screen without an email is still recorded and still counted in [Analytics](/measure/analytics), but has nothing you can act on, so they are not listed here.

Search across email, company, and country, and filter by source (your live demo versus previews) and by date range.

Duration is measured to the visitor's **last interaction**, not to the last thing the page did — so a demo left open in a background tab and closed 45 minutes later is not a 45-minute session.

## The transcript

The full conversation: every turn the visitor took and every answer the guide gave, in order, marked with which were spoken.

This is your most direct source of product feedback. The questions people ask a demo agent are the questions they were too polite, or too early, to ask a salesperson.

<Note>
  Read the first five transcripts after any change, end to end, without skimming. It consistently beats reasoning about the funnel from aggregate numbers.
</Note>

Read for four things:

<CardGroup cols={2}>
  <Card title="Questions the guide fumbled" icon="circle-question">
    Each one is a missing [knowledge doc](/build/knowledge), or a missing section in one.
  </Card>

  <Card title="Questions you did not expect" icon="lightbulb">
    Objections you are not handling on your website either.
  </Card>

  <Card title="Where they interrupted" icon="hand">
    The beat they cut off is the beat that was not landing.
  </Card>

  <Card title="Where they went off-path" icon="route">
    What they went looking for is what they actually came for.
  </Card>
</CardGroup>

## Session details

Alongside the transcript, you can see the visit's duration, screens viewed, questions asked, outcomes, source, campaign, device, and location. See [what a session shows](/measure/analytics#what-a-session-shows).

## Analysis

Sessions carry the fields the guide gathered — what it asked during the visit, and what was deduced from the transcript afterwards. Both are shown against the conversation they came from, so a value you disagree with can be checked against what was actually said.

Configure what gets collected under [What the agent collects](/build/what-the-agent-collects).

## Locked sessions

When credits run out, the demo still records the session, qualification, and buyer intent. An identified visitor's email, transcript, and analysis remain locked.

Click **Unlock with 10 credits** to reveal every saved session for that email. The charge applies once per billing period, so repeat visits cost nothing extra. You can also unlock several visitors at once.

On the Free plan, every identified session is locked. See [Plans and credits](/account/plans-and-credits).

## Next

<CardGroup cols={2}>
  <Card title="People" icon="users" href="/measure/people">
    Sessions grouped by the person who had them.
  </Card>

  <Card title="Knowledge" icon="file-lines" href="/build/knowledge">
    Where the answers to fumbled questions go.
  </Card>
</CardGroup>