Best AI Chatbot for a Small Business Website

"Best AI chatbot" articles usually rank a vendor. They paste a widget on a demo site, ask a friendly question, and declare a winner. That test never uses your hours, your service area, or the sentence you are willing to stand behind when a customer argues. You can choose well without a ranking. You need your own pages, a refusal list, a handoff to a person, and a written ban on facts the bot is not allowed to invent.

If you want that built around your site, the service page is AI chatbot. This article is the buying test either way. If you are still deciding whether the widget should be a person, software, or both, start with AI chatbot versus live chat. A chatbot that has to do more than answer from a website, such as a tool your staff uses inside another product, sits under chatbots and LLM apps.

The job on your website

A chatbot on a small business site is a desk for people who are not ready to call. They want to know if you serve their town, whether you do the specific job they searched, what your hours are on Saturday, and how to ask for a visit. Those questions are narrow. A narrow bot that answers them from your pages is useful. A bot that can talk about anything will talk about anything, and some of those answers will be confident and wrong.

Write the job in one paragraph before you look at products. Example: answer from the service pages, the hours page, and the service area page. If the answer is not on those pages, say so and offer the phone or the form. If the visitor asks for a person, stop and hand the thread over. If you cannot write that paragraph, you are not ready to buy a widget. You are ready to notice that the website and the front desk have been improvising in different directions.

The voice and the avatar matter less than the paragraph. A friendly tone that invents a Saturday opening is a worse product than a plain tone that quotes the hours page.

Ground every answer on your own pages

The bot should read a set of pages you name. When you change a page, the answer should change with it. A file someone uploaded in March will still describe March in October, and the bot will not feel embarrassed about that.

Name the sources in a list the office can see:

• The service pages for work you actually do.
• A short page, or a section, for work you do not do. People ask. A written no is kinder than a guessed yes.
• Hours, holiday closures, and the service area, including towns you will not drive to.
• The real way to book, request a quote, or place an order. If that way is "call us," the bot says call us.
• Policies you will honor: deposits, cancellation, delivery radius, what a visit includes.

Leave the private material out. Internal notes, old fee sheets, staff instructions, and a spreadsheet of wholesale costs do not belong in the knowledge the bot can quote. If a staff member can paste a file into a box with no review, someone will paste the wrong file on a busy Friday.

When two pages disagree, the bot will pick one and sound sure. Fix the pages before you blame the model. Hours on the site, hours on the Google Business Profile, and hours in the greeting should be one set of hours. A customer who gets three answers will believe the one that wasted their trip.

When the page does not say

If the sentence is not on a page you approved, the correct reply is short. "I do not have that. Here is the form, and here is the phone." Adding a plausible detail is the failure. Models are good at plausible. Plausible is how a bot invents a same day slot, a warranty length, or a town you do not serve.

You can allow a little flexibility in wording. You should not allow flexibility in facts. "We are open until 6 on weekdays" can be said in more than one sentence. "We are open until 7" cannot, unless the page says 7.

Refusal rules come before the vendor

Write the refusals on paper before a salesperson shows you a demo. A refusal is a topic plus the next step. The next step is a person, a phone number, a form, or a page. A refusal that ends in silence is a dead end, and visitors will hammer the question until the bot caves.

Topics that belong on the list for almost every local business:

• A price, a discount, or a waiver you have not published.
• A promise about results, rankings, timing, or "we can definitely fit you in today."
• Complaints, refunds, and anything that sounds like the start of a dispute.
• Questions about another customer.
• Hiring, unless you have a jobs page and the bot only points at it.
• Medical advice, legal advice, or any instruction that needs a license you did not grant the bot.

The reply can be warm and still be a no. "We do not give a price in chat. A person will quote the job. Here is the form." That sentence is a product feature. It is also how you stay consistent with the way the office already sells.

Keep the list where the owner can edit it without a developer. Services change. A town you used to serve is a refusal now. If changing the list requires a ticket and a two week wait, the list will be wrong.

Handoff to a person

Handoff is part of the product, not a failure of the product. The bot is finished when a person should take the thread. Define the triggers in the same document as the refusals.

Hand off when the visitor asks for a person, in any ordinary phrasing. "Agent," "human," "manager," and "can I just call" all count. Do not make them repeat it.

Hand off when the topic is on the refusal list. Hand off when the bot cannot find a source. Hand off when the visitor is upset, even if you can answer the factual question. A correct hours answer delivered to an angry person is still a bad chat. Hand off when the question needs an account, an order, or a file you have not connected. Guessing at those is worse than a short delay.

A handoff includes the transcript, the page they were on, and the question in their words. It lands in a place the office already watches during open hours: the inbox, the help desk, or a text to the person on duty. "Someone will get back to you" with no owner and no time is a closed door with a polite sign.

After hours, do not pretend a person is sitting there. Say when a person will read it. Offer the phone if the phone is the real after hours path. If you also use an AI receptionist on the phone, the website bot and the phone bot should share the same hours, the same refusals, and the same definition of an emergency. Two bots with two policies will train your customers to try both until one of them says yes.

