Demo Agent Setup

Setting up the demo automation agent takes about 20 minutes once you have your site configured. The agent needs three things: content to know your product, exploration data to navigate it, and capabilities to structure what it shows.

Prerequisites

Before configuring the demo agent, make sure you've completed these steps:

  1. Site created: You need a site in the dashboard pointed at your product's URL. See Sites if you haven't done this yet.
  2. Content ingested: The agent's product knowledge comes from your documentation. Add at least your docs site and one other content source (knowledge base, videos, etc.) via ingestion.
  3. Exploration completed: The agent needs a map of your product's screens and interactive elements. Run exploration from the Explorer tab.
  4. Capabilities generated: Capabilities tell the agent what your product can do. Generate them from the Capabilities tab. See Capabilities.

If you haven't completed these steps, follow the Quickstart first. The demo agent won't have enough context to run a useful session without all four in place.

Configuring the demo experience

Once prerequisites are met, configure how the demo agent behaves from your site's settings in the dashboard.

Selecting capabilities to highlight

Not every capability needs to be in a demo. A product with 40 capabilities would make for a scattered, unfocused session. Instead, select the 5-10 capabilities that matter most to your buyers.

In the Demo Configuration section:

  • Featured capabilities: Choose the capabilities the agent leads with. These are what the agent shows when a prospect hasn't specified what they want to see. Pick the ones that deliver the fastest aha moment.
  • Available capabilities: These are accessible if the prospect asks about them, but the agent won't proactively bring them up. Good for secondary features that round out the story.
  • Hidden capabilities: Features the agent won't show or discuss during demos. Use this for admin-only features, unfinished areas, or anything you don't want prospects seeing.

Setting the opening message

The agent's opening message sets the tone for the entire session. Configure it in the Demo Configuration section.

A good opening message does three things:

  1. Greets the prospect by role if known (e.g., "Welcome! I hear you're leading the customer success team at Acme.")
  2. States what the session is about (e.g., "I'm going to walk you through how our platform handles engagement surveys.")
  3. Asks a discovery question to personalize the rest of the demo (e.g., "Before we dive in, what's the biggest challenge your team is facing with user onboarding right now?")

You can set a default opening message or leave it dynamic. When set to dynamic, the agent crafts an opening based on whatever context it has about the prospect (name, company, role) from the session metadata.

Demo environment

The agent runs against a live instance of your product. Configure which environment it uses:

  • Product URL: The URL the agent navigates. This should be a demo environment or sandbox account, not production.
  • Authentication: Credentials for the demo account. The agent uses these to log in at the start of each session.
  • Demo data: Pre-populated data makes demos more realistic. A "Reporting" demo is more convincing when there are actual reports to show, not empty states.

Invest time in your demo data. An empty state kills momentum. The best demo environments have realistic sample data that makes features look like they're already in use.

Starting a demo session

Once configuration is done, you can start a session.

From the dashboard

  1. Go to Demo Sessions in your site
  2. Click Start Demo
  3. Optionally add prospect context: name, company, role, specific interests
  4. The agent launches a browser, loads your product, and is ready to go
  5. Share the session link with the prospect

Session link

Each demo session generates a unique link. The prospect clicks it and lands on a branded page where they see the agent's live browser and hear the voice conversation. No downloads or installs required on the prospect's side.

Adding prospect context

The more context you give the agent, the better the demo. When creating a session, you can provide:

  • Prospect name and company: The agent uses this in conversation
  • Role or title: Helps the agent emphasize relevant features (a VP of Sales sees different things than an IT admin)
  • Specific interests: "They asked about SSO and custom reporting" lets the agent prioritize those areas
  • Industry: Helps the agent draw relevant examples

This context isn't required. The agent runs fine without it, starting with a broader demo and narrowing based on the prospect's live questions. But pre-loaded context makes the first two minutes feel tailored rather than generic.

Verifying your setup

Before sharing demo links with real prospects, run a test session yourself:

  1. Start a demo session from the dashboard
  2. Join as the prospect using the session link
  3. Check that the agent can log into your product
  4. Ask it to show a few of your featured capabilities
  5. Try asking about something outside the featured list to see how it handles it
  6. Test interrupting the agent mid-explanation to make sure it adapts

Things to watch for:

  • Navigation failures: The agent can't find a screen or clicks the wrong element. This usually means exploration data is stale. Re-run exploration.
  • Inaccurate explanations: The agent says something wrong about your product. Check your ingested content for gaps or outdated information.
  • Missing capabilities: The agent can't address a topic you expected it to know. Verify that relevant documentation was ingested and that exploration reached those screens.

What's next

FAQ

Can I run multiple demo sessions at the same time? Yes. Each session is independent with its own browser instance.

Do I need a separate demo account for each session? A single demo account works for concurrent sessions as long as the demo data doesn't conflict. If sessions modify data (e.g., creating records), consider separate accounts to keep each session clean.

What happens if my product is down during a demo? The agent detects when pages fail to load and communicates this to the prospect. It will attempt to retry navigation, but if the product is unreachable, the session can't proceed.

Can prospects interact with the product directly? In the current setup, the agent controls the browser. The prospect watches and talks. Direct prospect interaction is on the roadmap.