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

# Studio: act on what HelpAlive observes about users

> Studio is where you act on user behavior — manage Agent pages, work the Topics inbox of unanswered questions, and ship in-app Guides from one place.

**Studio** is the action surface in your dashboard. It's where you turn what HelpAlive observes into changes that move adoption — by sharpening your Agent, shipping in-app Guides, and seeing exactly which pages of your product carry the most support load.

You'll find Studio in the dashboard sidebar. It has the following tabs:

| Tab               | What you do here                                                                              |
| ----------------- | --------------------------------------------------------------------------------------------- |
| **Pages**         | View the pages where the Agent is active and how each one is performing.                      |
| **Topics**        | Work the inbox of questions the Agent couldn't answer well — your "what to write next" queue. |
| **Guides**        | Author and manage in-app walkthroughs that complete tasks step-by-step alongside the user.    |
| **Features**      | *Coming soon* — automatic feature discovery and health scores.                                |
| **Configuration** | *Coming soon* — Studio-level settings.                                                        |

## What your team gets

<CardGroup cols={3}>
  <Card title="Visibility into where users need help" icon="globe" href="/studio/pages">
    Per-page chat volume, ratings, and engagement — so you know which pages are your highest-value support surfaces.
  </Card>

  <Card title="A backlog of what to fix" icon="inbox" href="/studio/topics">
    Every question the Agent couldn't answer well, grouped into topics, ranked by impact. Stop guessing which docs need work.
  </Card>

  <Card title="A way to ship help, not just write it" icon="map" href="/studio/guides">
    Step-by-step walkthroughs that highlight real elements as the user clicks through. Users finish the task, not just read about it.
  </Card>
</CardGroup>

## The loop Studio enables

Most adoption problems share a shape: a user wants to do something, your product can do it, but the user can't find the path. Studio gives your team a closed loop for fixing those:

1. **Observe.** [Pages](/studio/pages) shows where users open the Agent most. [Topics](/studio/topics) shows what they're asking that you can't answer well.
2. **Decide.** For each gap, pick the right intervention — write a doc, add a custom answer, or ship a Guide.
3. **Ship.** Train the Agent on the new content (Agent → Train), or author a Guide that walks users through the flow.
4. **Measure.** Watch the next 24–48 hours. Topic scores drop. Guide completion rates land. Adoption metrics in [Insight](/insight/overview) confirm the lift.

This is the workflow we built Studio around — and the reason "act on what we see" is on the same screen as "see what users do."

## How Studio fits with Agent and Insight

Three sections, three jobs:

* **[Agent](/agent/overview)** — set up and configure the AI assistant your end users talk to.
* **Studio** — improve the Agent over time and ship in-product Guides that turn answers into completed tasks.
* **[Insight](/insight/overview)** — observe overall adoption and product usage at the user, workspace, and report level.

You'll typically work the loop in that order: configure the Agent, watch what comes back through Studio, and validate the impact in Insight.

## Next steps

<CardGroup cols={2}>
  <Card title="Topics inbox" icon="inbox" href="/studio/topics">
    The queue of unanswered questions, ranked by impact.
  </Card>

  <Card title="Guides" icon="map" href="/studio/guides">
    Step-by-step walkthroughs — what they do, what's possible, what ships today.
  </Card>

  <Card title="Pages" icon="globe" href="/studio/pages">
    Per-page chat performance — find your highest-impact support surfaces.
  </Card>

  <Card title="Train the Agent" icon="book-open" href="/agent/train">
    Add the content that resolves the gaps Studio surfaces.
  </Card>
</CardGroup>