Ctrlk
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Launcher

The always-available entry point to the Agent: a floating prompt on your pages that users open whenever they need help.

Dashboard path: Agent > Customize > Launcher (/agent/launcher)

What is the Launcher?

The Launcher is the Agent's own trigger. It is a floating input bar ("Ask or search anything...") that sits at the bottom of your product and opens the Agent chat when a user types in it. Unlike the Ask Agent block in a Resource Center or a Launch Agent action in an experience, it does not depend on another experience being displayed: you decide on which pages, which devices and for which users it shows, and it is there.

Users can drag it along the bottom edge of the screen to move it out of the way of your own interface. It snaps back to the bottom when released.

Overview

  • One global switch: the Active toggle turns the Launcher on or off for the whole project.

  • Live preview: see the Launcher on a mock page, in light or dark mode, with the accent colour of your choice.

  • Where: devices (Desktop, Tablet, Mobile) and pages (all pages, a specific page, or filtered URLs), the same targeting model as any experience.

  • Who: everyone, or a segment.

  • Suggestions above the bar: up to four predefined prompts per scanned page, shown as chips above the Launcher when the user is on that page. Managed from the page's panel in Knowledge > Interface.

  • Independent from the Resource Center: you can run the Launcher alone, the Ask Agent block alone, or both.

Use Cases

  • 🧭 Help everywhere, no Resource Center needed. Turn the Launcher on for all pages and every user gets a way to ask the Agent.

  • 🎯 Only where it matters. Restrict it to the pages where users get stuck (a settings area, a builder) with filtered URLs.

  • 🧪 Roll out to a segment first. Show it to a beta segment or internal users before opening it to everyone.

  • 🤝 Coexist with your own chat. Keep the Launcher off, and reach the Agent only through Launch Agent actions from specific buttons or flows, so it does not stack with another support widget.

How to Access

  1. Open the Launcher page: in the dashboard, go to Agent > Customize > Launcher.

  2. Turn it on: click Set up your launcher to flip the Active toggle. The status line reads "Active, live on every page" once it is on. (It doesn't apply until you save.)

  3. Check the preview: the Launcher preview shows the input bar on a mock page. Use the colour dots and the Light / Dark switch to preview it in your context. The Visiting /any-page badge reminds you which page the preview simulates.

  4. Set Where and Who: open the two sections below the summary sentence ("On every page, for everyone."), adjust, then click Save (top-right).

Main Features

Preview

The preview reflects your Agent widget styling. The colour dots and the Light / Dark switch only change the launcher, not the following chat: the full widget's real appearance is set in the Agent Builder.

Active/Paused

State
What users see

Active

The Launcher shows on the pages and for the users defined below.

Paused

No floating Launcher. The Agent stays reachable through Ask Agent blocks and Launch Agent actions.

Where

The summary line under the section title recaps the current setting (for example "Desktop · Tablet · Mobile · On all pages").

  • Select devices to show this experience on: tick Desktop, Tablet, Mobile.

  • Page to show this experience:

    • On all pages: default.

    • On a specific page: one exact URL.

    • On filtered URLs: URL rules, same syntax as the Where step of an experience. See Where for the rule types.

Who

Everyone by default. Open the section to target a segment, with the same picker as the Who step of an experience. See Who.

Suggestions

Suggestions are quick prompts displayed as chips above the Launcher, one set per scanned page. When a user lands on a page that has suggestions, the chips appear above the bar ("How to change my billing info?"); clicking Ask on a chip sends that prompt to the Agent. They turn the Launcher from a blank input into a guided entry point for the questions users ask most on that screen.

Suggestions are not configured on the Launcher page. They live with the page's knowledge: open Agent > Train > Knowledge > Interface, click the scanned page, and use its Suggestions tab. See Page details for the full setup (up to four prompts, attributes and Skills inside a prompt, ordering).

Suggestions only show for pages you have scanned. A page without a scan, or without suggestions in its panel, shows the bare Launcher.

User Context is read in the live widget only: the dashboard test chat does not receive it. To check that the Agent adapts its answer once a property is added, open the Agent in your product as a user who has that property, in a new chat.

On the user's side

The Launcher appears as a rounded input bar at the bottom of the page, with the page's suggestion chips above it when there are any. Typing a question and pressing Enter opens the Agent chat with the question pre-loaded. Users can drag the bar left or right along the bottom edge.

The Launcher and the Ask Agent block open the same Agent, with the same knowledge, instructions and styling. Only the entry point differs.

Best Practices

  • Start with all pages, then narrow. A visible Launcher is the fastest way to get conversations into Analyze; restrict it once you know where questions come from.

  • One floating widget at a time. If you already show a Resource Center trigger or a third-party chat bubble in the same corner, either turn the Launcher off or move the other widget. Users drag the Launcher, but a clean default placement is better.

  • Use a segment for a quiet rollout. Internal users first, then a customer cohort, then everyone.

Related pages

PreviousAgent Builder
NextKnowledge

Last updated