Deployment
It is one click only if the decisions were made beforehand.
Adding the script is genuinely a copy and paste. Everything that determines whether the assistant helps or embarrasses you happens before that.
- Private launchOnboarding selected teams now
- Answers from your pages onlyIt refuses when your content does not cover it
What it does
A single script tag loads the assistant on your site. It is platform agnostic because it is just a script, so it works anywhere you can add one.
Why it matters
The one click framing is accurate about effort and misleading about sequence. The click is the last step. Source selection, escalation rules and placement are the work, and skipping them produces an assistant that answers from your 2023 blog archive.
There is also a scope question the phrase hides. One embed on every page is the fast path, and it is how an assistant ends up on checkout and login pages where it competes with the one action the page exists for.
The platform question is usually asked and rarely matters. Because it is a script, Webflow, WordPress, Shopify, a static site and a framework app all behave identically. What differs is where you paste it and whether your platform lets you exclude pages, which is a template question rather than a compatibility one.
The part that genuinely differs by platform is reindexing. A site that publishes through a CMS can usually emit an event on publish. A hand edited static site cannot, so it falls back to a schedule, and the gap between publishing a price change and the assistant knowing about it is however long that schedule is.
How it works
Add the script
One tag, before the closing body tag. No build step, no framework requirement, no package to install.
It loads deferred
The widget does not block rendering and does not run until the page is interactive, so it does not cost you a Core Web Vitals score.
It reads its configuration
Which agent, which sources, which escalation rules. Configuration lives with the agent, not in the snippet, so changing behaviour does not mean editing your site.
Placement rules apply
Pages where the launcher should not appear are excluded by configuration rather than by adding the script selectively, so the rule lives in one place.
The decisions that have to happen before the click
Four things, and none of them are technical. Skipping them is what turns a five minute install into an assistant you quietly remove three weeks later.
Which pages the assistant may answer from. This is the whole quality lever, and the default instinct of indexing the domain is the most common way to get it wrong.
What it must never answer. Pricing improvisation, anything contractual, anything requiring an account lookup. These belong in configuration, not in hope.
Where the launcher appears. On a checkout page it competes with the one action the page exists for. On a product page it resolves the objection that would have ended the session. Same widget, opposite effect.
Who reads the logs. An assistant nobody reviews degrades silently, because the content it depends on drifts and nothing surfaces that until a customer quotes a wrong answer back at you.
What is built and what is planned
Removing the Creobot badge is planned for the Pro plan and above. Deeper platform integrations beyond a script embed are not built, and an embed is not going to be described as an integration.
Where the data goes
The embed loads the widget and sends visitor questions for answering. It does not read your page's DOM, does not track visitors across sites, and sets no advertising identifiers. Security and data boundaries.
Where this comes up
Questions
Signal
Is this the capability you need?
Access is by waitlist, demo request or public-content pilot. Tell us what your site has to answer and we will say honestly whether this covers it.