One line of code. Or none, on any site we have a plugin for.

It is worth being clear about this, because plenty of chat tools make installation sound like an integration project. It is not one. The widget is a single JavaScript file. You load it, you tell it which agent to run, and it renders. That is the whole mechanism, and it is the same mechanism on every platform.

Nothing about this product requires a plugin. If you can paste a line of HTML into your site, you are done, whether that site is a Shopify theme, a Webflow project, a Next.js app or a page somebody hand-wrote in 2011.

The plugins exist for a narrower reason: on some platforms, pasting a script tag means editing a theme file, and the person who wants the chat widget is not the person with access to the theme file. The plugin removes that step.

On WordPress, adding a script tag properly means either a child theme, a functions.php edit, or a third-party snippet plugin, and all three are the kind of thing that quietly breaks during an update. The official WordPress plugin sidesteps all of it: install, paste the agent ID, done.

Framer and Bubble are the same story from a different angle. Both are visual builders where dropping in raw script tags is possible but awkward, so the widget ships as a native component in the Framer marketplace and the Bubble plugin library instead.

WHMCS is the specialist case. If you run a hosting or services business, your customers spend their time in the client area rather than on your marketing site, and that is exactly where a support agent should be. The addon is free and supports WHMCS 8.0 through 8.13.

Shopify, Webflow, Wix, React, Vue and plain HTML all take the script tag directly, and on those platforms pasting it is genuinely trivial. Shopify wants it in your theme file before the closing body tag. Webflow and Wix both have a custom-code panel built for exactly this. A React or Vue app takes it in the document head.

There is also an iFrame embed, which is a different shape of the same thing: instead of a floating bubble in the corner, the chat renders inline, inside the page. This is the right choice for a dedicated help page or a contact page where the conversation *is* the content rather than an overlay on top of it.

Installation is the easy part, and it is not where the value is. An installed widget with nothing behind it is a bubble that says it cannot help.

Before you paste the tag, train the agent on your content so it has something to say, and make the widget look like yours so it does not feel bolted on. If you are putting it inside a logged-in area, such as a WHMCS client area, also look at verified user identity, so the agent knows which customer it is speaking to rather than treating them as an anonymous visitor.