How to build an AI chatbot for your business, step by step

Building an AI chatbot for a business is mostly not a technical job. The slow part is deciding what it should answer and collecting the facts it needs; the software part takes minutes on a no-code platform, and the testing is where you find out whether you got the first part right. The six steps below use ChatPal, which we make, as the worked example; the advice holds for any tool.

Build it yourself or use a platform

You can write a chatbot in code on top of an AI model, or set one up on a platform that already has the pieces. For a small business answering customers, the second is almost always the right call.

If you are still choosing a tool, our comparison of no-code AI chatbot builders explains the difference between flow builders and builders that answer from your content.

Step 1: decide the one job

A chatbot that tries to do everything does each thing badly. Start with one job and say it in a sentence:

• A dental clinic: answers questions about prices, opening hours and insurance, and passes appointment requests to reception.
• An online store: answers product, delivery and returns questions, and tells signed-in customers where their order is.
• A software company: answers how-to questions from the help center and hands bugs and billing to support.

Then open your inbox, your WhatsApp or your Instagram messages and copy out the 20 questions you answered most last month, word for word. That list decides what knowledge you need in step 2, and it becomes your test set in step 4.

Write down, too, what the chatbot must never handle alone: complaints, refunds, medical advice, anything that needs a judgement call. Those go to a person.

Step 2: give it your knowledge

An AI chatbot for a business answers from the information you give it. Before each reply, it searches your documents for the passages that match the question and writes the answer from them. This is what people mean by "training it on your data": you don't retrain the AI model, you hand it the right pages. Our guide to chatbot knowledge bases explains how that search works.

On ChatPal, the fastest start is the Setup page:

1. On chatpalbot.com, click Start Free Now, enter your email, click Send code, type the code from your inbox and click Verify & login. Or use Continue with Google.
2. On the Setup page, paste your website or a key page, add a short description of the business if you like, and click Let's get started.
3. ChatPal reads the site and drafts the instructions, the welcome message and the chat window's own text, then opens Configuration for you to review them.

If your site runs on Shopify or Horoshop, the Setup page offers to connect the store too, and the assistant then answers product questions from your catalog.

Then add what the website doesn't say. In Configuration, open your assistant:

• On the Files tab, click Upload files and add PDF, Word or plain text files: a price list, a service menu, your returns policy.
• On the Links tab, click Add Link and paste a page address. Tick Single page only if you want just that page rather than the pages it links to.
• Wait until each source shows Ready. A small file usually takes under a minute; a whole site takes longer.

What separates a good knowledge base from a bad one:

• One topic per document. A file called "Prices 2026" and another called "Cancellation policy" work better than one 40-page PDF.
• Exact facts. "Teeth cleaning: $95, 45 minutes" beats "competitive prices for all treatments".
• Your customers' words. If people ask about "whitening", don't only call it "aesthetic dentistry".
• No duplicates or old versions. Two price lists with different numbers give you two different answers.
• Text, not scans. A scanned PDF is an image; copy the text into a Word file first.

When a price changes, delete the old file and upload the new one. When a web page changes, click Reindex on its link.

Step 3: write short instructions

Instructions tell the chatbot how to behave. Facts belong in the knowledge, not here. A good set fits on one screen. For the clinic from step 1:

You answer questions for Riverside Dental, a family dental clinic. Answer only from our documents. Keep replies short and friendly. If the answer isn't in our documents, say you don't know and offer to pass the question to our team. Never give medical advice or diagnose; suggest booking a consultation instead. For appointment requests, ask for the patient's name, phone number and preferred day, and tell them reception will confirm.

Three lines in there do most of the work: what it is for, what to do when it doesn't know, and what it must never do. Leave out price lists, opening hours and long policy text: when they live in the instructions, nobody remembers to update them. Our guide to chatbot instructions that don't hallucinate has before and after examples.

In ChatPal, the Instructions and Welcome Message fields are on the Basic tab of Configuration; click Update when you're done. The welcome message can carry up to 10 quick-reply buttons, shown in your website chat and on Telegram; keep it to three or fewer, each under 20 characters, so they fit on a phone.

Step 4: test it with real questions

Ask your 20 questions from step 1 exactly as customers wrote them, typos and half-sentences included. Polished questions hide the problems.

In ChatPal, click Playground in the left menu. It is the same chat your visitors get, so what happens here is what happens on your site. Under each answer, a short line shows how many sources it used and how confident it was; click it to see the passages it read.

When an answer is wrong, find out why before you change anything:

