Undo
Undo is taking back the last change made to a record, so that a mistake costs one sentence rather than a lost day. IZeat undoes the last change in two steps, a preview then a confirmation, and undoes only that change: a corrected item goes back to what it was, an added item goes out, and the rest of the meal stays as it is.
There is no screen where a customer could repair a mistake, so undo has to exist in the conversation. The first call previews what would happen, item by item, and changes nothing; the second, after the customer says yes, applies it within ten minutes. Only a change made in the last forty-eight hours can be undone, and at most ten confirmed undos an hour. A restore reverses an undo the same way. Every change stays in the history; nothing is erased.
Undo is what makes correction safe to attempt. A person who knows the last change can be taken back in one sentence corrects freely; a person who fears making things worse leaves the error in, and the record rots from there. Because IZeat previews before it acts, the customer sees the item-by-item consequence, and because undo works on the last change only, it never unwinds a day's worth of work to fix one line.
Put it into practice: Undo and restore.
Updated