Macro drafts and submission
A macro is a prepared response or action that an agent applies manually. Zendesk’s macro documentation separates applying the actions from submitting the ticket. Review the composer and ticket fields between those steps.
In an original fictional case, ticket LC-41 needs a reference number. An approved macro adds reference_requested, prepares a public request and sets Pending. Applying it changes the draft. Until Submit, you cannot use the saved ticket or comment history as evidence that the work is complete.
Overlapping macro actions
Suppose another macro sets Open after the first sets Pending. Inspect the final draft rather than assuming the first value is locked. Manual edits can also replace prepared actions. Check the requester, public/internal audience and source reference before saving.
After Submit, read back the status, tag and saved comment together. A tag alone does not prove that a reply was saved. A local public comment also does not establish email delivery.
Practice tasks
Apply the approved response, replace one field deliberately, then identify which draft value will be persisted. In the Zendesk course, the original local workspace lets you check these distinctions without contacting a customer. Use triggers and automations when a later rule appears to undo the saved result.