Sessions and incidents, learned as episodes.
Duplex learns each session, run or incident as an episode your team can ask about later.
Persistent intelligence. It runs After a job step or when a job closes.
One episode covers the whole incident.
The alert, the steps taken, who took them and how it ended stay together, so anyone can follow what happened.
What happened: checkout failed for 39 minutes.
Each closed incident informs the next one.
When a session, a run or an incident closes, Duplex turns it into an episode. The next time something similar happens, the team can ask what happened then.
The checkout fails on a Saturday afternoon.
Every episode follows your rules.
Episodes stay in their work area, follow your retention rules and can be removed. Your access settings decide who can ask about them.
It stays in the work area where it happened.
Brings the right history to each step.
Past experience, documents and earlier sessions come into the current step, each labelled by its source.
- Finished work becomes experienceWhat a finished task taught is ready for the next one, within your privacy rules.
- Past experience, brought into the stepA new task starts with what your team learned last time, labelled as past experience.
- Approved documents, with source and versionApproved documents become searchable, each with its source and version.
- The passages a task needsEach step gets the few passages it needs, each one linked to where it came from.
- Context sized to fit, citations keptYour model reads what it needs and nothing more, with every source still cited.
- Sessions and incidents, learned as episodesDuplex learns each session, run or incident as an episode your team can ask about later.
- What happened last time, with citationsAsk what happened last time, and Duplex answers from the episodes it learned, with citations.
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.