How to add an AI assistant to your website in three steps

Adding an AI assistant to a website takes less work than most people expect. The hard part isn't the code. It's deciding what the assistant should know, how it should sound, and what it should do when it doesn't know something. Once those decisions are made, installation is one snippet.

This guide walks through the three steps ChatWith uses, and what to check at each one. The steps apply to any website where you can add a script, including WordPress, Webflow, Shopify, Framer and plain HTML sites.

Before you start

You need two things: a list of the questions your visitors ask, and access to the place where your site's scripts are added. The first matters more. If you know the ten questions that come up most often in email, on calls or in the sales conversation, you already have a test set for the assistant.

It also helps to decide who will read the unanswered questions after launch. The assistant will meet questions your site doesn't cover, and someone on your team needs to review them and fill the gaps. A named person, or a shared inbox, is enough.

Step 1: Connect your knowledge

The assistant answers from the content you connect, so this is the step that decides its quality. Add the sources where your answers already live:

• Your website. Connect the domain and the assistant reads your pages. Websites are re-synced every day, so later edits reach the assistant automatically.
• Your help center or documentation. If your setup steps and troubleshooting live on a separate site or platform, connect it as its own source.
• PDFs and documents. Upload brochures, spec sheets, terms or any file that holds information not published elsewhere.
• Pasted text. Paste in anything that exists only in your head or your inbox, such as a seasonal opening schedule or a current promotion, then keep it up to date.

Once the sources are connected, ask a few questions yourself and read the answers. If a reply is wrong or missing, look at the source it cites. Usually the fix is a clearer sentence on a page, not a change to the assistant.

Step 2: Customize the assistant

Customization shapes how the assistant introduces itself and how it talks. ChatWith lets you set:

• Its name and welcome message. The name visitors see, and the first thing they read when they open it.
• Accent color and position. Choose a color that fits your site and where the launcher sits on the page.
• Tone. How formal or relaxed the replies sound. Tone and appearance settings are part of the Pro and Agency plans, while Growth includes color and welcome message customization.
• Suggested questions. Up to three questions that visitors can tap. Pick the three your visitors ask most, so the first click is a useful one.
• The fallback message. What the assistant says when your content doesn't answer. Write it with a real next step in it: an email address, a contact form or a booking link.

Keep the welcome message short and specific. "Ask about pricing, setup or shipping" tells a visitor more than "Hi, how can I help?" The suggested questions do the same job: they show what the assistant is good at.

Step 3: Publish with one snippet

When the assistant is ready, copy the snippet from its settings and paste it into your site. The snippet is a single script tag, and it goes before the closing body tag of your pages.

The exact place to paste it depends on your platform. In most setups, you add it to the site-wide footer, a custom code area, or a global script setting. The principle is the same everywhere: the snippet should appear on every page where you want the assistant to be available. If your platform only lets you add scripts to some pages, add it to the pages where visitors ask the most questions.

After you publish, do three checks on the live site:

1. Open the assistant on a desktop page and on a phone-sized screen.
2. Ask one of your suggested questions and confirm the reply cites the right source.
3. Ask something your site doesn't cover and confirm the fallback message appears.

If one of those checks fails, fix it before you tell anyone the assistant is live.

Common mistakes to avoid

A few things cause most of the problems we see in assistants that launch badly:

• Connecting too little. An assistant with only the homepage will have many gaps. Add the pricing, policy and help pages before launch.
• Leaving the fallback vague. "We can't help with that" is a dead end. Name the next step.
• Forgetting the unanswered list. The questions your site doesn't answer are the most useful feedback you'll get. Review them every week.
• Testing only with easy questions. Ask the awkward ones: price changes, edge cases, questions with two parts.

Lead capture, if you need it

If you want the assistant to collect leads, lead capture is part of the Pro and Agency plans. When a visitor asks for a follow-up, the assistant asks for their name and email and saves the lead with the conversation attached. That gives your team the question the visitor asked, not just a name in a list.

You can compare what each plan includes in the ChatWith pricing section. You don't need to decide everything before you start: connect your content, publish the assistant, and review what visitors ask in the first few weeks.

Summary

Adding an AI assistant to your website comes down to three steps. Connect the content your visitors need. Customize the name, tone, suggested questions and fallback message so the assistant sounds like your business. Publish it with one snippet, then test it on the live site. Review the unanswered questions regularly, and your assistant gets better as your content does.