video1.0<iframe src="https://www.loom.com/embed/474789266db04f52941b7b6635e3972e" frameborder="0" width="1646" height="1234" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>12341646Loomhttps://www.loom.com12341646https://cdn.loom.com/sessions/thumbnails/474789266db04f52941b7b6635e3972e-f2da2080e627ff91.gif438.571This Loom explains how to create a custom attribute to filter Freshdesk tickets by who last modified them. It recommends storing the information in one of three ways: a dropdown field LastModifiedBy that is indexed for filtering, a persistent text field LastModifiedByText set via workflow so reporting remains accurate even if the user profile is deleted, or using tags with the user email for filtering multiple people. The speaker demonstrates a workflow triggered on ticket updates, replies or forwards, and certain note types, which sets LastModifiedByUser and LastModifiedByText and adds a tag with the event performer email. They also warn that triggering on every ticket update can become expensive due to API calls.