An AI chat website set-up succeeds or fails at installation. You create a chat widget on the levelpartner.ai platform, connect an AI agent to it, place one snippet of code on your site, and every conversation then lands in Conversations against a contact record. Get the placement wrong and the widget slows the page, clashes with the cookie banner, loads twice or vanishes after the next site update. This article answers the installation question: how to put AI chat on any website, built on the platform or elsewhere, check that it works, and keep it working.
What you are installing on an AI chat website
There are two pieces. The chat widget is the bubble and window your visitors see, and it is created under Sites. The AI agent is what answers inside it, and it lives under AI Agents. You connect the two on the agent's Deploy tab.
The code you paste onto a site is a small loader script, sometimes called the live chat embed. It loads the widget and ties it to your account. The greeting, colours, contact form, office hours and who answers are all set in the widget and the agent, not in the code. So you install the snippet once, and later changes appear on the site without anyone touching it again. That matters if an outside developer or contractor manages your website: they add the code once, and your team runs chat from the platform without raising a ticket for every greeting change.
Because the widget writes into the same contact records as your forms, calls and emails, a visitor who chats today and fills in a form next week is one contact with one history. That is the main reason to use the platform's widget rather than a separate chat tool added to your site.
Before you start
- Access to Sites and AI Agents, and edit access to your website's code settings, or a developer who has it.
- An AI agent already created with a basic knowledge base. AI agents covers building one.
- Your brand colour, logo and the name the chat assistant should use.
- A privacy notice that mentions chat and AI, linked from your site.
- If your site uses a consent tool or a tag manager, the name of each and who manages them.
- Any older chat tool already on the site, noted so it can be removed. Two widgets on one page conflict.
How to set it up
Create the widget and add it to a site built on the platform:
- Go to Sites > Chat Widget.
- Click New and select Live Chat.
- Customise the widget's appearance to match your brand.
- Click Save.
- Click Get Code, then Copy.
- Go to Sites > Websites or Sites > Funnels.
- Open your website or funnel's settings.
- Under the Chat Widget section, select your widget.
- Click Save.
Instead of steps 6 to 9, you can add the copied code to a platform site directly: open the site or funnel for editing, click the tracking code icon (</>), paste the code and click Save. For a site built on another system, paste the copied code into that system's site-wide header or footer code area, once only. Then connect the agent:
- Go to AI Agents > Conversation AI and open the bot.
- Select the Deploy tab and turn on Chat Widget.
- Open the Chat Widget channel's edit icon and turn on Assign channel.
- Select the widget and add tag conditions if needed.
- Click Update, save the bot and test the widget on your site.
Chatbot site internet installs on any site builder
A chatbot site internet install, meaning one widget covering every page of a website, follows the same rule whatever the site runs on: one copy of the snippet, in the place every page uses. WordPress themes, other website builders and custom builds all offer some form of site-wide header or footer code area, and that is where it belongs. On a custom build, your developer adds it to the shared layout template.
Do not paste the snippet into individual pages through a page-builder block. A theme update or a rebuilt template removes it from some pages and not others, and nobody notices until chats dry up. If you need different widgets on different pages, that is a deliberate set-up covered in placing AI chat page by page.
If your site loads scripts through a tag manager, you can add the snippet there as a tag instead. Choose either the tag manager or the site's code area, never both, and write down which one holds it.
Picture the agency adding the widget through a page-builder block on six key pages. A theme update strips the block from three of them. If nobody notices for 19 days, on pages that would normally produce around 20 chats in that time, those conversations are simply lost. Moving the snippet to the theme's site-wide footer code area would prevent a repeat, and a two-minute chat test on the monthly site checklist would catch anything else.
Page speed and the live chat embed
A widget that loads before your content can delay the page and hurt your speed scores. The widget has a Load on user interaction option intended to help page speed, so switch it on if your speed scores matter. Run a page speed test on your homepage before installing and again afterwards, so you can see the effect on your own site rather than guess at it.
Consent and the cookie banner
The chat script may be held back until a visitor accepts certain consent categories. That is correct behaviour, and it means a tester who declines cookies will not see the widget and may report it as broken. Do not edit your consent tool's configuration as part of installing chat. Check with whoever owns compliance how the script is classified, and test with consent both given and refused. The widget also has its own Compliance notice and consent option for what visitors agree to before chatting.
Installing the snippet in two places, typically the site's footer and a tag manager, or a plugin and the theme. The widget loads twice, chats can duplicate and it becomes hard to tell which copy is broken. Install it in exactly one place and record where.
Asking for details before or during the chat
Requiring a name and email before the chat starts filters out casual visitors but also loses some genuine ones. Asking for nothing produces more conversations and more anonymous ones. A middle path works for most firms: let the visitor ask their question first, then have the agent ask for an email or phone number when it offers to book or follow up. For writing the agent's instructions once the widget is live, see AI chat websites.
Keeping it working after site changes
Most chat outages happen weeks after installation: someone changes the theme, swaps a plugin, moves to a new consent tool or rebuilds a template. Put a monthly check on the calendar. Open the site in a private window, send a test chat and confirm it arrives in Conversations. Add the same check to your website release checklist, so every redesign ends with a test chat.
What it replaces and the time it takes
The platform's chat replaces standalone chat tools and the bottom-of-page contact form as the main way visitors start a conversation, and it keeps everything in one inbox. Installation is a one-off hour or so. The ongoing work sits in the agent's knowledge and instructions, not in the widget.
When not to add chat yet
If nobody can pick up the conversations your agent hands over within a working day, fix that before adding chat. A visitor told "a person will reply" who waits three days is worse off than one who used a form. If you are about to rebuild your website, wait and add chat as part of the new build. And if your site has strict security headers or a deployment process you do not control, hand the snippet to your developer instead of trying a plugin workaround.
Troubleshooting
The widget does not appear. The consent banner is holding the script, a cache is serving an old page, or the change was saved but not published. Accept consent in a private window, clear the site cache and check the code is in the page source.
It appears on some pages but not others. The snippet sits in some templates but not all. Move it to the site-wide header or footer code area.
Two chat bubbles show. An older tool's script, or a second copy of the snippet, is still loading. Search the site settings, templates and tag manager and remove the extra one.
Conversations do not reach the inbox, or nobody answers. The agent is not assigned to that widget. Check the Chat Widget channel on the agent's Deploy tab.
Frequently asked questions
Do I need a developer to install it?
Not on most site builders. You paste one snippet into a site-wide code setting. On a custom build or a site with strict security settings, ask your developer to add it to the shared layout.
Will the code change if I update the widget?
No. Greeting, colours and fields update from the platform. You only need new code if you create a separate widget.
Can I use the same chat on more than one website?
Yes. Install the same widget on several sites, or create one widget per site if they need different greetings or owners. Chat bots for websites covers running several sites. For the agent itself, compare the chat bot for website guide.
Will the chat work on phones?
Yes. Test it on your own phone, because themes sometimes place a sticky button or cookie banner over the chat bubble. If they collide, move the bubble to the other corner in the widget's style settings.