// practical guide

A website chatbot: when you really need one (and when it's a gimmick)

2026 · 08 · 11 — PRACTICAL GUIDEWhen you really need one (and when it's a gimmick)

It's happened to you already: an agency pitches you “the chatbot with artificial intelligence” for your website, your competitor has one, and you're left with the doubt — do I really need it, or am I about to pay for a toy? The honest answer is: it depends, but on precise criteria that no salesperson lists for you. This guide gives you all of them: when a chatbot pays for itself, when it's a gimmick, what it really costs and which simpler alternatives are often enough.

1 · What a chatbot really does today (and what it doesn't)

A modern chatbot, built well, does one thing but does it well: it answers repetitive questions instantly using your business's information — opening hours, prices, delivery times, availability, how a service works. If it's connected to your documents (price lists, FAQs, product sheets), it answers in your words, not with made-up sentences.

What it does NOT do: it doesn't close complex sales, it doesn't handle an angry customer, it doesn't replace the quote you write yourself. And a badly built chatbot — the kind that answers “I didn't understand, please rephrase” — does damage: the visitor leaves more irritated than when they arrived.

2 · The 3 signs you really need one

Before signing any quote, check whether you recognize at least one of these three signs:

• The same questions, every day. Opening hours, shipping, sizes, “are you open in August?” If your inbox or your phone is full of copy-paste questions, it's the perfect use case.
• After-hours requests. If inquiries come in during the evening and on weekends — when you can't answer — every hour of silence is a customer writing to a competitor. A chatbot answers at 11:40 p.m. on a Sunday.
• Whoever answers costs you more than they bring in. If you or someone on your team spend hours answering FAQ-type questions instead of working, the automation pays for itself fast.

3 · When it's a gimmick: the cases where you say no

The chatbot is the perfect gimmick because it “looks modern.” But there are cases where it's just a cost dressed up as innovation:

• A 5-page showcase website with little traffic. If you get 3 inquiries a week, you don't need a robot to handle them: you need to answer those 3 well.
• The requests are all different and delicate. Custom quotes, consulting, personal situations: here the value IS the human answer. Automating it makes a worse impression.
• You have no content to feed it. A chatbot without FAQs, price lists and up-to-date documents is a parrot without a script: it makes things up or doesn't answer. First you sort out the information, then you automate.
• They sell it to you “turnkey” without asking you anything. If whoever's pitching it hasn't asked how many requests you get and of what kind, they aren't solving a problem of yours: they're selling a widget.

4 · The real costs, straight up

The price brackets you'll come across, translated into practice:

• Ready-made widgets (€0–50 a month). Subscription services you install yourself: fine for simple FAQs, but generic answers, limited customization and data passing through third-party servers. Watch out for “free” plans that then lock everything behind an upgrade.
• An AI chatbot configured on your content (mid-range, from a few hundred euros of setup plus a monthly fee). It reads your documents and answers with your information. It's the right level for most small businesses that have the 3 signs from point 2.
• A custom assistant integrated with your systems (from a few thousand euros). It checks real availability, books appointments, hands the conversation over to a human. It only makes sense with serious volumes of requests.

The hidden cost nobody talks about: content maintenance. You change prices or opening hours and don't update the chatbot? Now you have a digital employee giving customers wrong information, 24 hours a day.

5 · The simple alternatives (that are often enough)

If you have only one sign out of three — or want to start slowly — there are three moves that cost little or nothing and cover 80% of the need:

• A well-made FAQ page. Your 15 most frequent questions, with real, up-to-date answers. It's also the essential foundation if one day you do build the chatbot: that work doesn't go to waste.
• WhatsApp Business with quick replies. Welcome message, saved replies for frequent questions, product catalog. For many local businesses it beats any widget — the customers are already there. If volumes grow, that can be automated too: we cover it on the Telegram and WhatsApp bots page.
• A smart form. Instead of a generic “write to us,” a form that asks for the 3-4 right pieces of information (which service, what timeline, what budget). You answer once, with all the data already in hand.

6 · Where to start, step by step

If you've made it this far and the signs are there, the sensible path is this:

• Week 1: for 7 days, write down every question you receive (email, phone, social media). At the end, count the repeats: that list IS the spec sheet for your chatbot.
• Week 2: write the official answers to the top 15. Publish them as an FAQ on your website: from today you answer with a link instead of rewriting every time.
• Then decide with the numbers: if the repetitive questions run to dozens a week, take the step to a real chatbot — one trained on your content, with handover to a human when needed, like the AI virtual assistants we build. If there are few, the FAQs are still yours anyway: you've invested zero and solved the bulk of it.

In short

A chatbot is neither a miracle nor a gimmick: it's a tool. It pays off when you have a volume of repetitive questions, after-hours requests and up-to-date content to feed it. It's a gimmick when traffic is low, the requests are all different, or they sell it to you without having asked you anything. And in between there are the simple alternatives — FAQs, WhatsApp Business, a smart form — which are often the right first step. Criteria first, robot second.

Frequently asked questions