Agents normally solve requests before a later close rule closes them. A solved ticket can receive a requester reply and reopen. A closed ticket cannot reopen; its reply creates a follow-up with a new identity and only a supported subset of inherited fields. Current product configurations can permit authorized edits to selected closed fields. Keep that permission exception separate from status and conversation restrictions. These exercises disclose the local account setting.
Use the supplied training clock rather than waiting in real time. Inspect an eligible ticket and a nearby exclusion after advancing the scheduler. Later requests remove the worked sequence and change the threshold. The result needs both the intended saved effect and evidence that an unsafe repeat is prevented.
Worked example: solved and closed boundaries.