Payday happens once, even when the connection drops.
Step 1 of 4: Handed over
Every handed-over step, closed once.
Each step runs exactly once and none is lost, so a payment or a deployment never happens twice.
Confidence and autonomy. It runs After every handed-over step.
A step runs once, even when retried, and stays in view until its reply comes.
In a working day, steps get retried, clicked twice or left waiting. Duplex sends each step to your tool once, and any step still waiting stays in view.
Step 1 of 4: First time
The first request to pay a supplier £4,200 goes to your payment tool.
What has to be true before a step is closed.
A handed-over step is closed once, when its result arrives. A repeat does not run again, and a step that is still waiting stays open.
Step 1 of 5: Not twice
A second request for the same release is spotted, and not run again.
A week of handed-over steps, none twice, none lost.
Over a week, every step Duplex handed over was closed once. One waited a day for its result, and stayed in view until it came.
Step 1 of 5: Monday
Monday: a stock reorder is handed over and closed once.
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.