Guide

AI chatbot: examples from practice

How an AI chatbot is actually used in the daily life of small businesses — concrete processes instead of product promises, including the cases where it didn't work.

Request assessment ↗AI chatbot

Quote upon request2 to 4 weeksStatus 2026

In short

In practice, an AI chatbot almost always starts with exactly one process, not with an overall concept. Around two-thirds of all initial inquiries at small businesses are repeat questions that a well-maintained knowledge base covers completely. Expansion only happens once the first step demonstrably works in real operation.

01 — Practice

What this looks like in concrete terms

Observation from practice

Around two-thirds of all initial inquiries at small businesses are repeat questions that a well-maintained knowledge base covers completely.

A typical start looks like this: the business names the one process that causes the most trouble. We collect what you already have: website copy, offers, FAQ, email threads. From this, the knowledge base emerges.

After launch, we don't expand immediately — we observe. After the start, we see where answers are missing in real conversations — and add them.

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 — Scope

When we advise against it

The process is still changing. As long as you're adjusting the process itself, manual work is more flexible and cheaper.
Exceptions outweigh standard cases. Then you're automating exceptions, and that gets expensive.
There's no data foundation. Without digitally available source data, the basis is missing.
Volume is too low. With five transactions a month, no system pays off — not even an affordable one.
The real bottleneck lies elsewhere. If you don't have enough inquiries, you don't need faster processing.

04 — Questions

Frequently asked questions

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.

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 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.

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.

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.

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.

05 — Next

AI chatbot by region

Next step

We'll look at your starting position.

Tell us what's eating up time today. That becomes an assessment with effort and benefit — and only then an offer.

Send inquiry ↗ office@pipeline-solutions.at OR +43 681 207 64 203