Assistant

An assistant for staff, not a public chat.

People ask about a procedure, an internal case, or where the right document lives. The answer is computed by a model inside the company, not by a browser tab wired to someone else’s cloud.

01

Internal

An employee account, not an anonymous widget on the marketing site.

02

Source

An answer can be checked against a procedure once documents are connected.

03

A person

The program suggests. Decisions and sending stay with people.

Where it fits

The useful first cases are dull and repetitive. That is the point.

  • Questions about internal procedures and rules that already sit on the intranet.
  • Help for IT: where to report a fault, what the workplace standard looks like.
  • A draft reply to a repeated email, before a person sends it.
  • A new employee finding where things live, without searching a colleague’s mailbox.

What the assistant does not do

We do not put it in front of end customers until the organisation chooses that on purpose. That step needs its own rules: what may be said, how to show that a program is replying, and how to cut off data it should not see.

We do not promise that it will “run the company”. If procedures contradict each other, the assistant will repeat the contradiction. Tidying the sources is part of the work and connects to document search.

Access and trace

An employee’s question can be personal data. Logs are kept only as long as diagnostics need, and only for named administrators. Retention is written down with the deployment, together with compliance.

When the assistant should look at mail or tickets, the reading scope is agreed with the system administrator. Connections are described under integrations.

Call Request a proposal