Answers about clearer answers.
Understand what the assistant is designed to do, where its answers come from, and what to bring to a useful product conversation.
Explore the questionsStart with the essentials.
Find clear answers about the product experience, source references, team use cases, and preparing for a demo.
01What is an AI knowledge assistant?
It gives people a conversational way to find and understand information across a defined collection of company documents. A team member asks a natural-language question, receives a concise answer, and can follow references back to the supporting material.
02What information can it help my team find?
That depends on the documents included in the knowledge collection. Common sources include policies, product guides, process manuals, internal procedures, and employee handbooks. Answers are grounded in the connected material.
03What does “source-backed” mean?
An answer is paired with references to the documents used to support it. That gives the reader a route to the original wording and its surrounding context instead of asking them to trust an answer on its own.
04Should people still check the original document?
Yes. Source references make checking easier, but important decisions still deserve human review. Teams should open the original material whenever accuracy, policy interpretation, safety, finance, legal duties, or another high-impact decision is involved.
05How are my company documents connected?
Your documents are connected through an authorised WHOLYSTEMS product environment. Access and document sources are configured for your organisation as part of setup.
06Do I need special prompts to ask a question?
The experience is designed around ordinary workplace questions. Useful results still depend on the quality, scope, and currency of the documents available to the assistant.
07Which teams could use it?
Use cases include operations, customer support, and employee onboarding, and the same pattern can apply anywhere a team repeatedly searches approved business documents for guidance.
08What should I prepare for a demo?
Bring a short description of your team’s workflow, the kinds of documents they rely on, and a few questions they often need to answer. Do not upload or paste confidential material into this public website.
09What security or deployment options are available?
Access controls, hosting, data handling, integrations, and retention options are matched to the product configuration and your organisation’s requirements. The WHOLYSTEMS team can cover these details during a demo conversation.