Approved knowledge base
Define maintained information about services, processes and recurring questions.
Answers with a clear next step
Website chatbots
Website chatbots answer agreed questions and make the next contact easier. We scope the knowledge base, limits and handover to your team around the inquiries you actually receive.
A website chatbot can help with recurring questions: which service fits, what information is needed and what happens next? Your content and actual inquiry process define its job.
We first establish whether an assistant has a specific job. Direct contact stays available. A chatbot does not automatically attract visitors; unclear offers or limited visibility may make website and SEO work the earlier priority.
How we work
From recurring questions to a tested assistant
Du sollst schnell wissen, ob und wo es sich lohnt. Deshalb arbeiten wir in klaren Etappen: erst prüfen, dann umsetzen, dann ausbauen.
Start here
01
Choose questions and content
Review recurring inquiries, approved sources and desired contact paths.
Next step
02
Plan answers and handover
Agree coverage, required information and when to hand over to the team.
Scale
03
Test and maintain
Test typical, ambiguous and unsupported questions. Assign content and operation owners.
Agreed scope
What we scope for your website chatbots
Website integration
Implement agreed placement, mobile interaction and an accessible direct contact path.
Answer limits and questions
Define covered questions, clarifications and when the assistant hands over to a person.
Inquiry information
Agree useful optional information and where an actual inquiry will arrive.
Data and providers
Agree data sharing, storage, providers and ownership before release.
Tests and maintenance
Check agreed answers and contact paths; scope source updates and ongoing operation separately.
Where it fits
When a website assistant can be useful
Recurring questions
Visitors repeatedly need information that approved content can answer.
Prepare inquiries
A few relevant questions help your team understand the need and next step.
Fix the foundations first
Unclear services or few relevant visitors can make content, website and SEO work more useful first.
Budget and operation
Pricing by scope and responsibility
Website assistant
An entry point for a defined assistant. Knowledge coverage, functionality and ongoing costs are agreed in advance. Agreed questions and content · Integration and direct contact path · Defined test cases and ownership
from €400
Agree project scope, provider and usage costs separately.
Not sure where to start?
We assess the existing website and agree the next steps first.
Review your project: Not sure where to start?Questions before a website chatbot
No. It is an additional route to information and contact. Visitors should still be able to reach your team directly. We define which questions the assistant handles and when it hands over before launch.
We scope the knowledge base and test typical and unsupported questions. Ambiguous inquiries get clarification or a handover path. An AI assistant can still make mistakes, so critical information needs an appropriate human review process.
That depends on the agreed functions and providers. Before release we review data flows, storage, access and required visitor information. The configuration and relevant requirements need to be assessed for the actual project.
The entry price applies to a limited, agreed assistant. Knowledge coverage, integrations and test cases determine the quote. Operation, provider or usage charges and future extensions are identified separately.
We assess the website, integration options and existing contact path. A complete redesign is not automatically necessary. Suitability of the current setup and required changes form part of the initial assessment.
First agree the task: answering recurring questions or preparing contacts. Then review use, handovers and confirmed inquiries over an appropriate period. The number of chat messages alone does not establish a revenue benefit.
Which questions should your assistant answer?
Share your website and typical inquiries. We discuss the use case, contact path and scope.