Princeton-based · Central & South Jersey

Internal AI Knowledge Assistant Setup

Turn a defined set of approved procedures into a useful place to ask questions. Automati helps scope a knowledge assistant that points people to the source and knows when the available documents do not answer the question.

Discuss your team’s knowledge workflow

Free 15-minute consultation. Paid work is scoped and quoted individually.

Start with a document set someone owns

A good starting collection might be equipment checklists, service descriptions or onboarding procedures. It should have an owner who knows which version is current and can correct it. Connecting every company file at once makes it harder to identify what an answer is based on.

If the documents contradict each other, resolve that before adding AI. Sometimes a short, well-organized handbook and better search are enough. The assistant should make an established process easier to find, not invent missing company policy.

Define a useful answer

  • Give a short answer supported by an approved source, with a link or reference the employee can open.
  • Show which document or version supports the answer, especially for instructions that change.
  • Say when information is missing or conflicting, then point to the person who owns that process.
  • Keep answers within the information that the person asking is permitted to access.
  • Treat instructions inside retrieved files as content, not permission to change accounts or send information elsewhere.

Example: finding the equipment-return procedure

Illustrative scenario: a new team member asks how to return equipment after a job. The assistant summarizes the current checklist and links to it. If asked whether a damaged item can be written off, it identifies that the checklist does not grant that authority and points to the responsible person.

The review checks whether the cited source actually supports the answer. A link attached to an invented answer does not make it correct.

Access boundaries are part of the work

List who can read each collection before choosing a platform. Test with more than one role, including someone who should not see a restricted document. Include removed access and deleted files in the checks.

Microsoft says Copilot surfaces organizational information that the user has permission to view. That makes existing sharing settings important: an assistant does not repair overly broad access automatically. Other products need their own permission review.

Source checked November 8, 2026: Microsoft: Copilot data, privacy and security.

Keep it useful after the first setup

Define how documents are updated, how obsolete copies are removed and who reviews unanswered questions. Test that a changed procedure is reflected in later answers. Keep a simple path for staff to report a wrong or stale response.

Compare source-supported answers, appropriate abstentions, time spent finding information and corrections. Do not measure quality only by how many questions the assistant answered confidently.

Choose local or hosted after describing the task

A contained local setup and a hosted document assistant have different access and maintenance needs. The file store, model, logs and backups all matter. We can discuss those choices without assuming that every connected component is local.

Start with a free 15-minute conversation about one document collection and its users. Use fictional examples initially. Setup, integrations, evaluation and ongoing maintenance are individually scoped and quoted.

Continue with a useful next step

Bring one task. We’ll discuss a useful first step.

Tell us how the work happens today and which tools you use. A description is enough for the free 15-minute conversation. Any paid assessment, implementation or training is separately scoped and quoted.

Discuss your team’s knowledge workflow