
Knowledge assistants
Answers from your own documents, with the source attached, for your staff and your customers.
- 1Connect sources
- 2Chunk and embed
- 3Search: keyword and meaning
- 4Rerank
- 5Answer with sources
A knowledge assistant answers questions from your company's own documents: policies, manuals, contracts and product data. It uses retrieval-augmented generation (RAG): it finds the passages that answer the question, writes the answer from them, and shows where each part came from. PI Square builds them so people only get answers from documents they are already allowed to open.
Your documents
SharePoint, Google Drive, wikis, PDFs, databases
- Your cloud
Indexed with permissions
who may see each passage
The right passages found
by meaning and by keyword
Answered from them
with every source linked
Staff and customers ask
in Teams, Google Chat, your intranet or your app
What it's for
Retail
Store teams ask how to handle a return or a stock count, and get the answer from the current procedure.
Financial services
Staff find the right clause in credit policy or product terms, with the page it came from.
Professional services
Proposal teams reuse past answers to tenders without searching shared drives.
Customer service
Agents and customers get the same answer, from the same source.
How we keep it safe
- Access rights are carried into the index, so an answer never draws on a document the person can't open.
- Every answer links to its sources. When nothing relevant is found, the assistant says so.
- Personal information can be masked before anything reaches the model.
- Before launch, answers are tested against real questions from your team, and tested again after every change.
Built with
- Vertex AI Vector Search
- Gemini
- Claude
- OpenAI
- Python
- FastAPI
- Cloud Run
Where we've built this
- A regulated consumer AI product: an AI companion for mental health and wellness, with every model call checked before it runs.
- A southern African retail group: an assistant that asks employees follow-up questions in Google Chat and builds a complete brief from their answers.
How an engagement runs
Understand
We pick the questions people ask most and the documents that answer them, and test the assistant on a sample.
Prove
One assistant for one team, on the real documents, with the sources of every answer on show.
Embed
Your team owns the sources, permissions and evaluation questions, with an agreed way to maintain the assistant. Additional teams and sources are a separate decision.
Questions about knowledge assistants
- What is retrieval-augmented generation (RAG)?
- RAG makes a language model answer from your documents. The system first retrieves the passages that match the question, then the model writes the answer from those passages and cites them. Your documents stay in your cloud, and the model is not retrained on them.
- Will the assistant make things up?
- Language models can, so we design against it. The assistant answers only from the passages it found, shows its sources, and says when it can't find an answer. Before launch we test it on real questions from your team and check that each answer matches its source.
- Can it respect who is allowed to see what?
- Yes. Permissions from SharePoint, Google Drive or your own systems are stored with each passage in the index, and every search is filtered by the person asking.
- How is retrieval accuracy tested before deployment?
- We compile an evaluation set of representative questions paired with verified passages from your documents. We measure retrieval recall and answer fidelity, checking that every answer is grounded in its source and that unanswerable questions are flagged.
- Does company data remain private and secure?
- The engagement defines where documents and indexes are hosted, who can access them and how model providers process data. Retention and training terms depend on the selected services and configuration; we review those requirements before using business data.
The other five
Agentic workflows
Agents that carry a piece of work from request to done, inside the tools your people already use.
How we build itDocument intelligence
Documents read as they arrive, checked against your rules, and sent where they need to go.
How we build itGenerative content
On-brand images, video and copy in volume, checked against your brand rules before anyone sees them.
How we build itModernisation and integration
Old systems mapped and documented by AI, rebuilt one slice at a time, and proved against the original before anything switches.
How we build itGovernance and guardrails
The controls that let you put AI in front of customers, staff and auditors, and stop it when you need to.
How we build it
Tell us what you're working on
Keep this general; leave out sensitive or confidential information.
Or email nikhil@pisquare.ai