A decision you can check against the cases it came from.
Step 1 of 4: The decision
The examples behind a decision.
Ask why, and Duplex shows the confirmed examples behind a decision.
Status and explanations. It runs On request, read-only.
A reason your reviewer can check.
When a decision surprises someone, they can see the confirmed cases behind it and judge those cases for themselves.
Step 1 of 3: Asked why
A manager asks why a £180 night was approved.
See why, then put it right.
When a case behind a decision is out of date, a reviewer corrects that one case, and the next decision rests on the corrected cases.
Step 1 of 5: Decided
Duplex approves a £210 hotel night in London.
Asking why changes nothing.
Seeing the reasons is read-only. Duplex shows the cases, who confirmed them and when, and only to people allowed to see them.
Step 1 of 4: Read-only
Asking leaves every decision, rule and lesson as it was.
Decides whether to answer, hand over or decline.
For every request, Duplex answers from what it learned, hands the work to your model or a tool, or declines, and can show why.
- Every request: answer, hand over or declineKnown work is answered at once, new work goes to your AI, and work that breaks a rule stops.
- The examples behind a decisionAsk why, and Duplex shows the confirmed examples behind a decision.
- Every handed-over step, closed onceEach step runs exactly once and none is lost, so a payment or a deployment never happens twice.
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.