AI Assistants on Small Business Websites: Useful Tool or Gimmick?

The question behind the question

When owners ask me whether their site needs an AI assistant, what they usually mean is: customers ask the same twenty questions over and over, and answering them costs time — can software take that over?

Sometimes yes. An AI assistant is a chat window powered by a language model — software that generates humanlike text — and it can genuinely handle the repetitive layer: hours, service area, what you do and do not offer, how booking works, what to bring to an appointment.

The same technology also confidently makes things up when it does not know the answer. The industry calls this hallucination, and it is not a rare glitch — it is how these systems behave by default when unconstrained. For a business whose whole advantage is trust, that makes the technology worth understanding before it is worth buying.

What a site assistant can genuinely do well

Grounded in your actual content, an assistant is good at:

• Hours, location, parking, and service area — instantly, at eleven at night, when nobody is answering the phone.
• What services you offer and do not offer, which saves the calls you could never serve anyway.
• Process questions: what happens at a first visit, what a quote includes, which payment types you take.
• Pointing visitors to the right page or form, or capturing a name, need, and phone number for a callback.
• Answering in the visitor's own language, which matters in a region as multilingual as the DMV.

Notice the pattern: these are lookup questions whose answers already exist in writing. A good assistant is a friendlier search box over your own content. That alone can be worth having, since an after-hours visitor otherwise leaves with nothing.

Where it hallucinates — and what that costs you

An unconstrained assistant answers every question, including the ones it has no basis for, in the same fluent, confident tone:

• Prices. It will happily quote numbers you never set.
• Availability and promises — telling someone a technician can come Tuesday.
• Guarantees, warranties, and policies you do not actually have.
• Anything requiring judgment: diagnosing a problem from a description, whether something is covered, legal or medical or safety specifics.

Here is the part that matters: to your customer, a chatbot's answer on your own website is a promise from your business. They may hold you to it, or walk away angry when you correct it. The trust cost of one confidently wrong price outweighs the value of a hundred correctly answered questions about your hours. Any assistant that cannot say it does not know and hand off to a human should not be speaking for you.

Grounding: the one technical concept worth knowing

Grounding means the assistant is only allowed to answer from a specific set of content you give it — your pages, your FAQ, your policies — instead of from the model's general imagination. Vendors describe this as training it on your content or connecting a knowledge base; the label matters less than the behavior.

When you evaluate any product, this is the conversation:

• Can I control exactly what it knows, and does it decline or hand off when the answer is not in there?
• Can I read transcripts of what it actually told visitors?
• Can it collect contact details and escalate to a human?
• Can I correct a wrong answer today, not next month?

Then test it yourself before it goes live. Ask about a price you never published, a service you do not offer, and something absurd. If it improvises instead of declining, it is not ready to wear your name.

Costs, and the checklist that makes the decision

Realistic pricing: entry-level grounded chat tools run roughly $20 to $100 a month. More capable products with human handoff, booking, and integrations run $100 to $500 a month. Fully custom builds cost thousands and are rarely where a small business should start.

The decision checklist — install one only if every box checks:

1. You get repetitive lookup questions weekly, and their answers exist in writing. If they do not, writing the FAQ page comes first.
2. The tool is grounded, declines unknowns, and hands off to a human.
3. You can read transcripts, and someone will actually review them during the first month.
4. You have decided what it must never answer: exact quotes, guarantees, emergencies.
5. Your phone number and contact form stay front and center. An assistant is an addition, never a replacement.

What to do next

1. Write down the twenty questions your business actually gets, and publish the answers on a real FAQ page first. It is the cheapest fix, it helps your search rankings, and it becomes the exact grounding content an assistant would need later.
2. If the checklist passes, trial one grounded tool on a monthly plan and feed it only your published content.
3. Spend fifteen minutes trying to make it lie before launch, and again after any update.
4. Review the first month of transcripts and count conversations that ended in a captured lead or a booked job.
5. Judge it like an employee: helpful, honest, and cheaper than the alternative — or gone.

I build websites and custom software for a living at HashWhales, and my honest take is that a good FAQ page plus a fast human reply beats a mediocre bot every time. The businesses where assistants shine are the ones that already had their answers written down. Start there.