Your security team sees each change in its own tools, as it happens.
Step 1 of 4: A request
The history, event by event, for your tools.
The history flows into your own monitoring and audit tools as it happens.
Status and explanations. It runs Read-only.
Your existing alerts cover Duplex too.
The history arrives where your team already watches, so a declined action or a new release shows up beside everything else you monitor.
Step 1 of 3: A decline
At 14:02, an agent’s bulk delete is declined.
Event by event, through the working day.
Lessons learned, skills withdrawn, actions declined and releases made each reach your tools as they happen.
Step 1 of 4: A lesson
09:12: a correction to holiday-pay answers is learned, and the event reaches your tools.
Your team chooses where the history goes.
The history is your organisation’s alone, and the tools you pick receive the same history your team sees in the console.
Step 1 of 4: Your tools
It flows to the tools your team chooses.
Shows a history you can check.
Every change Duplex makes can be traced and checked, and exported to your own tools.
- Every change, traceable and checkableAn auditor can follow any change from its cause to its result.
- The history, event by event, for your toolsThe history flows into your own monitoring and audit tools as it happens.
- The checks behind every changeEvery release, reversal and new skill comes with the checks it passed.
See it on your own work.
From your own assistant to every agent your company runs, a pilot puts Duplex on your own work, with the measures agreed before it begins.