Skip to main content
No-code site builders can provide a place for an agent experience without changing the site’s application framework. The production Threetone embed and its live session path are not verified for this release, so the guides below describe preparation rather than a working copy-and-paste widget.

​
Prepare the placement

Choose where the experience belongs: a help page, product page, or persistent launcher. Keep it clear of cookie controls, forms, and navigation. Define the questions it should answer, where its knowledge comes from, and when it should direct someone to support.

Webflow

Plan an embed placement and staging checks in a Webflow site.

WordPress

Prepare a controlled page or theme placement without exposing credentials.

​
Launch checklist

Before enabling a released embed, verify its authoritative script URL, session authentication, permitted origins, content security policy, keyboard behavior, and mobile layout. Test microphone permission refusal and disconnected sessions where voice is offered. Provide a visible alternative contact path. Keep workspace keys and provider secrets out of HTML, CMS fields, tag managers, and third-party snippets. An agent identifier is not a substitute for a supported access policy.

​
Frequently asked questions

A verified production snippet is not available in this release. These guides will add it after the browser session path is released and tested.
Use it only if it leads to a working destination and accurately describes availability. Do not present a decorative launcher as a live agent.