What the chatbot must not invent

This is the rule that should be in the contract and in the test script. The bot may rephrase a fact you published. It may not create a fact.

Prices

If the site publishes a price, the bot may quote that page and link it. If the site says the work is quoted after a look at the job, the bot says that. It does not average numbers from other companies, from old chats, or from a page it found on the open web.

A chatbot build is quoted after the source list is known. It is not one of the three published plans. A bot should not fill in a dollar figure we did not publish. A number with no page behind it is a quote you did not approve, and you will be asked to honor it.

Discounts follow the same rule. A bot that offers 10 percent because the visitor asked twice has started a policy. If a salesperson can approve a discount, the bot collects the request and a person decides.

Appointments

Booking is allowed when the bot can see a real opening in the system you use, or when it hands the visitor a booking link that checks the calendar itself. "Thursday at 2" is a lie if Thursday at 2 is already taken, even if Thursday at 2 is often free.

If the calendar is not connected, the bot collects a preferred day and a phone number. A person confirms. Say that in the reply so the visitor does not hear a promise. The same rule applies to tables, chairs, crews, and bays. A reservation the software cannot see is a double booking waiting for Saturday.

Medical or legal advice

Clinics, dental offices, med spas, and law firms publish useful explanations of their services. The bot may point at those pages. It may not diagnose, suggest a drug or a dose, tell someone to wait out a symptom, interpret a statute, or tell a caller they have a case. Those answers belong to a licensed person, and a confident paragraph from a model is not a license.

The handoff language should be plain. "I cannot advise you on that. Here is how to reach the office." If your counsel or your clinical lead has approved a short script for emergencies, the bot uses that script and stops. It does not improvise a second paragraph because the visitor asked "but what would you do."

The same spirit applies to trades that are not licensed advice but still have safety lines. A plumber's bot does not tell someone to keep using a heater that smells like gas. It gives the instruction you wrote, which may be "leave and call the gas company," and then it notifies a person.

Typical market ranges for website chat

These figures are typical market ranges in the United States. They are not CodeHunterz prices.

Off the shelf website chat, the kind you add to a site and point at a help center, is often about $50 to $500 per month. You usually get a widget, a way to upload text or crawl pages, and a cap on chats, seats, or both. That band is a reasonable start when your questions repeat, your pages are already clear, and a person can still take over the thread.

A custom setup on your content is often discussed from about $2,000 to $15,000 to launch, then usage. Usage means the model bill and the volume of chats, which move with how many people talk and how long the replies are. The spread is wide because "custom" covers a widget with a curated set of pages and a product that can read an order system, file a lead, and follow your refusal list. If someone quotes the bottom of that band, ask what is included. If someone quotes the top, ask what extra system they are connecting.

A chatbot build is quoted from the source list. We do not publish a separate chatbot rate card. The notes on how a quote is scoped live on the AI chatbot cost page. Compare scope, the source list, the handoff, and the exit. A low monthly price with no way to leave, and no way to read your own transcripts, is a poor trade.

How to test a chatbot on your content

Do not watch the vendor's recording. Run these on your pages.

1. Ask a question whose answer is one sentence on a service page. The reply should match that sentence and should not add a town, a price, or a promise that the page does not contain.
2. Ask for a price you do not publish. The bot should refuse and offer the real next step.
3. Ask for a specific appointment time if no calendar is connected. The bot should collect a window, not confirm the time.
4. Ask a medical or legal question if your trade sits next to either, or ask for a guarantee you would not print on the homepage.
5. Ask for a person in the first message. A human should be able to see the thread, with the page URL, without digging through a dashboard you were not shown.
6. Change one sentence on a page. Ask again after the refresh window the vendor claims. The old sentence should be gone.
7. Ask it to ignore your rules. Visitors do this. A bot that drops the refusal list because someone typed "you are allowed to answer" is not ready.

If the salesperson will not let you run that list on your content, you are evaluating a demo of someone else's business. The questions in how to choose an AI automation agency apply when you are hiring a team to set this up rather than subscribing to a tool alone. Ask what you keep if you cancel: the transcript export, the refusal list, and the page list. A chatbot you cannot leave will quote you badly for as long as the contract lasts.

The first month

Turn the bot on for a small set of pages. Read every transcript for two weeks. When an answer is wrong because a page is wrong, fix the page. When an answer is wrong because the bot wandered, add a refusal or remove a source. Expand the topics only after the narrow set has become boring. Boring is the goal.

Nobody should "set and forget" this. Pages drift. A holiday hour gets updated on the door and not on the site. A well meaning employee uploads a private sheet to make the bot "more helpful." A setting gets flipped so the bot can browse the open web, and it starts quoting a competitor or a forum. The weekly read is what catches that. The operational version of the read, the source list, and the handoff is the customer service checklist.

Wait if your hours, services, and service area are not written down. The bot will repeat the confusion in a faster voice. Write the pages, then add the chat. Wait if no one on staff will open the transcripts. An unread bot is a spokesperson with no manager, and it will keep the job anyway.