> For the complete documentation index, see [llms.txt](https://docs.spara.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spara.com/build/channels/product-demo/visuals-and-interactivity.md).

# Visuals and Interactivity

Manage the screenshots and videos a Product Demo shows, and make them interactive with clickable regions, guided walkthroughs, and links.

Visuals are the screenshots, images, and short videos a Product Demo shows on screen while the agent talks. Out of the box a visual is a picture the agent narrates over. This page covers how to manage your visual library and, when it helps the demo, how to let prospects click, follow a guided tour, or steer the demo from the visual itself.

For how features choose their visuals, see [Product Demo](https://docs.spara.com/build/channels/product-demo.md). For the first thing a prospect sees, see [Opening Visual](https://docs.spara.com/build/channels/product-demo/opening-visual.md).

## The visual library

All of your demo visuals live in one library at [**Settings > Product Demo > Visuals**](https://app.spara.co/settings/product-demo/visuals), shared across every Product Demo channel in your account. From there you can:

* **Upload** a PNG, JPG, GIF, SVG, or MP4 up to 25 MB. Videos must be 30 seconds or shorter.
* **Capture** screenshots of your own product with the [Spara Scanner](https://docs.spara.com/build/channels/product-demo/spara-scanner.md) Chrome extension.
* **Filter** the library to visuals that are **In use**, **Unused**, or used by one particular demo, which is the quickest way to review one channel's screens.
* **Select several** visuals at once to download or delete them.

Click a visual to open its edit drawer, where you set its name, description, interactivity, and links, and see which features use it.

**Name and description.** The description tells the agent when this visual is worth showing on its own, independently of any feature it is assigned to. Spara writes one for each image automatically; edit it if you want to steer the agent.

## Interactivity

By default a visual is inert: the agent shows it, and nothing on it reacts. Turning interactivity on is a choice you make per visual in the edit drawer, under **Interactivity**:

* **None**: The screenshot is shown and no highlight reacts. Links, below, are set separately.
* **Clickable**: Regions of the screenshot outline on hover and take a click. A prospect can click a region to ask about that part of the screen.
* **Walkthrough**: Clickable, plus a guided tour the prospect can start, with the agent highlighting one part of the screen at a time.

Interactivity never changes what the agent says about a visual. Leave it on **None** for title cards, diagrams, and anything that should not look clickable.

### Walkthroughs

A walkthrough is an ordered set of highlights on one visual, each with a name and a line the agent says while it is highlighted. Prospects can step through it at their own pace with **Next step**, or pause and ask a question part way through.

You can build one in two ways from the visual's edit drawer:

* **Create walkthrough** draws the highlights from scratch. Give each highlight a name and what the agent should say, in order. A walkthrough needs at least two steps.
* **Generate walkthrough** asks Spara to write one for you. It is available once the visual has regions and a page URL to work from, which Spara Scanner captures provide automatically.

Walkthroughs work on uploaded visuals as well as Scanner captures. Open the walkthrough with the pencil icon to edit the steps, and use **Edit walkthrough** to reorder or remove them.

### Links

A screenshot often contains things that look clickable, such as a navigation bar, a tab strip, or an agenda slide. Links make those boxes do something: when a prospect clicks one, it sends a request to the agent in the prospect's own words, and the agent answers it like any other question, usually by showing the screen behind it.

To add links, open the visual's edit drawer, click **Add links** under **Links**, and draw a box over each area. Give every box a request written the way a prospect would ask for it, for example "Show me how pipeline automation works" or "What does pricing look like?". Every link needs a request before you can save.

The **Active** switch under **Links** turns a visual's links on and off without deleting them, so you can prepare links in advance or pause them while you rework a feature. Links are independent of the **Interactivity** setting: a title card with interactivity set to **None** can still carry the links that act as the demo's menu.

{% hint style="info" %}
Links describe what to ask for, not which feature to open. That keeps them working when you rename, split, or reorder features, and lets one shared visual behave correctly in several demos.
{% endhint %}

## What prospects can do

Beyond talking, a prospect in a demo has a few controls of their own. There is nothing to configure for these.

* **Mute the agent's voice.** A speaker button beside the microphone silences the agent without ending the call or muting the prospect, for example in an open office or on a shared screen. The agent keeps listening and the transcript keeps updating.
* **Type instead of talk.** If their microphone is blocked, missing, or in use by another app, the demo tells them so and they can keep going by typing in the chat panel. The agent answers in voice and text as usual.
* **Book a meeting without leaving the demo.** **Talk to Sales** opens your booking calendar in place of the visual, and **Back to demo** returns to it where they left off.
* **Follow or skip a walkthrough.** Prospects step through a walkthrough with **Next step**, pause it, or ask a question at any point.

## FAQ

### Why are my visuals suddenly not clickable?

Interactivity is opt-in. Visuals start as **None**, and a visual only becomes clickable when someone sets it to **Clickable** or **Walkthrough** in its edit drawer. Check the setting on the visual, not on the feature.

### Can one visual have different links in different demos?

No. Links belong to the visual, and the visual library is shared across your Product Demo channels. Because a link is a request in words rather than a pointer to a feature, the same link works in every demo that shows the visual: each agent answers it from its own features.

### Do I need Spara Scanner to build a walkthrough?

No. Scanner captures let you **Generate walkthrough** automatically, but any uploaded image can have a walkthrough drawn by hand with **Create walkthrough**.

### Does a walkthrough change what the agent narrates?

Only while the prospect is inside it. The walkthrough's step text is what the agent says during the tour. Outside the tour, the agent narrates from the feature's description as usual.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.spara.com/build/channels/product-demo/visuals-and-interactivity.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
