How to add an AI customer support chatbot to your website

To add an AI customer support chatbot to your website, prepare the information it should answer from, copy your provider's widget snippet and add it through your website's custom-code setting or shared page template. Check that the widget loads and that customers can reach your team when it cannot help before you launch it widely.

Start with the questions your business can answer reliably: opening hours, delivery areas, product information and current policies. Remove conflicting versions and assign someone to keep the sources current. Installing a chat bubble does not make its answers accurate, and a general policy answer does not give a chatbot permission to change an order or approve a refund.

In Chat Support, the workspace Settings screen provides the website widget snippet when an active widget key is available. Copy the whole snippet from your own workspace. It includes the widget script address, a data-key attribute and defer. Keep private API credentials out of your website HTML; use the supplied widget snippet rather than substituting a server credential. If no active key exists, Settings offers key rotation to create a snippet.

Use your website's existing custom-code facility or ask its maintainer to place the snippet in the shared template for the pages that need support. Avoid adding it both in a template and in a tag manager, which can load it twice. Website builders differ in which plans and settings permit scripts, so confirm that your current plan accepts custom JavaScript before changing anything. This guide does not establish a native integration with a particular builder.

The defer attribute lets an external classic script run after the HTML document has been parsed, as MDN's script reference explains. Preserve the attributes in the snippet you copied. If your site uses a Content Security Policy, ask its maintainer to check the specific blocked script, frame or network request and permit only the required origins. Do not disable the policy to make the widget appear.

Test on a staging page first, then check the intended public pages after your normal website release. Use a fresh browser session and a narrow mobile viewport. Confirm that the launcher opens, the message field works and the widget does not cover a purchase button or cookie control. Check the browser console and network panel for failed script or chat requests. A visible bubble alone does not prove that messages reach the service.

Ask a documented question, a question absent from your sources and an explicit request for a person. Check the reply and the queue your team will monitor. Use synthetic questions without customer details, and avoid actions that send real notifications or change accounts during a test. Our testing guide covers answer checks in more detail; our human-handoff guide explains what the receiving teammate needs.

If the widget does not appear, check whether the snippet is present on that page, whether its script request succeeds and whether your workspace has an active key. A blocked request can come from a site policy or a browser extension; compare a clean session before changing configuration. If the widget loads but gives a poor answer, review the source and handoff setup separately from the installation.

Compare Chat Support plans before choosing your setup, then create a workspace and copy its snippet from Settings. If your website has a restrictive script policy or a specific integration requirement, contact us with the public page and a description of the problem. Do not include passwords, private API keys or customer conversations.