Everything you need to get your agent live
Setup, embedding, knowledge, and routing — in plain language.
Building against the API, the embed script, or the product-demo SDK? See the full developer / SDK reference — parameter tables, the session/lead API, webhooks, and a complete copy-paste example.
Setup
Create an agent from the Agents tab, then fill in its identity (name, tone, role) on the Build sub-tab. Add what it should know under Knowledge — at minimum, point it at your product's docs or FAQ. Test it live in the Evaluate sub-tab before publishing. Publishing copies your draft config to the live agent visitors actually talk to; nothing you edit afterward affects a live call until you publish again.
Embedding on your site
Go to Agents → your agent → Distribute, and copy the embed snippet. Paste it before the closing </body> tag of any page you control. It loads asynchronously (never blocks your page's own render) and renders as a small launcher that opens the live agent when clicked. One snippet per agent; a single site can run multiple agents on different pages if you want different personas for different audiences.
Audience links (also on the Distribute tab) are a second way to drive traffic to a specific agent — share a link directly (e.g. in an email or a paid ad) instead of embedding a widget, and that visitor's session is automatically attributed to that audience in your Sessions and User Flow views.
Knowledge base
Under the Knowledge tab, add any combination of: PDF/Word/plain-text documents, URLs to crawl, and free-text Q&A pairs. The agent is instructed to answer only from what's actually here — if something isn't in the knowledge base, it says so rather than guessing. Re-crawl a URL source any time its content changes; delete anything you no longer want the agent drawing from. Each agent has its own knowledge sources, filtered from the account-wide library.
Routing
Routing rules decide which agent a visitor without an explicit audience link or agent ID sees, based on a matched signal (e.g. UTM source) or an "always" catch-all rule, evaluated by priority. An Audience link always overrides routing — it's a more specific, explicit signal than a general rule. Test a rule before publishing it to confirm it matches the traffic you expect.