InformlyInformly Docs
Chat Widgets

Chat widgets overview

A chat widget is a single instance of the Informly AI experience that you embed on a website or surface inside your own app.

A widget is the surface your customers actually touch. It's a single instance of the Informly chat experience — branded, configured, and scoped to one project — that you drop onto a webpage with a script tag or render inside your own app. Each widget has its own appearance, persona, voice, security rules, and assigned skills, but it answers from the documents attached to its parent project.

You can run many widgets in a single project. Most teams start with one widget per surface: one for the marketing site, one for the in-app help center, one for a dedicated support page.

How widgets relate to projects

A widget always lives inside a project. The project decides which documents the widget can answer from; the widget decides how those answers look and behave. That separation lets you reuse the same content across several customer surfaces without duplicating documents.

The widgets page

Open Widgets from the sidebar to see every widget in your organization. Each row shows:

ColumnWhat it tells you
Statusactive, inactive, or draft — controls whether the widget responds to traffic
ConversationsTotal conversations this widget has handled
DocumentsHow many documents are available to the widget through its project
Public keyThe UUID used in the embed snippet

The public key is safe to expose in client-side code; it's the identifier the embed script uses to load this specific widget.

Widget configuration tabs

Open any widget and you'll see a row of tabs that map roughly to one feature each:

  • Config — name, layout, appearance, behavior
  • Documents — view documents inherited from the project
  • Persona — assistant name, role, tone, audience
  • Voice — assign voice agents for browser calls
  • Skills — enable skills from the marketplace for this widget
  • Training — fine-tune answers and add manual Q&A
  • Handoff — routing rules for human escalation
  • Notifications — per-widget Slack, Discord, or email alerts
  • Interactions — conversation log scoped to this widget
  • Analytics — usage, ratings, and quality metrics
  • Actions — webhooks and CRM sync triggered by conversation events
  • Campaigns — proactive outbound messages
  • Security — origins, PII masking, rate limits, secrets

Most of these have their own page in this section.

Lifecycle of a widget

A widget starts as a draft while you configure it, moves to active when you embed it, and can be flipped to inactive to take it offline without deleting it. Inactive widgets don't load on the page even if the script tag is still there, which is handy for emergency shutoffs.

What's next

On this page