A macro is a prepared set of ticket changes that an agent applies manually. Applying it fills draft fields or the composer. You can inspect and edit that draft before submitting. The saved ticket does not prove the macro worked until Submit persists the update. In this workspace, macro output is local training data; it does not contact a requester or a connected service. Read both the fields and comment audience.
Use the named ticket and inspect its stored state after each operation. These tasks move from a guided update to a fresh transfer request. The local model has On-hold enabled and performs no external delivery. A saved field, public comment and follow-up identity each provide different evidence of completion.
Worked example: macro drafts and submit.