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

# Screen Apps

> Let your AI persona put a booking page, a form, or any web page on the participant's screen at the right moment.

A screen app is a web page your AI persona can open on the participant's
screen during a session. Think of it as the AI saying *"let me pull that up
for you"*, and a booking calendar or a sign-up form appearing right next to
the conversation.

You choose the page. The AI decides when to show it, based on a short
description you write.

## What you can show

> **Book a meeting (Calendly)**
>
> The participant asks to talk to your team. The AI opens your Calendly
> page and they pick a time without leaving the call.

> **Book a meeting (Cal.com)**
>
> Same idea with Cal.com: your booking page appears and the participant
> books the slot themselves.

> **Collect details (Google Forms)**
>
> A lead form, a feedback survey, a registration form. The participant
> fills it in while the AI stays on the call to help.

> **Your own tools**
>
> A pricing calculator, a product configurator, a sign-up flow. Your
> developers can build pages that the AI can fill in and react to.

Some other places it works well:

* **Sales calls:** show the pricing page or a "request a quote" form once the prospect is interested.
* **Support:** open a returns form or a ticket form when the customer describes a problem.
* **Recruiting:** put an application form or an interview scheduler on screen at the end of a screening call.
* **Training:** show a quiz or a checklist the learner completes during the session.

## Adding a screen app

**1. Open your scenario**

Go to the scenario you want the AI to use it in.

**2. Go to Settings › Screen Apps**

Click the **Settings** tab, then **Screen Apps**, then **Add app**.

**3. Fill in the details**

* **Name**: a short label such as `book_demo` or `feedback_form`.
* **Page URL**: the link to your booking page or form. It must start with `https://`.
* **What it does and when to show it**: one or two sentences. This is the most important field. See below.
* **Default placement**: where on screen it appears.

**4. Save and try it**

Start a test call and ask for the thing your description mentions, for
example *"Can I book a time with your team?"*

## Writing a good description

The AI cannot see the page. It decides when to open it, and what to say,
only from your description. Say **what the page is** and **when to open it**.

| Good | Too vague |
| - | - |
| "Our Calendly page for booking a 30-minute demo with sales. Open it when the participant wants to talk to someone or book a demo. They book the time themselves." | "calendar" |
| "Google Form that collects company name, team size and budget. Open it at the end of the call if the participant is interested in a quote." | "use when needed" |

> [!WARNING]
>
> Do not put example names, emails or companies in the description. The AI may
> treat them as real details about the participant.

## Where it appears

| Placement | What the participant sees |
| - | - |
| **Stage** | The page takes the main area; faces sit beside it. Best for most forms and calendars. |
| **Side column** | A narrow column; faces stay large. Good for short forms. |
| **Floating card** | A small card in the corner. Good for a single question or a quick button. |
| **Fullscreen** | The page fills the call; faces float in a corner. Good for long forms. |

On phones, the page takes the full screen unless it is a floating card.

## What the AI knows about the page

This depends on the page.

* **Booking tools and forms from other companies** (Calendly, Cal.com, Google Forms, Typeform):
  the AI knows it opened the page, but it **cannot see** what the participant
  picks or types, and it is **not told** when they finish. If you want the AI
  to confirm, ask it in your meeting script to check: *"Once the calendar is
  open, ask whether they managed to book a slot."*
* **Pages your developers build** with the Waterr screen SDK: the AI can fill
  fields in for the participant, is told what step they are on, and responds
  as soon as they submit. See [Screen Apps for developers](https://docs.waterr.ai/api-reference/screen-apps.md).

## If the page stays blank

Some websites refuse to be shown inside another site. If the panel opens but
stays empty, use the **embed** link the tool offers instead of the normal one:

* **Google Forms:** add `?embedded=true` to the end of the form link, for example
  `https://docs.google.com/forms/d/e/<form-id>/viewform?embedded=true`.
* **Calendly and Cal.com:** use the link from the tool's **Embed** option
  (often listed under *Share* or *Embed on your website*).

If none of these work, that tool does not allow embedding, and it cannot be
used as a screen app.

## Good to know

* Screen apps work in Waterr meetings and in meetings embedded on your
  website with the inline embed. They are not available in the sidebar
  assistant widget, when your AI joins Google Meet, Zoom or Teams, or on
  phone calls.
* You can add up to 10 screen apps to a scenario.
* Each participant sees their own copy of the page. What one person types is
  not visible to others.
* Close the page by asking the AI to remove it. Pages built with the SDK can
  also close themselves when the participant is done.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.