1. Click Why this answer? under the answer. Copilot, ChatPal's built-in assistant, shows what the chatbot read, why it answered that way and the likely cause.
2. Tell Copilot what the answer should have been. It suggests up to three fixes, such as a document to update or a line to add to the instructions.
3. Click Apply on the right one. It shows the exact change before it goes live, and the change applies to your website too.
4. Click Ask again under the answer and Show changes to compare the new answer with the old one.

A wrong answer usually has one of two causes: the right document is missing, or the wrong one won the search. They need opposite fixes, which is why you look at the sources first.

Then make the tests permanent. Click Save as test on a Playground conversation, and it becomes a saved test in Assistant Tests: your question, plus the answer you expect. Pick how it is graded: Answer similarity checks that the reply says the same thing as your expected answer, and Handed off to a human checks that a complaint still reaches a person. Select your tests and click Run selected after every change to the knowledge or the instructions, because new documents can shift answers that used to be right.

A good test set of 20 covers easy facts, policies, edge cases, questions it must hand to a person, and one or two in another language. Our guide to testing an AI chatbot shows how to build one. Every reply in the Playground and every graded test counts towards your monthly messages.

Step 5: connect it to your channels

Start with one channel, the one where most questions arrive. In ChatPal, click Integrations:

• Chat Widget for your website. Open the Embed code tab, copy the Installation script and paste it just before the closing </body> tag. On WordPress, Wix, Squarespace or Webflow, paste it into the custom code or footer setting. On Shopify you switch on the chat as an app embed in your theme instead.
• Telegram: create a bot in Telegram's @BotFather, click Connect Telegram Bot and paste the bot's token. Our Telegram guide has every step.
• WhatsApp: connect your business number. You can keep using the WhatsApp Business app on your phone alongside the assistant.
• Instagram and Messenger: connect an Instagram Business or Creator account, or a Facebook Page, and the assistant answers direct messages.
• Zendesk: the assistant answers tickets or suggests replies to your agents.

A connected channel shows a green Connected badge. Every channel is on every plan, so adding a second one later doesn't change your ChatPal plan. On WhatsApp, Meta bills replies past 1,000 a month per number.

Before you announce it, decide what happens when the chatbot can't help. In Configuration, open your assistant, click Additional Settings, switch on Enable human-in-the-loop (it saves at once). When a customer asks for a person, the chat moves to the Handed off to a human view in Chats, your team gets an email or Telegram alert, and the assistant stays quiet until someone clicks Return to AI. Your reply goes out on the customer's own channel.

Step 6: watch it and fix it

Plan to spend fifteen minutes a day in the first week. Open Chats, read the conversations, and look for three things:

• Questions it couldn't answer. Each one is a missing document or a fact to add. Add it, then check the answer in the Playground.
• Answers that were wrong. Ask the same question in the Playground, use Why this answer?, apply the fix, and save it as a test so the mistake can't come back. You can also click Create test on the real conversation in Chats.
• Chats that should have reached a person sooner. Tighten the instructions, or add a rule for that kind of request.

You can also ask Copilot what customers have been asking about this week. After the first week, a weekly look is usually enough, plus a test run whenever your prices or policies change.

Mistakes that make chatbots bad

• Uploading everything. Old brochures, internal notes and three versions of the price list give the search more chances to pick the wrong page.
• Putting facts in the instructions. A price written into the instructions is the one nobody updates.
• No way to say "I don't know". A chatbot told to always help will guess. Tell it to admit gaps and offer a person.
• Testing with your own wording. You know what your services are called; your customers don't.
• Going live everywhere on day one. Two channels with problems are twice the cleanup. Start with one.
• Never looking again. Prices, hours and policies change, and the chatbot only knows what you last gave it.

What it costs

On a platform you pay a monthly plan; in code you pay for AI usage, hosting and a developer's time.

ChatPal's plans, checked on 13 October 2026 and billed monthly in dollars (pricing):

• Free: 100 replies a month, one assistant.
• Starter: $20 a month for 500 replies.
• Standard: $50 a month for 1,500 replies.
• Pro: $120 a month for 4,000 replies.

Every channel and integration is on every plan, the free one included, and AI isn't a separate add-on. Each reply the assistant writes counts as one message, including replies to your own tests and from Copilot. You get an alert at 80% of the month's replies, and at 100% the assistant stops replying until the month resets or you upgrade.

To size it, count a week of your own messages. As an illustration, at an assumed 10 customer chats a day and 3 replies each, you'd use about 900 replies a month, which fits Standard. At 3 chats a day, you'd use about 270, which fits Starter.

A sensible first afternoon: sign up on the free plan, paste your website on the Setup page, add your price list and policies, and ask your 20 questions in the Playground. You'll know by the end of it whether the answers are good enough to put in front of customers. For a website chat specifically, see ChatPal's website chatbot page.