A £95 call-out charge, traced to its method, its tests and its record.
Step 1 of 4: What it does
One method, with its tests and history.
Any method can be inspected, down to its tests and its track record.
Reusable skills. It runs Read-only.
A customer’s query, answered from the method itself.
When a customer asks why a visit cost £95, your team opens the method and finds the answer in its tests, in its record or with its owner.
Step 1 of 3: Why £95?
Why £95 on a Saturday? A known case in its tests shows exactly that charge.
Its whole history, from the day it was written.
Every change to the method is dated, with what changed and what it passed before it was used again.
Step 1 of 5: Written
In March, Duplex writes the method and tests it on past call-outs.
Its tests are written in your own terms.
Each test is a case your team would recognise: a visit, a distance, a time of day and the charge it must come to.
Step 1 of 4: A weekday
A weekday visit, 5 miles away, must come to £60.
Writes and tests small programs.
For a well-defined task, Duplex writes a small program, tests it against known cases and uses it only once it passes.
- A small program, proven on known casesRepetitive, well-defined work is done by a tested program, at almost no cost per run.
- Your model helps once, Duplex checks itFor a hard case your model is asked once, and the proven result is reused from then on.
- A solved problem, answered from its solutionA problem solved once is never paid for again.
- Trust in a program follows its resultsReal-world results raise or lower trust in each program.
- Every proven method, by status and ownerYour team sees every method Duplex relies on, who owns it and where it applies.
- One method, with its tests and historyAny method can be inspected, down to its tests and its track record.
- The reusable parts behind its programsThe building blocks that keep recurring are visible, so your team knows what new work stands on.
- The checks behind a programBefore your team relies on a program, it can see the tests it passed.
- A proven method becomes the preferred oneThe method with the best record is the one used by default.
- A doubtful method, paused straight awayA method that might be unsafe stops being used straight away.
- A fixed method returns to useOnce the cause is fixed and it passes again, a method returns to use.
- A wrong method, withdrawn for goodA method found to be wrong is withdrawn, and never comes back into use.
- A program erased when the law requires itA program and its data are erased when the law or the owner requires it.
- A flawed part, withdrawn everywhere it was usedA flawed building block is withdrawn, along with every method that used it.
- The parts that keep coming backWhat recurs across proven programs becomes a shared part, so new programs start further ahead.
- Every new method tested before useA method reaches your work only once it has passed its tests, whether it is new or changed.
- A new area starts from proven methodsA new work area can start from a library of proven methods, each re-checked locally.
- What its programs solve and saveYour team can see how much work programs take off your AI, and what that saves.
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.