Macros
A macro is a saved reply that also carries conversation changes. It lives in the same library as canned responses — in Helpin, a shortcut can be text, actions, or both — so when you use it, the customer gets the message and the conversation gets updated in one step.
One library, two kinds of shortcut
Both live in the shortcuts panel. Use ! in the composer to open it:
A canned response inserts saved text and nothing else.
A macro carries actions. It can also carry text, in which case the actions run after the reply is sent.
So there is no separate "macros" menu. If your team says "apply a macro", they mean use a shortcut that has actions on it.
Creating a macro
Open the shortcuts panel, choose Add, and fill in the shortcut form. Below the message field there is an Actions (optional) section. The help text there states the rule plainly: these run when the shortcut is used — right away if it has no message, otherwise after the reply is sent.
The Message field becomes optional once the shortcut has actions. A shortcut with actions and no message is a pure macro: typing the code changes the conversation without sending anything to the customer.
The actions a macro can carry
Status — Reopen, Waiting on customer, or Resolve.
Priority — Urgent, High, Medium, or Low.
Assignee — a teammate, or Unassign.
Move to inbox — another inbox, or the main inbox.
Tags — add and remove.
Snooze — 1 hour, 4 hours, 1 day, 3 days, or 1 week.
Each field defaults to No change, so a macro only touches what you configure. Two interactions worth knowing: choosing Resolve clears any snooze you set, and Snooze offers only those five fixed durations — a macro cannot pick an arbitrary date.
Using one
Type ! in the composer and select the shortcut.
With a message — the text is inserted into your draft, and you still edit and send it yourself. The actions fire after the send, so you are never in the dark about what happened to the conversation.
Without a message — the actions run immediately when you use it.
Before you rely on a macro, read the plain-language summary the editor shows for its actions (for example "move to Billing, assign to Priya, add tag escalated"). That summary is generated from the actions themselves, so it always matches what will happen.
Permissions and limits
Using a shortcut needs support read access. Creating, editing, and deleting shortcuts — including macros — needs support admin. Because a macro changes a conversation, treat it with the care you would treat a bulk action: it is the same kind of change, without a confirmation step.
Macros worth building
Escalate — priority Urgent, assign the on-call lead, add tag escalated, with a short message saying you have escalated it.
Hand to billing — move to the Billing inbox, assign, add tag billing.
Close as duplicate — Resolve, add tag duplicate.
Snooze to tomorrow — Snooze 1 day, status Waiting on customer.
Related pages
Was this article helpful?