KeyAI - ChatOnline

The whole install is a copy and paste. You grab a snippet from the dashboard, drop it before the closing body tag, and the widget appears. Async loading means the script doesn't hold up your page render, which keeps Core Web Vitals out of the conversation. For a marketing site with a slow third-party stack, that detail matters more than it sounds.

WordPress users add a Custom HTML block and paste the same snippet. No plugin, no theme file edit, no FTP. That keeps the setup inside the editor your content team already uses, so a marketing hire can ship it without waiting on engineering. The widget then loads on every page that uses the template.

On Shopify, the script goes into a Custom Liquid section under the footer in the theme customizer. Store owners get a Shopify chatbot without touching Liquid logic. Because it sits at theme level, it follows the shopper from product pages to checkout, which is where most pre-purchase questions actually appear.

The docs include working code for both stacks. React uses a useEffect hook that appends the script and removes it on unmount. Next.js uses the Script component with afterInteractive strategy. That's the pattern most front-end teams expect, so wiring the bot into a single-page app doesn't turn into a research project.

Webflow projects take the script in the Footer Code field under project settings. Any static host works the same way: put the tag in your layout file and rebuild. If your site is hand-coded, this is the shortest path to a live chat widget without a build step.

Settings in the dashboard hold your account ID and the script code you'll reuse across sites. The account ID is the only thing tying a page to your bot, so a staging copy of the site will talk to the same assistant unless you swap it. Keep that in mind when you test changes.