A lesson made answers worse. Take it back, and the good answers return.
Step 1 of 5: All good
A wrong change is taken back.
A lesson that made answers worse can be reversed, and the answers that worked before come back.
Forgetting and data control. It runs On an authorised request.
Only someone authorised can take a change back.
Taking a change back is a decision your team makes, and it is recorded like every other change.
Step 1 of 5: Authorised
The request comes from someone allowed to make it.
The answers that worked come back.
Taking a change back returns Duplex to how it answered before that change, not to a blank start.
Step 1 of 3: A bad lesson
A bad lesson gets in.
Every change, on the record.
You can see when a change was learned, what it changed and when it was taken back.
Step 1 of 4: Learned
The record shows when the lesson was learned, and from what.
Learns and unlearns.
Duplex learns from each confirmed result straight away, and any single lesson can be taken back while the rest stays.
- It learns from every confirmed resultConfirm a result once, and the next request already benefits, with no retraining and no re-prompting.
- A correction changes the next answerYour team stops repeating the same correction: once accepted, it shapes every similar answer after it.
- A wrong change is taken backA lesson that made answers worse can be reversed, and the answers that worked before come back.
- One lesson removed, the rest keptRemove one outdated or unwanted lesson and keep everything else, with nothing to retrain.
- It learns what each action doesPlans grow more reliable over time, because Duplex learns what each action changed.
- A wrong observation is removedRemove an observation that turned out wrong, and every plan built on it is checked again.
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.