Skip to content
AgeDash

Guide · Guide

How to add an AI chatbot to your website that answers from your own documents

By Dev Patel, founder of AgeDash. Published . 8 minute read.

To add an AI chatbot to your website that answers from your own documents, you collect the answers your team already gives, decide what the bot may answer alone and what goes to a person, add the chat to your site with one line of code, and test it with real questions before visitors see it. The model is the easy part. The answers you give it, and the rule for when to stop and ask a person, decide whether customers trust it.

Three kinds of website chatbot

KindWhat it doesGood for
Answers onlyReplies from your pages and documents, takes an email when it does not knowShops and services with many repeated questions
Answers and actsAlso books, moves or checks things in your calendar, store or systemClinics, salons, consultants, anyone who takes bookings
With human handoffA person from your team can take over the live chat, then hand it backBusinesses where some questions always need a person

Most businesses start with the first kind and add the others later. You can try all three in the library: the AI chatbot for your website, the support chatbot that books and AI chat with human handoff.

Step 1: collect the answers you already give

Open your WhatsApp, email and phone notes from the last month and write down the questions people actually asked. For most small businesses, a short list covers most of them: delivery areas and times, prices, returns, timings, location, payment options, and how to book. Write one clear answer for each, in plain words, the way your best team member would say it.

This list becomes the knowledge base. It can live on your website pages, in PDF files, in a Google Drive folder or in Notion. What matters is that it is correct and current, because the chatbot repeats whatever it finds there.

Step 2: decide what it may answer, and what it must not

Write the rules down before anything is built. A good starting point:

  • It answers only from your knowledge base, never from general knowledge on the internet.
  • When the answer is not there, it says so and offers to take an email or a phone number. It does not guess.
  • Refunds, complaints, medical or legal questions, and price negotiations always go to a person.
  • It says it is an AI assistant. People mind it less when it is honest and a person is one step away.

A chatbot that says "I do not know, let me get you an answer" keeps trust. One that invents a delivery date loses it, and the customer remembers.

Step 3: add it to your website

A website chat is usually added with one line of code: a small script that draws the chat button in the bottom right corner of every page. Where it goes depends on how your site is built:

  • WordPress: in the theme settings or a plugin that adds code to the footer.
  • Shopify: in the theme code, before the closing body tag, or through an app embed.
  • Wix and Webflow: in the custom code section of the site settings.
  • A hand-built site: before the closing body tag of the main template.

After that, the colour, the greeting and the answers are changed from the chatbot dashboard, so nobody needs to touch the website again.

Step 4: test it with real questions

Before visitors see it, ask it the questions from your list in Step 1, then ask the awkward ones: a question that is not in your documents, a question in Hinglish, a spelling mistake, an angry message, and someone asking for a person. Check three things for each: is the answer correct, does it say when it does not know, and does it pass the right things to your team.

Fix the source, not the bot. If an answer is wrong, the document is usually wrong or unclear. Correct it there and ask again.

Step 5: plan what happens when it cannot help

Every chatbot meets questions it cannot answer. Decide where those go: an email to your team, a WhatsApp alert, or a live handover to whoever is on duty. Keep a list of every unanswered question. Adding one line to your documents for each is the fastest way to make the chatbot better every week.

Step 6: watch a few numbers

  1. Chats per day, so you know whether people use it.
  2. How many were answered by the AI, and how many went to a person.
  3. The questions it could not answer, as a list to add to your documents.
  4. Leads or bookings that started in the chat.

What it costs to run

Three things decide the running cost: how many chats you get, how long the answers are, and how much of your knowledge base each answer needs to read. A shop with a short FAQ and a few dozen chats a day costs little to run. A large catalogue with long conversations costs more. Ask for the cost per chat in writing before you start, and see it in your dashboard after. See how pricing works at AgeDash.

Mistakes we see in the first month

  • Uploading everything. Old price lists and outdated policies make the bot give old answers. Upload only what is current.
  • No way to reach a person. Visitors who cannot get past the bot leave. Always offer a person, an email or a call back.
  • Testing only easy questions. The hard ones arrive on the first day.
  • Nobody owns the knowledge base. Name one person who adds the unanswered questions every week.

Doing it yourself vs having it built

Several tools let you set up a basic FAQ chatbot yourself in an afternoon. The work that takes time is the rules, the handover to your team, connecting it to your calendar or store, and keeping it correct. If you want that built and run for you from one dashboard, see AI agents and chatbots.

Common questions

Can an AI chatbot answer only from my own documents?

Yes. It can be set up to search only your pages and files for each answer, and to say it does not know when the answer is not there, instead of using general knowledge.

Will the chatbot slow down my website?

A well-built chat loads after the page, so the page itself does not wait for it. Check your page speed before and after adding it.

Can it work in Hindi and Hinglish?

Yes. Current AI models understand and reply in Hindi, English and a mix of both. Test it with the way your customers really write.

Can the same chatbot work on WhatsApp?

Yes. The same knowledge base and rules can answer on your website chat and on WhatsApp, if your number is on the WhatsApp Business API.

How do I keep the answers up to date?

Change the document, not the bot. When your prices or policies change, update the page or file it reads from, and the next answer uses the new version.

Try it yourself

Playable demos from the AgeDash library, with fictional data.

Support

AI chatbot for your website

A chat button in the corner of your website. It answers visitors from the pages and documents you add in your AgeDash dashboard, and takes an email for your team when it does not know.

Tools: Website chat widget, Google Drive, Notion, Shopify, Email, n8n+1
Try the previewView dashboard
Support

AI support chatbot that books and changes appointments

The website chat that does the job, not only answers: it books from your real calendar, moves a booking, and sends the confirmation on WhatsApp or email, all inside the chat.

Tools: Website chat widget, Google Calendar, Outlook Calendar, Google Meet, WhatsApp Business API, Email, SMS (Twilio), Google Sheets, n8n+4
Try the previewView dashboard
Support

AI chat with live human handoff

When a customer asks for a person, the AI confirms, alerts your team by pop-up, message or call, and steps aside while someone takes over the chat from AgeDash. When they finish, the AI carries on.

Tools: Website chat widget, WhatsApp Business API, Slack, Microsoft Teams, SMS (Twilio), Google Drive, n8n+2
Try the previewView dashboard

Read next

Want this set up for you?

Book a 30 minute call. We look at how you work today and say plainly what is worth automating.