A strike-week adjustment, rolled back once the strike was over.
Step 1 of 4: Usual days
An adjustment undone if it does not hold.
A change that does not hold up can be rolled back, and the answers that worked return.
Operational intelligence. It runs On an authorised request. In the Agent Operating System, it is the Runtime Intelligence that powers it all: learning from the work.
The Monday after the strike, the next answer is right.
Once the strike is over, the adjustment it needed gets in the way. Rolling it back takes one authorised request, and the next answer is right.
Step 1 of 4: The strike
A strike week changes what the right answer is.
The rollback undoes one adjustment and leaves the rest.
Rolling back the strike adjustment leaves the rest of that week’s learning in place, like the new form for delay compensation.
Step 1 of 3: Strike week
In strike week, MS Duplex learns two things: trains are cancelled, and there is a new compensation form.
A rollback is your team’s call, and it is recorded.
Only someone authorised can roll an adjustment back. It names the adjustment, leaves everything else in place and goes on the record.
Step 1 of 5: Authorised
The request comes from the travel desk lead, who has the right to make it.
Stays fast and sound as it grows.
MS Duplex makes room as the work grows, stays fast as it learns, and checks itself before it answers.
- Room to grow when the work doesNew kinds of work never hit a ceiling, and everything MS Duplex already knows goes on working.
- Growth undone if it made things worseGrowth never has to cost accuracy: if it made answers worse, it can be undone.
- Keeps up as the work slowly shiftsWhen customers start asking things a little differently over months, answers stay right without retraining.
- An adjustment undone if it does not holdA change that does not hold up can be rolled back, and the answers that worked return.
- Stays compact and fast as it growsAnswers stay as fast months in as on the first day, however much MS Duplex has learned.
- A restore point before every risky changeAny risky change can be undone, back to the moment before it.
- Checked before it answersMS Duplex checks itself after every major change, so a damaged or half-finished update never reaches your team.
See it on your own work.
From your own assistant to every agent your company runs, a pilot puts MS Duplex on your own work, with the measures agreed before it begins.