Loading the Elevenlabs Text to Speech AudioNative Player...

TL;DR: A chatbot on a small business website is worth it for exactly one job: answering the same 30 questions your phone rings with, at 11pm, without you. It is not a salesperson, not a booking engine, and not a replacement for a clear website. Here’s what to expect, what to feed it, and where it will embarrass you if you’re not careful.

I build these for local businesses, so I have a bias. I also see the demos vendors run and the disappointment owners feel two months later, so I have a second bias in the other direction. This is my attempt to be straight about both.

What a website chatbot is actually good at

The questions you’re sick of answering. Hours. Parking. Do you take reservations. Is there a kids menu. Do you do gluten-free. Can I bring a dog. How much for a party of 20. Every business has a list like this, and every one of those questions is currently either a phone call, an unanswered DM, or a customer who gave up.

Being awake. Half the people looking at your site are doing it outside business hours. A bot that says “yes, we have a patio, and it’s dog-friendly” at 10:47pm just kept a customer you’d never have known you lost.

Pointing people to the right next step. “Want to book? Here’s the link.” “Planning an event? Here’s the form.” A good bot is a friendly signpost, and a signpost is a lot more useful than most people expect.

What it’s bad at

Anything it wasn’t told. A chatbot only knows what you feed it. If your seasonal menu changed and nobody updated the bot, it will confidently describe a dish you stopped serving in March. This is the number one way bots go wrong, and it’s a maintenance problem, not a technology problem.

Judgment calls. “Can you seat 14 at 7 on a Saturday?” depends on tonight’s book, the host’s mood, and whether the big table is already gone. A bot should say “for parties over 8, call us at [number]” and stop. Bots that try to answer this make promises your staff has to break.

Upset people. Someone who had a bad experience and is typing angrily into a widget does not want a cheerful robot. The bot should recognize the situation, apologize once, and hand off to a human with a clear path. Anything more makes it worse.

Selling. Vendors love to show bots that “close deals.” For a restaurant or a home services company, the bot’s job is to remove friction, not to pitch. A bot that pushes is a bot people close.

What to feed it (this is the whole game)

Before a bot goes live, I build it a knowledge base from four sources:

  1. Your website, page by page. This is the baseline. If your site is thin, the bot will be thin.
  2. Your actual FAQ. Not the one on your site. The one in your head. Ask whoever answers the phone: “what are the 20 questions you get every week?” Write down the answers the way you’d say them.
  3. The rules. What the bot must never do: quote custom prices, confirm large-party bookings, promise a time for a callback, discuss competitors, make things up. When it doesn’t know, it says so and gives a phone number.
  4. The menu, if you’re a restaurant. Item by item, with what’s in it, and honest dietary labels. “Contains dairy” is safe. “Definitely vegan” when you’re not sure is a liability. When in doubt, the bot should say “please confirm with the restaurant.”

The first pass takes a few hours. Keeping it current takes fifteen minutes a month. Skip the second part and the bot slowly becomes a liar.

How to tell if it’s working

Read the conversation logs once a week. Every bot platform has them. You’re looking for three things: questions it couldn’t answer (add them to the knowledge base), questions it answered wrong (fix them today), and questions you didn’t know people had (that’s free market research). The logs are the most useful part of the whole system and almost nobody reads them.

Cost, roughly

The platform is usually a modest monthly fee. The bigger variable is how much conversation volume you get and which AI model sits behind it. A busy site can run more than a quiet one. Ask any vendor two questions: “what happens to my bill if traffic triples?” and “what does the bot say when it doesn’t know something?” The second answer tells you more than the demo does.

Try this

Before you buy anything, spend 20 minutes writing down the 20 questions your phone rings with and how you answer them. If that document doesn’t exist, no bot can help you. If it does, you’ve done the hard part, and any decent bot can take it from there.


Justin Peters runs Zoomies Media, an AI-powered marketing agency for local and hospitality businesses in Orlando. This post was drafted with AI assistance and edited by Justin. Read about how this site works.