An AI support agent on your website

The widget sits on the page where the question forms

Every other channel meets a customer somewhere else: in WhatsApp, in their texts, on a call. The website widget is the one that lives on your own property, in the bottom-right corner of the page a visitor is already reading. That location matters more than it looks. By the time someone has a question, they are usually deep in something specific: a plan on your pricing page, a spec on a product page, a policy buried in your docs. The widget puts the answer within reach of the exact thing that raised the question, so the visitor never has to leave the page, open a contact form, and describe where they were and what they were looking at.

Answered in the context of the page they are reading

Because the widget loads on every page from the same snippet, a question meets the agent wherever it comes up rather than on a separate support page you hope the visitor finds. You can shape that first moment per page. The greeting and the suggested questions can point at what people usually ask on the page they landed on, and proactive triggers can surface the widget on the pages where a nudge is worth it, within timezone-aware business hours you set. Restraint matters as much as reach here. On a page where the visitor is mid-checkout or halfway through a form, a proactive nudge that covers the field they are filling is the fastest way to lose the sale it was meant to save, so those are the pages to leave quiet and let the visitor open the widget when they are ready. The answer itself is grounded in your own knowledge through hybrid retrieval. When your content does not cover something, the agent says it does not know rather than guessing at an answer the visitor might act on, which is the behavior you want on a page where a wrong reply costs you a sale.

The first unanswered question on a pricing page is the expensive one

A question on a blog post can wait. A question on the pricing page usually cannot, because the person asking it is close to a decision and the question is the objection standing between them and it. If there is nowhere to ask, the objection does not resolve itself; it leaves with them, and you never learn what it was. An agent that sits on the page turns that silent exit into a conversation you can answer, and when the honest answer is that a person should take it from here, into a lead you can keep rather than lose.

One script tag, and how it loads

Going live is a single script tag placed near the end of your page's body, which is where the widget expects to sit. It loads asynchronously, so it does not block your page from rendering. Your own content paints first and the bubble arrives a moment later without holding anything up, which keeps the widget off the critical path that decides how fast the page feels. On a first paint the bubble arrives closed, so a new visitor sees your page rather than a panel demanding attention. If they left a conversation open on an earlier visit, it comes back with them: a question asked on the pricing page one day is still there when they return to the checkout to finish the next. The widget renders inside a Shadow DOM, an isolated boundary that keeps its markup and styles separate from yours, so it will not inherit your CSS or bleed its own styling into your layout. And because the tag is attached to the site rather than to one template, it covers the pages you add later without another change: publish a new page and the agent is already on it.

Put it on whatever built your site

The snippet is plain HTML, so it goes wherever you can paste a script tag. The integrations directory lists the platform you are on, with per-builder steps for the exact field names and placement each one uses. If your site is built in Webflow, the snippet goes in the custom code section set to load before the closing body tag. On Framer, it is a custom-code entry set to load site-wide. On Ghost it is the Site Footer field in Code Injection, on Bubble the body field under SEO / metatags, and on BigCommerce a footer script in Script Manager. The same paste-and-publish approach applies to WordPress, Squarespace, and a hand-coded site. There is no rebuild, no plugin to keep updated, and nothing to reconfigure when you redesign, because the tag does not care what the rest of the page is made of.

What happens after the answer

Grounded answers resolve most of what visitors ask, but the widget is also the front of a longer workflow. When a conversation needs a person, it moves to human handoff, and the teammate who picks it up can see which page the visitor was on when they asked. When the moment is a buying signal, the agent can capture the lead in the conversation, validating details inline and on the schedule you decide, rather than routing everyone to a form. Each chat can end with a CSAT rating and per-answer feedback, and that feeds the analytics that show your resolution rate, how much the agent deflected, and which questions it still cannot answer well. The visitor gets an answer in the moment. You get a record of what was asked, how often it landed, and where your knowledge has a gap worth filling.