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

# Agent settings

> Customize your agent's appearance, welcome screen, calls to action, conversation options, and scheduling.

Open the **Settings** tab in the Navattic Agent editor to customize your agent's appearance and visitor experience.

## Avatar

Choose how your agent appears visually:

* **Orb** - Displays an animated orb with a custom color. Use the color picker to set the orb color.
* **Logo** - Displays your company or product logo. Enter the logo URL in the input field.
* **Live** - Displays a photo-realistic avatar. Click **Create live avatar** to upload a photo and configure it in a two-step modal:
  1. **Framing** - Crop your photo to a square. The source image must be at least 1152px on its shortest edge and no larger than 25MB. Any aspect ratio is accepted.
  2. **Details** - Enter a name for the avatar and choose whether to remove the background.

After you submit, avatar creation runs in the background and may take up to 2 minutes to complete. You can close the modal once submitted; Navattic will notify you when the avatar is ready.

When you create a new Navattic Agent, the avatar defaults to the logo configured for your selected environment.

When a live avatar is selected, a **Display mode** control appears to set how the avatar is positioned during a session:

* **Dynamic** (default) - The avatar expands to fill the demo panel when the agent is talking, then contracts into the chat sidebar tile while a flow is presenting. This keeps the visitor's attention focused on whichever mode (speaking or showing) is active.
* **Fixed** - The avatar stays pinned in the chat sidebar tile at all times, regardless of whether the agent is talking or navigating a flow.

## Welcome screen

Customize what visitors see before they start the demo:

* **Title** - The headline on the welcome screen (defaults to your demo name)
* **Description** - A short message introducing the demo experience
* **Button text** - The label on the start button (defaults to "Get Started")

## Call to action

Add a call-to-action that appears during or after the demo session:

* **Button text** - The button label (e.g., "Schedule a call with our team")
* **URL** - Where visitors go when they click the button
* **Highlight when stuck** - Surfaces the CTA automatically when the agent reaches an impasse in the conversation

When a visitor clicks a CTA button, the button label is recorded and surfaced as the **Navattic Agent CTAs** End User property: a comma-separated list of every CTA clicked during that session. You can map this property to a field in your CRM via [field mappings](/integrations/field-mappings) to use clicked CTAs in lead scoring and marketing automation workflows.

<Note>
  Navattic Agent CTAs are only tracked when the visitor is identified (for example, via a form gate
  or CRM cookie). The property is per session and is not cleared by later sessions with no CTA
  clicks.
</Note>

## Form gate

Require visitors to submit a form before starting the demo. Use this to capture lead information before granting access.

## Conversation

* **Allow interruptions** - When enabled, visitors can speak at any time, including while the agent is talking. Disable this if you want the agent to finish before accepting input.
* **Allow mic input** - When enabled (the default), visitors can speak to the agent using their microphone. When disabled, the microphone button is hidden from the player and visitors interact through text chat only. Disabling this also turns off **Start with voice enabled** automatically.
* **Start with voice enabled** - When enabled, the microphone is activated for visitors as soon as they join the demo. Only available when **Allow mic input** is on.
* **Pace** - Controls how quickly the agent progresses through the demo. Choose **Relaxed** to give visitors more time between moments, **Default** for automatic pacing, or **Brisk** for a faster experience. Contact your account team if this option isn't visible in your workspace.

## Scheduling

Add a booking button to the player so visitors can schedule a meeting without leaving the demo:

* **Show scheduling button** - Shows a calendar icon in the player toolbar
* **Provider** - Choose your scheduling tool: Calendly, Chili Piper, RevenueHero, HubSpot Meeting, or a default scheduler
* **URL** - The URL for your scheduling page
* **Button label** - The label shown when hovering the button (defaults to "Book a meeting")

When enabled, clicking the calendar button slides a scheduling panel in from the right side of the player.

## Personalizing links

The CTA and scheduler URL fields accept personalization variables, so a link can open already filled in with what Navattic knows about the visitor. This works in four places:

* **URL** in the **Call to action** section of the Settings tab
* **URL** in the **Scheduling** section of the Settings tab
* **Button URL** on a CTA outcome, in the [Conversation Builder](/agents/build/conversation)
* **Scheduler URL** on a Calendar outcome, in the [Conversation Builder](/agents/build/conversation)

Each of these fields has a small `{}` button next to the input. Click it to open a list of your workspace's visitor properties, then select one to insert it at your cursor position, so you can drop a variable into the middle of a URL you're already editing.

Variables use the format `{{user.propertyName}}`, for example `{{user.email}}` or `{{user.firstName}}`.

| Token                | Resolves to             |
| -------------------- | ----------------------- |
| `{{user.email}}`     | Visitor's email address |
| `{{user.firstName}}` | Visitor's first name    |
| `{{user.lastName}}`  | Visitor's last name     |
| `{{user.fullName}}`  | Visitor's full name     |

The most common use for this is prefilling a meeting scheduler so a visitor doesn't have to retype information the agent already collected. Navattic substitutes the variable and leaves the rest of the URL alone, so use whichever parameter names your scheduler expects.

**Calendly** prefills from `name`, `first_name`, `last_name`, `email`, `location`, `guests`, and `a1` through `a10` for custom questions:

```
https://calendly.com/your-team/demo?email={{user.email}}&name={{user.fullName}}
```

**Chili Piper** has two link styles, and the one you're using decides the parameter:

```
https://example.chilipiper.com/router/demo?email={{user.email}}&name={{user.fullName}}
```

A router or booking link prefills the Chili Piper form, where `email` is required and the other parameter names must match your form mapping.

```
https://example.chilipiper.com/ownership/contact-owner?id={{user.email}}
```

A one-click or ownership link identifies the prospect with `id` instead, which accepts either an email address or a CRM record ID. Passing an email that already exists in your CRM lets the visitor skip the form and go straight to picking a time.

<Note>
  The two Chili Piper styles are mutually exclusive. When you pass `id`, Chili Piper bypasses the
  form, so any other prefill parameters on that link are ignored.
</Note>

Check your provider's own documentation for the parameters it accepts. Navattic Agents support Calendly, Chili Piper, RevenueHero, and HubSpot Meetings.

Navattic fills in a variable with whatever it knows about the visitor at that moment: answers from the demo's form gate, identification parameters on the demo link, who a share link was sent to, or a visitor identified by the parent page embedding the demo. Values can arrive partway through a session. For example, a visitor who answers the form gate mid-conversation has their variables filled in from that point forward.

<Warning>
  The variable picker only lists visitor properties, since those are the only values available in
  the visitor's browser during a session. Company properties (such as company name or industry) come
  from server-side enrichment that never reaches the browser, so a company variable in one of these
  fields will not resolve.
</Warning>

Two behaviors are worth knowing when you're building these links:

* Values are URL-encoded automatically, so special characters survive the trip. An email like `dave+test@acme.com` reaches the destination intact instead of the `+` turning into a space.
* If every variable in a query parameter fails to resolve, Navattic drops that parameter from the URL entirely rather than sending it empty. This is intentional: schedulers often treat an empty parameter (like `?email=`) as an invalid answer, while a missing parameter is simply unanswered. A parameter you've left blank on purpose, with no variable in it, is never touched.