PIPELINEGuide
Implementing an AI chatbot: step by step
The path from decision to live operation — in the order that has proven effective in small businesses, including the points where projects typically get stuck.
An AI chatbot is implemented by first naming the bottleneck, then defining it narrowly, and only then proceeding with implementation. The implementation itself takes 2 to 4 weeks; a project is almost never delayed by technology, but by missing content, access, and decisions.
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 — Process
The steps in detail
Review content
We gather what you already have: website copy, offers, FAQs, email threads. This becomes the knowledge base.
Define response behavior
What may the bot answer, where must it redirect, what tone fits you. This is documented in writing, not guessed.
Test run with real questions
We feed the bot the 50 most common inquiries from your day-to-day and correct until the answers are right.
Go live and refine
After launch, we see where answers are missing in real conversations — and add them.
03 — Participation
What we need from you
- A contact person who can make decisions — not just forward them.
- Access to the affected systems, in time and not on launch day.
- Real examples from daily business — the messier, the more useful for testing.
- Two to four hours for coordination, distributed over the project duration.
- An answer to the question of what success means. Without it, nothing can be assessed afterward.
04 — Bottlenecks
What typically causes delays
- Content and deliveries. By far the most common cause of delay. Text, images, price lists, access credentials — what's missing blocks progress.
- Decisions. When it's unclear who approves, the project waits. A named contact person with decision-making authority noticeably shortens the timeline.
- Access to third-party systems. Getting access to inventory management, phone systems, or CRM regularly takes longer than the integration itself.
- Endless review rounds. Two correction rounds are normal, five are a sign that the goal wasn't clear at the start.
05 — 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.
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.
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.
Do we have to label the chatbot as AI?
Yes. Since August 2026, the transparency requirements of Article 50 of the EU AI Act apply: Anyone communicating directly with an AI system must be able to recognize it. We build the labeling in as standard, it costs nothing extra.
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.
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.
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.
06 — Next
Related pages
- AI chatbot — Overview
- AI chatbot — Duration
- AI chatbot — AI disclosure
- AI chatbot — Team and acceptance
- AI chatbot — Checklist
- AI chatbot — Common mistakes
- AI chatbot — Real-world examples
- AI chatbot — Funding
- 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.