# Let your team ask the company’s documents a question and get a sourced answer

> A private AI knowledge assistant uses retrieval-augmented generation (RAG): it searches your own documents for the passages relevant to a question, then has a language model answer only from those passages and cite them. Cognova AI builds these assistants for internal teams, connected to SharePoint, Google Drive, wikis and policy libraries, with each person seeing only what they already have permission to open.

Service: Private AI Knowledge Assistant (RAG) · For: Teams of 10 to 500 people whose answers are buried in shared drives, wikis and email · URL: https://cognovaai.com/services/ai-knowledge-assistant · Updated: 2026-11-18

## Problems we solve

- New hires take months to learn where things are and who to ask.
- Senior staff answer the same internal questions about procedures, pricing and policy every week.
- The answer exists in a PDF or an old email thread, but search cannot find it.
- Staff use public AI tools to answer company questions, which leaks data and invents answers.

## How we work

### 1. Source inventory and cleanup

We list the folders, wikis and systems the assistant should read, flag outdated or duplicate documents, and agree what is excluded.

### 2. Permission-aware indexing

Documents are split, indexed and tagged with their existing access rights, so a question from one team never surfaces another team’s restricted files.

### 3. Answer rules

The assistant answers only from retrieved passages, cites them, says when it cannot find an answer, and refuses topics you rule out.

### 4. Test with real questions

We gather questions your staff actually ask, check every answer against the source, and tune search and instructions until accuracy is acceptable.

### 5. Roll out where people work

Deployment in Teams, Slack or a web app, with content owners who keep sources current and a monthly review of unanswered questions.

## What you get

- Source map with owners and exclusions
- Search index that respects existing permissions
- Assistant in Teams, Slack or a web app, with cited answers
- Test set of real staff questions with accuracy results
- Report of unanswered questions to guide new documentation
- Admin guide for adding sources and owners

## Timeline

First team live in 4–6 weeks; further sources and teams added in 2–3 week phases.

## What it costs

| Engagement | Typical range | What drives the price |
|---|---|---|
| Knowledge assistant build (first team or department) | $10,000–$30,000 | Number of sources and systems, permission complexity and document cleanup needed. |
| Hosting, upkeep and new sources | $400–$1,500/month | Number of users and documents, and how often sources change. Model and search usage billed at cost. |

Typical ranges, not quotes. Your price depends on scope, integrations and call or content volume, and is fixed in writing after a free 30-minute call. Usage costs (phone minutes, AI model usage) are billed at cost.

## Knowledge assistants for Dallas–Fort Worth teams

Multi-office DFW firms, such as engineering, accounting, property management and healthcare groups, often have the same procedure saved in different versions across sites. The source cleanup step is where we resolve that with your team, in person when it helps.

Your data stays in your own Microsoft 365, Google Workspace or cloud accounts. We set the assistant up there rather than copying your documents into a third-party tool.

Serving Dallas, Fort Worth, Plano, Irving, Frisco, Richardson, Arlington, Addison, McKinney, Garland.

## Frequently asked questions

### What is a RAG chatbot?

RAG stands for retrieval-augmented generation. A RAG chatbot first searches a set of documents for passages related to the question, then gives those passages to a language model with instructions to answer only from them. That keeps answers tied to your own content and lets the bot cite its sources, instead of relying on what the model learned in training.

### How is this different from your AI chatbot development service?

Our chatbot service is mainly customer-facing: website and help-desk assistants that answer buyers and customers. The knowledge assistant is internal. It reads documents staff cannot share publicly, enforces who can see what, and is judged on how well it helps employees find procedures, policies and past work.

### Does Microsoft 365 Copilot already do this?

Partly. Copilot can search content in your Microsoft 365 tenant for licensed users, and for some firms that is enough. A custom assistant makes sense when knowledge also lives outside Microsoft 365, when you need stricter answer rules and citations, or when buying Copilot licences for every user costs more than a focused assistant.

### Will staff see documents they are not supposed to?

Not if permissions are designed in from the start. We index each document with its existing access rights and filter search results for the person asking, so the assistant cannot quote a file that person could not open. We test this with accounts from different teams before rollout.

### What happens when the documents are wrong or out of date?

The assistant will repeat what the documents say, so content quality matters. We flag duplicates and stale files during setup, assign an owner for each source, and send a monthly list of questions the assistant could not answer or got flagged, which shows exactly which documents to fix.

---

Cognova AI · hello@cognovaai.com · (940) 331-4304 · 17370 Preston Rd #490, Office B, Dallas, TX 75252
Book a call: https://cognovaai.com/contact
