A small business does not need a chatbot that books flights, negotiates refunds, or holds a conversation about the weather. It needs the same twenty questions answered correctly, instantly, at eleven at night, without anyone picking up a phone. That is a much smaller problem than the marketing around AI suggests, and it is one you can solve this afternoon.
This guide covers what a chatbot realistically does for a small business website, what it does not, and the shortest path from nothing to a working widget on your site.
What it realistically does
Trained on your own pages and documents, a website chatbot answers the questions your content already answers. For a typical small business that means:
- Opening hours, location, parking, and how to reach you
- Prices, what is included, and what costs extra
- Delivery times, shipping areas, and return rules
- How to book, cancel, or reschedule
- Whether you do a specific thing, in the words a customer uses rather than the words on your menu
It does this in the customer's language, at any hour, and hands over to you when a question needs a person. A chatbot for small business websites is a well-read receptionist who never sleeps and never improvises.
What it does not do
It does not know things you have not told it. If your returns policy is not on a page or in a document you uploaded, the chatbot cannot answer returns questions, and a good one will say so rather than guess.
It does not take payments or process bookings itself. It points people to your booking page or store, which is the right design: your checkout stays your only checkout.
It does not replace a person for anything that requires judgment, a discount, or an apology. Set the handoff up properly and those conversations reach you faster than they did through a contact form.
Start with your actual questions
Before you touch any software, spend ten minutes with your inbox and your call log. Write down the questions you answered last week that you have answered a hundred times before. Group them. You will usually find three to five clusters that account for most of the volume.
That list is your specification. It decides which pages to feed the chatbot, how to test it, and how to judge whether it is working. Do not skip this step; the businesses that are disappointed by chatbots are almost always the ones that trained them on everything and tested them on nothing.
What to train it on
Take your question list and find the page or document that answers each cluster.
- Hours, location, and contact: your contact or about page
- Prices: your pricing or services page, or a PDF price list
- Delivery and returns: the policy pages, exactly as written
- Booking: the page that explains how, with the link
- Product questions: the product or service pages themselves
Add those, and only those, to start. Leave out the blog, the news page, and anything that describes how things used to work. A retired offer on an old page will be quoted with complete confidence. The guide to training a chatbot on your own data goes deeper on what to include and what to leave out.
Setting it up
The whole process, on the hosted website builders, needs no developer.
- Create the chatbot and give it a name customers will recognise, usually your business name.
- Add the sources from the list above. Website pages by URL; price lists and policies as files.
- Add support contacts: your email, phone, and booking link. This is what the chatbot offers when it cannot answer, so do it before launch, not after the first stuck customer.
- Write the welcome message in your own voice. Two sentences: what it can help with, and that a human is available.
- Copy the embed snippet and paste it into your platform's custom code area. WordPress, Shopify, Wix, Squarespace, and Webflow each have one; the platform guides show the exact spot for each.
Reload a public page and the widget is live.
Test like a customer, in your customers' words
Open your own site in a private window. Ask the questions from your list, phrased the way customers phrase them. Not "what are your operating hours" but "are you open Sunday". Not "return policy" but "can I send it back if it doesn't fit".
Read every answer. Three things can be wrong: the answer is right (good), the answer is missing because the page did not cover it (add or fix the page), or the answer is wrong because the source was out of date (fix the source). Each of those is a five-minute fix, and after one round the chatbot is better than most of the ones you have used as a customer.
Put it where questions get asked
The floating widget on every page is the default and it is right for most businesses. Two additions help:
- Put it on your contact page above the form, so the easy questions never become emails.
- If you have a docs or FAQ page, consider the inline mode, which renders the chatbot as a panel where a search box would go. The AI website search page shows how that looks.
What it costs
Start on the free plan. It puts a real chatbot on your real site with no card, and the only limit you are likely to feel is the daily message cap. When you hit that cap, you have proof the widget is being used, and the paid plans are flat monthly prices in your local currency with no per-conversation fees. Paid plans do not auto-renew, so a quiet season never bills you. The live numbers are on the pricing page, and the pricing logic is explained in how much does an AI chatbot cost.
The realistic first month
Week one, the chatbot answers the obvious questions and a few surprising ones you had not written down. Week two, you fix the sources for the questions it missed. By week three, the contact form gets fewer emails and the ones it gets are the ones that need you. By week four, you have a list of questions you never knew customers had, which is the best marketing research you have done all year.
Frequently asked questions
Do I need to write scripts or decision trees? No. The chatbot answers from your content, not from a flowchart. You maintain pages, not conversation paths.
What if a customer asks something rude or off-topic? It stays on your content and politely declines anything outside it. It does not become a general assistant on your site.
Can I run it on two locations or two brands? Yes, as separate chatbots with their own sources, each embedded on its own site. Plan limits on the number of chatbots are shown on the pricing page.
