Approved sources only
An assistant answers from the material you approve for it. Where a question falls outside that material, the designed behaviour is to say so and hand over, not to improvise.
Every workflow we build has defined points where a person decides. This page explains the controls we use and what they do not guarantee.
An assistant answers from the material you approve for it. Where a question falls outside that material, the designed behaviour is to say so and hand over, not to improvise.
Where the underlying tooling produces a confidence score, we agree a threshold with you. Below it, the item is routed to a person instead of being actioned automatically.
You decide which outputs a person must approve before they leave the organisation or change a record. Those points are written into the design and tested during acceptance.
Cases the workflow is not designed to handle — unusual documents, sensitive requests, missing data — are sent to a named queue rather than forced through.
Access to review queues and configuration follows the roles you define. Reviewer responsibilities are covered at handover and in training.
Workflows are configured to record what was processed and what a reviewer decided, to the extent the platforms in scope support it. What is recorded is confirmed in the scope.
The sequence below is an illustration of a designed workflow, not a recording of a client system.