AI chatbot trained on your website: what it means and how to do it
What it means to train an AI chatbot on your website, which content to connect, and how to keep its answers accurate, sourced and up to date.
"Train an AI chatbot on your website" sounds like a technical project. In practice, it means one thing: when a visitor asks a question, the assistant looks in your own content first, finds the passages that answer it, and writes a reply from those passages. If it can't find them, it should say so.
This guide explains how that works, what to connect, and how to keep the answers accurate once the assistant is live. The examples are about a typical business website, but the approach is the same for SaaS products, online shops, agencies and professional services firms.
What "trained on your website" actually means
Most people hear "training" and imagine a model that has learned your business in a deep, permanent way. Tools built for websites usually work differently, and it's worth knowing the difference before you choose one.
Your content is read, split into passages and indexed. When a visitor asks a question, the assistant searches that index for the passages most relevant to the question. It then writes the reply using only those passages. The content stays the source of truth. You don't have to retrain anything when a price changes; you update the page, and the next answer reflects it.
This matters for three reasons:
- Answers come from your words. A reply is built from what you have published, not from general knowledge about your industry.
- Changes show up quickly. When a page changes, the assistant's knowledge of it changes with it.
- Gaps are visible. If nothing in your content answers a question, the assistant has nothing to build a reply from, and that is a signal you can act on.
What to connect
ChatWith answers from the sources you connect. You can add your website, help center, documentation, PDFs, documents and any text you paste in. You don't need all of them. Start with the places where your visitors' real questions already get answered.
For most websites, that means:
- Pricing and plans. Visitors ask about cost, limits and what is included more than anything else. Make sure those details appear in plain text on a page, not only inside an image or a calculator.
- Product or service pages. What you offer, who it is for, and how it works.
- Help center and FAQ pages. Setup steps, troubleshooting and common questions, already written as questions and answers.
- Policies. Shipping, returns, refunds, cancellation, opening hours and booking rules. These are the answers people most want to get right.
- PDFs and documents. Spec sheets, brochures or terms that exist only as files. Upload them so their content is searchable too.
A useful test: if a visitor could find the answer by reading one page on your site, the assistant should be able to find it too. If the answer only exists in your head, your sales team's emails or a shared drive, add it to the site or paste it in as text.
Why sources matter
An assistant that answers without showing where its answer came from asks visitors to trust it on faith. That is a weak position, especially for pricing, legal or medical questions.
ChatWith shows the source of each answer. When a reply comes from your pricing page, the visitor can see that it came from there, and they can open the passage it used. That changes the conversation from "is this bot making things up?" to "this is what our page says."
Sources also help you. When a reply cites a page you no longer think is accurate, you know exactly which page to fix. The answer and the source are one step apart, so the fix happens in the right place.
Keeping the answers current
A chatbot trained on a website is only as good as the website it reads. Websites change: prices move, a feature is renamed, a shipping partner is replaced. Your assistant needs to follow those changes without someone re-uploading everything by hand.
ChatWith re-syncs connected websites every day, so a change to a page reaches the assistant on the next sync. PDFs and pasted text don't update themselves, so when one goes out of date, replace it. A simple habit works well: when you change a price or policy, change the page first, then check the assistant's answer to the question that depends on it.
When the assistant doesn't know
Every assistant will meet questions its content doesn't cover. The important thing is what it does next.
ChatWith doesn't guess. When the connected content doesn't answer a question, the assistant shows the fallback message you wrote, such as how to reach your team or where to book a call. It also adds the question to an unanswered list, so you can see what visitors are asking that your site doesn't yet explain.
Write the fallback message as if it were a helpful colleague. Name the next step, give a real contact route, and avoid anything that sounds like a dead end. A good fallback sends a visitor toward a person without making them feel passed along.
Testing before you rely on it
Before you tell visitors the assistant is ready, spend twenty minutes testing it as a visitor would:
- Ask the questions you hear most often on calls and in email. Check that each answer is correct and that it cites the right source.
- Ask something your site doesn't cover. Check that the fallback message appears and that the question shows up in your unanswered list.
- Ask about something that changed recently. Check that the answer reflects the current page.
- Try a question with two parts, such as "what does the Pro plan cost and what does it include?" Check that both parts are answered.
Keep a short list of these test questions. Run them again after you change your content or your plans.
What a chatbot trained on your website won't do
It helps to be clear about the limits, because they shape how you use the tool.
- It can't answer what your content doesn't say. It will tell visitors so, rather than inventing an answer.
- It doesn't replace your team. Complex, personal or urgent cases still need a person. The fallback and the lead capture step are there to hand over to one.
- It depends on how you write. Clear headings, direct sentences and explicit numbers make better answers than dense, vague copy.
If you want the assistant to take leads, that is available on 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, so your team can reply with context.
A practical starting point
If you're setting this up for the first time, work in this order:
- Connect your website, then add any help center, documentation or PDFs that answer questions the site does not.
- Read through the pricing, policy and FAQ pages and fix anything vague or missing.
- Write a fallback message that names a real next step.
- Test ten questions a visitor would ask, and check each answer and its source.
- Publish the assistant, then review the unanswered list every week and fill the gaps.
When you're ready to compare plans, the ChatWith pricing section lists what each one includes. Once the assistant is live, your existing content does more of the work it was always meant to do.