Skip to content
Service status

Type to search

Widgets · 1 min read

Behavior

Give a widget its instructions, model, knowledge, web search, one tool, and data retention.

The Behavior page decides how a widget answers: the instructions it follows, the model behind it, what it knows, and how long visitor conversations are kept.

Write instructions describing how the widget should behave and answer — the same field, and the same role, as Instructions on an ordinary assistant, but configured separately for the widget.

Choose the model the widget uses, or leave it on the default your organization has set.

Let the widget search the web to answer questions, the same way an assistant can.

A widget can have exactly one extra tool attached — only tools that work without signing in are eligible, since a visitor is never asked to authenticate.

A tool only becomes selectable for a widget once every one of its capabilities is set to approve automatically. There’s no visitor to approve a request mid-conversation, so anything that would normally ask for approval simply can’t be offered to a widget.

Attach knowledge sources the widget can draw on, the same way you would for an ordinary assistant. See Knowledge.

Configure how long a widget keeps visitor conversations before deleting them automatically — the same underlying mechanism as an assistant’s data retention setting. See Data retention policy.