A chatbot that only says what is actually true for your business.
The difference
Generic bot or assistant with your knowledge.
Many chatbots know the internet, but not your company. We ground the assistant in your own knowledge and draw clear lines where it should not answer.
Generic bot
Guesses when knowledge is missing
If information is missing, it still produces an answer – convincing in tone, but wrong on the facts.
Answers in generalities
Customers get boilerplate that would fit any company – just not your products and prices.
Ends in a dead end
When the bot gets stuck, the conversation goes in circles – and the customer is gone.
Stays a black box
You never find out what the bot told your customers – or only when someone complains.
Assistant with your knowledge
Knows products, prices and processes
The assistant answers from your own content: website, documents, price lists and internal guidelines.
Says "I don't know"
If it finds no reliable basis in your knowledge, it says so.
Hands over cleanly to your team
When uncertain, or at the customer's request, the conversation lands with the right person, along with everything discussed so far.
Every conversation visible
You see what was asked and answered – and spot early where the assistant is still missing knowledge.
How a conversation flows
From question to a sourced answer.
Every answer follows the same principle: search your knowledge first, then answer and show the source. If the basis isn't there, a human takes over.
Question
A customer or employee asks a question – in the website chat, by email or in an internal tool.
Knowledge match
The assistant searches your approved content: product data, documents, guidelines, previous answers.
Answer with source
It answers based on what it found and links to the source, so the answer stays verifiable.
Handover to a human
If the basis is too thin or the matter is sensitive, it hands the conversation to your team – history included.
You define these boundaries and can adjust them at any time: which topics the assistant answers, where it asks a follow-up question and when your team takes over.
Examples
What this looks like in action.
Website chat that sells at night
Trigger
Saturday, 11:40 pm: a prospect asks in the website chat about delivery time and volume pricing for a product.
Result
The assistant answers from your product data, clarifies the follow-up question and creates the contact as a lead in your CRM, conversation included. Your team sees it first thing Monday.
Internal assistant for your team
Trigger
An employee is looking for the current work instruction for a rarely used machine.
Result
Instead of digging through three folders, they ask the assistant and get the relevant section from the right document – with a link to the source, in the current version.
Ticket assistant with sign-off
Trigger
A support request arrives by email in the helpdesk.
Result
The assistant categorises the request and drafts a reply from your knowledge base. Your employee only has to review and adjust – ten minutes per ticket become two.
Channels & integrations
Where your customers and your team already are.
We put the assistant where your enquiries already arrive: in the website chat, the inbox, the helpdesk. Nobody has to remember a new channel.
Frequent questions
Four questions almost everyone asks.
That is why the assistant only answers from your approved content. If it finds nothing on a question in your knowledge, it says so and hands over to your team. Before launch we test together with the kinds of questions you really get, and you can review every conversation afterwards.
We connect your existing sources: website, documents, price lists, ticket histories. When content changes, the knowledge base updates automatically or after your approval. You keep maintaining content where you already maintain it today – not in a second system.
Before launch we clarify which data the assistant may see, where it is processed and how long conversations are stored. On request we use European providers or self-hosting, and personal data stays out of the knowledge base. We put all of this in writing together with you.
A rule of thumb: if your team answers the same five questions every day, or enquiries sit unanswered in the evenings, an assistant usually pays off. With a handful of enquiries per week it usually doesn't – a well-maintained FAQ is the better investment then.
Next step
Which questions does your team answer over and over?
Tell us where these enquiries land today – in the inbox, on the phone, in the chat. Then we can see together whether an assistant can absorb them and where to begin.