The builder and the setup assistantBeta
Where everything sits in the widget builder, and what the setup assistant does for you
This feature is in beta. It is usable, but details can still change.
The builder is where you configure one widget. The setup assistant on the right can change every setting for you, so you rarely need to touch a form yourself.
Find your way around
- Top bar: on the left the draft or published badge and the save state; on the right Publish, Share and the switch that shows or hides the test widget.
- Sections on the left, in this order: Identity, Brain, Behavior, Knowledge, Security, Versions, Install, Analytics, History.
- The test widget: a round chat bubble in the bottom-left of the builder, just right of the section list. It always sits there, whatever corner you chose for your website.
- The setup assistant: docked in the right-hand panel.
Every change saves itself as a draft. There is no save button.
What each section holds
| Section | What you set there | Details |
|---|---|---|
| Identity | name, colour, launcher icon or logo, position, welcome message, welcome note, starter prompts | Look and answers |
| Brain | the model, the language, the system prompt | Look and answers |
| Behavior | voice input, transcript storage, what visitors see about it | Transcripts and privacy |
| Knowledge | uploaded documents, the website source, knowledge retrieval on or off | Knowledge sources |
| Security | allowed domains, rate limits, steps per answer, monthly budget cap | Install, Limits |
| Versions | publishing and restoring earlier versions | Publish and versions |
| Install | the embed snippets and pages where the widget could not load | Install on your website |
| Analytics | conversations, messages, cost, top questions | Limits and billing |
| History | stored conversations, when transcript storage is on | Transcripts and privacy |
Work with the setup assistant
The assistant acts on this one widget. Ask it in plain words and it makes the change itself, then tells you what it changed:
- Set up from your website. It reads the site, groups the pages, proposes texts and a colour, and indexes the sections you pick.
- Change any setting. "Make the colour darker", "add example.com to the allowed domains", "use a fixed model".
- Hand you the embed code. It fetches the exact snippet for this widget and puts it in the chat, ready to paste.
- Check what the bot knows. It can test whether a fact is actually retrievable from the knowledge base before you publish.
- Answer product questions. Pricing, retention or embedding in a particular CMS come from this documentation, not from its memory.
It asks before it publishes or restores a version, and it never guesses your website from your organisation's name.
One switch stays with you: Allow null origin under Security. It lifts the domain restriction entirely, so the assistant explains it but leaves the decision to a person. See Local testing.
Test before you publish
The test widget runs your draft, on our own site. Use it for every change you make: new starter prompts, a stricter system prompt, freshly indexed pages. Because it is not on your website, the domain allowlist does not apply to it. An error inside the test widget therefore never means a domain is missing; see Troubleshooting.