AI · Jun 2026
An AI chatbot is no longer a gimmick in the corner of your website. Done well, it answers real questions, qualifies leads and books appointments around the clock. Done poorly, it frustrates everyone who touches it. This guide walks through what a serious business chatbot actually is, what it costs, and how to commission one without regret.
Most people picture a chatbot as the scripted bubble that pops up with "Hi, how can I help?" and then fails the moment you ask something off-script. That is a decision tree dressed up as intelligence. It can only do what someone explicitly programmed it to do, and it breaks on the first question phrased in a way nobody anticipated.
A modern AI chatbot works differently. It runs on a large language model and understands intent, nuance and context, even when a customer types messily, switches languages or asks two things at once. The difference is not cosmetic. One deflects work away from your team because it genuinely resolves questions; the other quietly trains your customers to skip the bot entirely and ask for a human.
When you decide to have an AI chatbot built, this is the line that matters most. You are not buying a widget; you are buying a layer of judgment that sits between your customer and your business. That layer is only as good as what it knows and how carefully it was set up.
A language model out of the box knows a lot about the world and nothing about your business. It does not know your prices, your return policy, your delivery times or the name of the product you launched last month. Ask it directly and it will either refuse or, worse, invent a plausible-sounding answer. For a customer-facing tool, a confident wrong answer is far more dangerous than no answer.
The technique that solves this is called retrieval-augmented generation, or RAG. In plain terms: your own documents, your website, your FAQ, your product catalogue and your policies are indexed and stored. When a customer asks a question, the system first retrieves the relevant passages from your material, then asks the model to answer using only that source. The model becomes a careful reader of your knowledge rather than a guesser.
This is the single biggest factor in whether a chatbot feels trustworthy. A well-built RAG setup can cite where an answer came from, stays current when you update a document, and refuses gracefully when something falls outside its knowledge. That is the foundation we build on for every AI chatbot we deliver.
Three use cases carry most of the value. The first is customer service: a chatbot trained on your knowledge base handles the repetitive forty to sixty percent of incoming questions instantly, at any hour, leaving your team the cases that genuinely need a person. The second is lead qualification: instead of a static contact form, the bot asks the right follow-up questions, understands what the visitor needs and passes a warm, structured summary to sales. The third is booking and scheduling: the bot checks availability, proposes slots and confirms appointments directly in your calendar.
What these have in common is volume and repetition. If something happens dozens of times a day and follows a recognisable pattern, a chatbot is a strong fit. If it happens twice a month and every case is unique, automation rarely earns its keep. The honest test is not "could a chatbot do this" but "does this happen often enough to be worth automating".
The most valuable chatbots rarely stop at conversation. They tie into the systems behind them: your CRM, your inbox, your booking tool. That handoff between talking and doing is where a chatbot becomes part of your AI automation rather than a standalone novelty.
A good chatbot knows its limits. It answers what it can defend from your material and hands off cleanly to a human the moment it is uncertain, rather than bluffing. It keeps the context of the conversation, so a customer never has to repeat themselves. It speaks in your tone of voice, not in generic support-bot phrasing. And it leaves a trail: you can see what people asked, where it succeeded and where it struggled.
Equally important is what a good chatbot does not do. It does not promise things you cannot deliver, it does not guess at prices, and it does not pretend to be human when asked directly. These guardrails are not a limitation; they are what makes the tool safe to put in front of real customers. A chatbot that occasionally says "I will connect you with a colleague for this" earns far more trust than one that answers everything and is sometimes wrong.
A serious build follows a clear arc. It starts with discovery: which questions come in, where the volume sits, which systems need to connect, and what tone fits your brand. Then comes knowledge preparation, where your content is gathered, cleaned and indexed, because the quality of the answers depends entirely on the quality of the source. After that the conversation design and guardrails are set, the integrations are wired up, and the bot is tested against real historical questions before it ever meets a customer.
For a focused, single-purpose chatbot, expect roughly two to four weeks from kickoff to a live pilot. A broader build with multiple integrations, several departments or complex workflows typically runs six to ten weeks. The first two weeks after launch matter most: you watch the real conversations, find the gaps and refine. A chatbot is not a project you finish; it is a system you tune.
Cost splits into two parts, and any builder who hides one of them should give you pause. The first is the one-off build. A focused chatbot with a tight scope and a clean knowledge base typically lands between 2.500 and 6.000 euro. A more substantial build with multiple integrations, custom workflows and a larger knowledge set runs from roughly 7.000 to 20.000 euro and up, depending on complexity.
The second part is the monthly running cost, and this is real. It covers the model usage (you pay per conversation behind the scenes), the hosting of your knowledge index, monitoring and maintenance. For most small to mid-sized businesses this sits somewhere between 150 and 600 euro per month, scaling with conversation volume. A bot that handles thousands of conversations costs more to run than one handling dozens, simply because the underlying model usage scales with traffic.
The point of these ranges is not precision but realism. The right way to judge cost is against the work the chatbot removes. If it deflects even a few hours of repetitive support per day, the monthly fee is modest against a salaried employee doing the same. If it qualifies leads that would otherwise leak through a dead contact form, it pays for itself in conversions long before it pays for itself in saved hours.
Honesty here separates a partner from a vendor. A chatbot is the wrong tool when your information is genuinely sparse: if you have no documented answers, no FAQ and no consistent policies, there is nothing for it to learn from, and you would be automating chaos. It is also wrong when your interactions are low-volume and high-stakes, such as bespoke legal or financial advice, where every answer must be human and accountable.
And sometimes the better answer is automation without a chat interface at all. If the real bottleneck is internal, like processing orders or routing emails, a quieter workflow behind the scenes serves you better than a bot on the website. The right question is never "do we want a chatbot" but "what is the actual bottleneck, and is conversation the right shape for solving it". We would rather tell you a chatbot is not the answer than sell you one that disappoints.
Ask three questions of any builder. First: how do you handle wrong answers and hallucination? A serious answer involves grounding in your content, clear guardrails and graceful handoff, not "the model is very accurate". Second: what happens after launch? A chatbot needs monitoring and tuning, so a one-and-done delivery with no aftercare is a warning sign. Third: who owns the knowledge and the data? You should retain control of your own content and conversations, and understand where the data flows.
Look for a builder who talks about your business before they talk about technology, who is comfortable saying no, and who can show you the difference between a chatbot and a broader strategy. If you want to go deeper, our pieces on implementing AI agents and on whether a chatbot is a gadget or a gamechanger are a good next read. The right partner leaves you with a tool you understand and can grow, not a black box you are afraid to touch.
You do not need to have everything figured out to start. The most useful first move is a short, honest conversation about where your real volume sits and whether a chatbot is the right shape for it. Sometimes the answer is yes and we map a clear path; sometimes it is a quieter automation instead. Either way you leave with clarity rather than a sales pitch. When you are ready, reach out and we will think it through with you, no pressure attached.