Guide
AI chatbot: where to start without losing focus
The most common mistake when starting is not the wrong technology, but the wrong first step. A sequence that has proven itself in small businesses.
Getting started with an AI chatbot doesn't begin with technology, but with a week of tracking: what repeats, what costs the most time. Then a single, clearly defined workflow with a measurable goal — only with clear scope do quotes become comparable at all.
01 — Getting started
Where to begin
Name the bottleneck
Not the most interesting thing, but what takes the most time. A week of tracking what repeats delivers a more realistic list than any workshop.
Define a small scope
One process, one measurable goal. What works gets expanded — what doesn't costs little.
Survey the starting situation
What content, data and access is available. For an AI chatbot, this is the factor that most strongly influences effort and runtime.
Decide who is responsible
For the implementation and for operations afterward. Without this definition, every system becomes outdated.
Only then request proposals
With a clear scope, proposals become comparable. Without it, you get numbers that have nothing to do with each other.
02 — Fit
When it's worth it
- The process in question occurs at least weekly.
- It follows rules you can write down — even if there are exceptions.
- Today it's manual work that no one enjoys doing.
- There's one person who decides, not three who need to coordinate.
- You can name what would tell you it worked.
03 — Checklist
Clarify before the first quote
- What should improve? In one sentence, no jargon.
- How will you know? One number that should change.
- Who decides? One person, not a committee.
- What budget is available? A range is enough — it makes quotes comparable instead of arbitrary.
- By when? And what the deadline depends on.
- Which systems are involved? And who has access to them.
- What do you already have? Content, data, preliminary work — this reduces the cost.
04 — Questions
Frequently asked questions
How much work does this create for us?
At the start, about two to three hours for gathering content and one alignment round. After that, nothing regular — unless you want to add new topics, which works through a simple document.
Can we turn the bot off again?
Anytime, with one click. The snippet remains, the bot is gone. There's no minimum term that binds you.
What happens to our customers' data?
The conversations run through servers in the EU, no training is done with your data, and we write the appropriate section for your privacy policy. On request, chat logs are automatically deleted after a set period.
Does this even pay off for us?
The calculation is simple: requests per week times processing time times hourly rate. With twenty repeat questions per week and seven minutes each, that's a good two hours of work — every week. We calculate this with your real numbers before the quote.
Does this also work on a WordPress site?
Yes. The integration is a single code snippet in the footer and works the same on WordPress, Shopify, Webflow, Wix, TYPO3, or a custom-built site.
Doesn't an AI chatbot just make up answers?
A free-running language model does. That's why we build the bot so it only answers from a verified knowledge base and provides the source. If it finds nothing, it says so and redirects — that's the most important part of the configuration.
What if the bot answers a question incorrectly?
You see every conversation. Incorrect answers are refined by making the knowledge base more precise. This happens a few times in the first weeks, then rarely after that.
05 — Next
Related pages
- AI chatbot — Overview
- AI chatbot — Duration
- AI chatbot — Common mistakes
- AI chatbot — Checklist
- AI chatbot — DIY
- AI chatbot — Team and acceptance
- AI chatbot — Process
- AI chatbot — Ongoing operation
- WhatsApp chatbot
- AI phone assistant
- Customer support automation
- All guides
AI chatbot by region
Next step
Send us a few sentences about your project.
We read every inquiry ourselves and respond personally. No sales team, no callback form into the void.