# Screens the agent can open

> List the screens of your product on the Product tab so the agent can open them by name, and accept the screens it found during calls as suggestions.

Source: https://talkdemo.com/help/product-and-flows/screen-catalogue · Updated 2026-11-20

## Key takeaways

- The Screens list on the Product tab names the pages of your demo tenant that the agent can open when a prospect asks, such as Reports.
- Each screen has a name, a path such as /reports, an optional description and the product roles that see it.
- A path with a part that changes, such as /vendors/:id, is reached through a flow or a click on screen, not opened directly.
- Screens the agent visited in calls but that aren't listed show up as suggestions you can accept or dismiss.

When a prospect says "show me reports", the agent needs to know where Reports is. The **Screens** list on the **Product** tab tells it. The agent opens a listed screen by its name, and the prospect sees the page load in the shared browser.

**Who can do this:** Admin, Member. Viewers can see the list. · **Plans:** live product mode (Growth and up).

## Add a screen

1. Open **Agents**, choose the agent and open **Product**. Save your demo tenant first: the list appears below it.
2. Under **Screens**, click **Add screen**.
3. Fill in:
   - **Name.** What a prospect would call it, such as "Reports".
   - **Path.** The address after the domain, such as `/reports`. Use `:id` for a part that changes, such as `/vendors/:id`.
   - **What it shows.** Optional. One or two sentences, such as "Weekly SLA reports by vendor". The agent uses it to pick the right screen.
   - **Seen by.** Optional. The product roles or plans that see the screen, separated by commas, such as "Admin, Manager".
4. Click **Add screen**. The agent can open it from the next call.

Click **Edit** on a screen to change it, or **Remove** to take it off the list. Two screens can't share a path.

## How the agent uses screens

- The agent gets the list with every call and opens a screen when a prospect asks for it by name, in any language the agent speaks.
- A screen whose path has `:id` is marked **Opened from a list**. The agent reaches it through a flow or by clicking the item on screen, because it can't guess which record to open.
- When a prospect names a menu item that isn't listed, such as "knowledge", the agent clicks that item in the menu on screen if there is exactly one with that name.
- For anything else, the agent clicks through the page step by step within your guardrails. See [Record and edit flows](/help/product-and-flows/record-and-edit-flows#what-if-a-prospect-asks-for-something-no-flow-covers).

The guardrails always apply: the agent opens only pages on your allowed hosts and paths, whatever the list says.

## Suggestions from calls

During calls the agent notes the screens it visits. Paths that aren't on the list appear under **Suggested from calls**, with how many calls visited them. Parts of a path that look like a record, such as a number or a long id, are shown as `:id`, so a suggestion names the screen, not one record.

- Click **Accept** to check the name and the path, add a description and roles, and add the screen to the list.
- Click **Dismiss** if prospects shouldn't be taken there. A dismissed path isn't suggested again.

Suggestions never reach the agent until you accept them.

## Frequently asked questions

### Do I need a screen for every page?
No. List the pages prospects ask for by name. Flows cover the paths you want shown step by step, and the agent can click through the rest.

### Does a screen let the agent open pages outside my allowlist?
No. The browser only loads hosts and paths on the allowlist on **Product**, and every click passes the guardrails on **Guardrails**.

### What data do suggestions store?
The path pattern, the page title, how many calls visited it and when. Never the address's query string, the page content or anything a prospect said.
