AI chatbot for your website: how an assistant that answers only from your content works

You have probably already met a chatbot that gave useless or off-topic answers: you typed a simple question and got a list of buttons, or an answer with too much confidence and little substance. Artificial intelligence has changed a lot, but it has brought a new problem: an assistant that answers everything well, even what it does not know.

The solution is not to give up, but to build the assistant the right way: one that answers only from your company's content and honestly says when it does not know.

What changes compared with a traditional chatbot

The rule-based chatbot

It follows a tree of predefined choices: "press 1 for…, press 2 for…". It is predictable but rigid. If the question does not fit the planned path, the user gets stuck.

The AI-based assistant

It understands freely written questions, as a person would ask them, and answers naturally. It is much more flexible. The risk is that, if it is not constrained, it answers with made-up or out-of-context information.

How an assistant "anchored" to your content works

The principle is simple: the assistant does not answer from memory, but consults a knowledge base that you wrote or approved.

1. Knowledge base. One or more documents with what the assistant may say: services, hours, terms, procedures, FAQs.
2. Clear instructions. It is told to answer only from that base and politely decline the rest.
3. Finding the relevant content. When a question arrives, the relevant part of the knowledge base is retrieved.
4. Answer. The assistant words the reply from that content, in the user's language.
5. Handover to a person. If the question is out of scope or needs human action, it points to the contact form or a contact address.

The chat on this site works exactly this way: it answers only what is written in a knowledge base about services and ways of working, and declines the rest.

The advantages for a website

• Immediate answers, at any hour. The visitor does not wait for an email to find out whether you offer a service or how you work.
• Fewer repetitive questions for your team. People focus on the cases that really need attention.
• Better-informed visitors. Whoever reaches the contact form already has a clear idea of what to ask.
• More languages. The assistant answers in the language it is asked in, based on the same content.

The limits to know

A good project does not hide the limits.

• It can still get things wrong. With a good knowledge base mistakes drop a lot, but they do not disappear. That is why the most frequent questions and the "tricky" ones are tested.
• It is only as good as the content. If the base is old or contradictory, the answers will be too. It must be updated like the site.
• It does not replace human relationships. For negotiations, complaints or delicate cases you need a person.
• It has a running cost. Every conversation has a small cost; with spending and request limits there are no surprises.

Privacy and GDPR

An assistant on the site processes text written by people, which sometimes contains personal data. So the following need thinking through from the start:

• what is saved and for how long (often, as little as possible);
• which service the messages are sent to, and whether it uses them to train models;
• the privacy policy, which must mention the assistant;
• an invitation not to enter sensitive data in the conversation.

How it is built, step by step

1. Choose what it must know. List the questions you receive most often.
2. Write the knowledge base. Clear, true and verified content. It is the most important part.
3. Build and connect the assistant to the site, with the right tone of voice.
4. Test with real questions, including out-of-scope ones, and correct.
5. Monitor and improve. Look at the questions it could not answer and add what is missing.

An assistant is not a better site

An assistant helps, but it does not make up for a confusing or slow site. If the site has basic problems (structure, speed, content), it is best to fix those first. If you are interested in the cost side of a site, also read How much does a website cost in 2026.

How to write a good knowledge base

The quality of the assistant depends almost entirely on this document. Some rules that work:

• Write facts, not slogans. "A polished site takes 2-4 weeks" is useful; "fast turnaround" is not.
• One question, one clear answer. Group by topic and use understandable headings.
• Also say what you do not do. Knowing that a service is not offered avoids made-up answers.
• Add the exceptions. Hours, areas served, special terms.
• Say what to do when information is missing, for example suggest the contact form.
• Update it whenever the site changes. An old base produces old answers.

Avoid anything you cannot guarantee: prices that change often, promises, unverified data.

Examples: what it answers and what it declines

A well-designed assistant behaves predictably.

• Question covered by the base: it answers clearly, in the user's language, and if useful suggests the next step.
• Partly covered question: it answers with what it knows and says a person is needed for the rest.
• Out-of-scope question (for example a recipe request or medical advice): it politely declines and reminds the user what it covers.
• Attempt to get around the rules: it does not let itself be talked into ignoring its instructions.
• Request for personal or confidential data: it does not ask for it and does not keep it unless necessary.

Testing these cases before publication is the least showy but most valuable part of the job.

Tone of voice and conversation design

An assistant is part of the company's image. Decide how it should speak: formal or more direct, short or detailed. Some design choices make the difference.

• Short answers, with the option to go deeper.
• A greeting that explains what it can do, so the user is not left puzzled.
• Suggested questions, for those who do not know what to ask.
• A simple way to talk to a person, always visible.
• Accessibility: the chat must also be usable with a keyboard and screen readers.

Why entrust it to me

I have been developing websites and applications since 1999, with more than 300 projects delivered and about 30 agencies as an external developer. I build AI assistants for websites and internal use, connected to the company's content, with verifiable sources and a handover to a person when needed. I work from Rome and remotely.

Before building anything I prepare a prototype on your real content, in a few days, so you see the result before deciding. If AI is not the right solution for your case, I tell you so. To talk about it, write to me: a chat of about 20 minutes, no strings attached. The service is described in AI integration and automation.