Two requests can share a subject without sharing a customer, organization or history. Use the ticket ID to identify the record, then read its requester and organization before changing anything. A ticket view is a way to find work; it does not establish that the first matching row is the intended case. Duplicate subjects are deliberate in these exercises.
Work on the exact saved record. The first task shows the action sequence; later requests remove those directions and introduce a nearby record that looks plausible. After an update, inspect the saved ticket rather than relying on a filled form. The conversation and customer context must stay attached to the original identity.
Worked example: ticket identity.