System memory

When an event is scheduled and a contact is added who is not on the update type's default list, the system records it. The next time an event is scheduled for that same system, the wizard offers that person again.

That is the whole mechanism. There is no form anyone has to fill in to make it work.

Two kinds of entry

Kind	Who creates it	What it holds
Contact	Saved by itself when an event is created	Name, email, phone, and when it was saved
Note	Written by hand on this screen	Free text shown beside the system

An entry nobody created by hand carries the label "Saved automatically". Each contact entry counts how many times it has been used and when it was last used — so an entry saved once and never chosen again is distinguishable from one chosen for every window.

Where it resurfaces

In the contacts step of the scheduling wizard, when the selected systems have any memory, a "System memory" block appears above the contact picker. Each row says when the addition was requested and who, with a single Add button. A contact already selected is marked as added and cannot be added twice. Notes appear in the same block in a separate shade, so they are not read as a contact you could add.

The block can be dismissed. It is an offer, not a step.

The screen

The screen groups entries by system, with a count per group. You can search by system name, contact or note text, add an entry by hand, edit an existing note, and delete — deletion takes a second click to confirm.

Two screens with similar names

Settings also has a "Memory scenarios" screen, and it is not this one.

	System memory	Memory scenarios
What is remembered	Contacts and notes, per system	A fault that work on one system caused on another
Who fills it in	Saves itself, or an administrator	An operator, on a form
Where it comes back	The scheduling wizard	The activity planning board

Memory scenarios is a form builder: it defines the questions an operator answers when recording a causal link like that. Two questions of the "system" kind are mandatory in every scenario, and the first is always the source system and the second the target — the order carries the meaning, the builder marks it on the cards, and it warns when a drag swaps the two.