Flagship · bounded onboarding

Business Knowledge Assistant

Answers come only from documents you approve. Every answer shows its source. If the approved set cannot answer, the assistant hands off. It does not invent policy.

Onboarding before the first answer

Source set

You name the playbooks, policies, and SOPs that may be used. Everything else is out of bounds until it is added on purpose.

Roles

Who may ask, and which answers may leave the building. Internal Q&A and customer-facing language are not the same job.

Refusal rules

Pricing exceptions, legal interpretation, and anything missing from the source set route to a person. Helpfulness is not a reason to guess.

Cite it, or hand it off

Bounded onboarding

Before it answers, we define the source set, the roles that may ask, and the questions it must refuse. It does not browse the open web or invent policy.

Source references

Each answer points back to the playbook, policy, or SOP section it used. If a citation cannot be attached, the answer is not shipped.

Handoff when unknown

Missing, conflicting, or customer-facing judgment calls route to a named owner. The assistant does not guess to stay helpful.

Operator constraints

Not an unsupervised customer chatbot.

Not a claim that we trained on your entire company drive.

Not a security certification or pentest report.

Not a case study with invented time saved.