Skip to main content

​
Configure Widget

This panel controls the user-facing widget experience. You can customize:
  • widget name
  • widget behavior (overlay or push)
  • widget icon
  • input placeholder
  • empty state title and description
  • starter suggestions
  • security disclosure visibility

​
Overlay vs push

The widget opens above the page. Use this when you want minimal layout disruption.

The widget makes room in the page. Use this when preserving visible app context matters more than strict overlay behavior.

​
White-labeling guidance

Replace the default widget name and icon with the customer’s product context before end users see it.

​
Suggestions

Starter suggestions are the short prompts shown in an empty chat. They should be:
  • short
  • clickable
  • action-oriented
  • written in end-user language
Examples:
  • “Show recent invoices”
  • “Create a refund”
  • “Summarize open approvals”

​
Custom Instructions

Custom Instructions define the assistant’s:
  • personality
  • knowledge boundaries
  • tone
  • response style
Use this area to shape how the agent speaks inside the customer’s product, not to restate technical implementation details. Good instruction traits:
  • concise
  • product-specific
  • non-technical unless the audience is technical
  • explicit about when to give step-by-step help
  • explicit about when to avoid guessing

​
Screen Autopilot

Screen autopilot lets the agent:
  • read the page context
  • find elements
  • execute UI actions
  • fall back to JavaScript execution when necessary
It does not require your manually defined frontend tools. Use it when:
  • your UI already contains the action but you have not exposed a dedicated tool
  • the action is easier to perform through the live page
  • users need page-level guidance, not just API execution

​
When to prefer a manual frontend tool instead

Prefer a manual frontend tool when:
  • the action already exists as a stable client-side handler
  • you need a strongly controlled, deterministic browser action
  • you want framework-aware state changes instead of UI inference