Skip to main content
Use a staging site to prepare an agent experience and its fallback contact path. A production Threetone embed is not verified for this release, so this guide does not provide a plugin name or script to install.

​
Prepare the integration

Choose a page or theme placement owned by your team. Decide whether the experience should appear on every page or only alongside relevant support content. Document who can change the placement and how to disable it quickly. Once an official embed is released, use a supported WordPress integration mechanism suitable for your hosting and security policy. Avoid editing a parent theme in a way that updates can overwrite. Keep installation in one place and review the exact script source before publishing.

​
Verify the experience

Test the placement with your active theme, cache settings, consent manager, and mobile navigation. Confirm keyboard access, readable status messages, and focus restoration. A blocked script should leave the page usable and retain a working support link. Never store workspace keys or provider secrets in page blocks, public shortcode output, or browser-visible settings. Privileged API operations belong on an authorized server boundary.

​
Frequently asked questions

No installable first-party plugin is verified in this documentation release. Do not install an unrelated package solely because its name appears similar.
Review what is cached. Public placement HTML must not include credentials or private workspace responses. Session authentication requires its own supported path.