The field didn't change
How you'll know: The reply went in, but the status or a custom field stayed the same.
Fix: The field isn't on that ticket's form, or the agent's role can't make that change. Add the field to the form or adjust the role.
A macro is a saved set of changes an agent applies with one click: a reply, a status, tags, a group. It only runs when someone chooses it. Triggers and automations run on their own. Here's how to make a macro, the placeholders that personalize it, and how to tell which of the three a job belongs to.
Create: as an admin, open Admin Center and choose Create macro. Agents can make personal macros that only they see.
Admin Center › Workspaces › Agent tools › MacrosApply: click Apply macro in the ticket's bottom toolbar and pick one, or type / in the comment box in the Agent Workspace and start typing its name.
Check first: hover over a macro and press Shift + Enter to preview the reply and field changes before applying.
Agents find macros by typing, so lead with the topic: "Refund: approved", "Refund: outside window". Add a description saying when to use it.
Add the comment action and use placeholders such as {{ticket.requester.first_name}}, {{ticket.id}} and {{current_user.first_name}}. A custom field appears as {{ticket.ticket_field_ followed by its ID and }}.
Set the status, add tags, assign a group, change priority. These are what make a macro faster than a saved reply.
Watch for: a macro can only change a field that's on the ticket's form. If the form hides it, the change silently doesn't happen.
Use Available for to share it with everyone or only certain groups, so billing macros don't clutter the technical team's list.
How you'll know: The reply went in, but the status or a custom field stayed the same.
Fix: The field isn't on that ticket's form, or the agent's role can't make that change. Add the field to the form or adjust the role.
How you'll know: An agent applied "Escalate" then "Waiting on customer", and the ticket ended up in neither state.
Fix: Macros apply in order and the last one wins on any field they share. Make macros that shouldn't be combined set the same fields consistently.
How you'll know: The tag the macro added has gone by the time the ticket saves.
Fix: A trigger fired on the update and removed or swapped it. The ticket's events log shows which one.
How you'll know: On a problem ticket, the reply greets the wrong requester when it copies to linked incidents.
Fix: Escape the placeholder with a backslash, as in \{{ticket.requester.first_name}}, so it fills per ticket.
How you'll know: The macro says "your tracking number is" and the agent looks it up and pastes it in.
Fix: Placeholders can only quote what Zendesk holds. Put the number in a ticket field, and the macro can quote that field.
An online retailer running refund requests through Zendesk
Tagging a ticket as a refund sent a webhook to the order system, but the trigger couldn't use the reply.
An agent still opened the order system to see whether the refund was allowed, then picked a macro.
n-frames built the receiving end: it checks the order, decides approve or needs review, and writes that decision onto the ticket through the Zendesk API.
By the time an agent opens the ticket, the decision is there and the matching macro is the obvious next click.
A saved bundle of ticket changes, such as a reply, a status, tags and an assignee, that an agent applies in one click. Unlike triggers and automations, a macro never runs by itself.
A trigger fires immediately whenever a ticket is created or updated and meets its conditions. An automation runs on an hourly check and acts on tickets that have been in a state for a certain time, such as pending for three days.
In Admin Center, open Workspaces, then Agent tools, then Views, and add a view with conditions such as status, group or tags, plus the columns and sort order agents should see. Views only organize tickets; they never change them.
Yes, by notifying a webhook. It sends the data and moves on, so it can't wait for an answer and branch on it. Anything that needs the reply, like the refund check above, needs a service on the receiving end that writes back through the API.
A ticket form decides which fields appear for a type of request, for example billing versus technical support. Macros also depend on them, because a macro can only change fields that are on the ticket's form.
Yes. Select tickets in a view and apply the macro as a bulk update. Check it on one ticket first, because the reply goes to every requester.
Only if they're already on the ticket. Placeholders read Zendesk fields, not your store. n-frames fills custom ticket fields with the order number, status and tracking link from your order system as tickets arrive, so the macro quotes them.