Ask about your operation and get an answer from your operation, not from the internet.
The conversational surface for operators — grounded in your live operational context.
The problem
What goes wrong without it
General-purpose assistants answer from general knowledge. In an operational setting that is worse than no answer, because a confident wrong answer about your site is acted on.
ChatVRTK is grounded in live operational context — your sites, incidents and personnel — and runs under the execution controls AI Intel enforces. Where it cannot ground an answer, it says so rather than inventing one.
Capabilities
What ChatVRTK does
Described from the current product build. Availability can depend on your deployment and plan.
- Answers grounded in live operational context
- Explicit operating modes rather than one opaque assistant
- Actions bounded by a defined tool authorisation model
- Available alongside the operating surface, not in a separate product
- Voice input where the operator's hands are occupied
Operational workflow
How it is used
These are ordered stages of real use, not a feature list rearranged.
- 01Ask
An operator asks in plain language, by text or voice.
- 02Ground
The question is answered against live tenant context.
- 03Bound
Any action is checked against the tool authorisation model.
- 04Answer
The response cites what it was grounded in.
Operating it
Integration, security and deployment
Integrations
- AI providers configured per organisation
- The operational data model as grounding context
Security & permissions
Grounding is tenant-scoped: the context assembled for a question contains only what that user could already see. Actions are separated from answers and gated by risk class, so a conversational surface cannot become an unaudited command channel.
Security modelDeployment
- Requires an AI provider to be configured for the organisation
- Grounding quality depends on how complete the operational data is
Documentation
Where the detail lives
Documentation for this module is being prepared against the product. It is not published yet.
We publish documentation only once it has been checked against the product, rather than listing procedures nobody has run. The documentation home shows what is written, in review or planned.
Documentation homeRelated
Modules that share this model
These read from the same sites, personnel and incidents.
See ChatVRTK against your own sites
A working session using your operational context rather than a scripted tour. If your operation fits a plan available online, we will say so rather than route you through a sales process.