Macro

5 min read

Also known as: Canned action, Quick action, Ticket shortcut

A macro is a saved set of pre-built ticket actions support agents trigger with one click to reply, update fields, and route in seconds.

Definition

A macro is a reusable bundle of ticket actions your support agents can apply with one click. It typically combines a canned reply, status changes, tag updates, priority shifts, and sometimes assignment changes into a single named shortcut.

Agents use macros to handle high-volume, repetitive ticket types — shipping questions, password resets, refund acknowledgments — without retyping the same response or clicking through five separate fields. The macro fires the reply, sets the ticket to pending, adds the right tag, and routes to the correct queue in one motion.

Macros differ from automations and triggers: a macro is agent-initiated (a human picks it), while triggers and automations fire based on conditions the system evaluates. Macros also differ from plain canned responses, which only insert text — a macro can modify the entire ticket record.

Why It Matters

Macros directly lower handle time and raise consistency. A support team running well-tuned macros can cut average response time on repetitive tickets by half or more, freeing agents to spend real attention on the cases that actually need judgment. They also normalize tone and messaging, which matters when ten agents are answering the same refund question every day.

Without macros, your team retypes the same paragraph hundreds of times a week, introduces inconsistent phrasing, forgets to set tags, and creates messy reporting downstream. Quality dips on routine work and burns the hours you needed for escalations, which is when CSAT and SLA breaches start stacking up.

Examples in Practice

A SaaS support team builds a 'Password Reset Sent' macro that inserts the reset instructions, marks the ticket as pending, applies the 'account-access' tag, and sets priority to low. Agents resolve these in under 30 seconds instead of three minutes.

An ecommerce brand creates a 'Shipping Delay – Carrier Issue' macro that pulls a templated apology, adds a courtesy discount code variable, tags the ticket for the weekly carrier review report, and assigns it to the logistics queue. Tier 1 agents handle it without escalation.

A B2B services firm builds a 'Renewal Question – Route to AM' macro that sends a brief holding reply, reassigns the ticket to the account manager, and notifies them in Slack. It keeps renewal conversations out of the support backlog and in the hands of the relationship owner.

Frequently Asked Questions

What is a macro and why does it matter?

A macro is a one-click bundle of ticket actions — a reply, status change, tags, assignment — that agents apply to repetitive cases. It matters because the bulk of support volume is predictable, and macros let your team move through that volume fast and consistently while reserving attention for the tickets that need real problem-solving.

How is a macro different from an automation or trigger?

A macro is agent-initiated: a human reviews the ticket and chooses to apply it. Triggers and automations fire automatically based on system conditions (ticket age, status, keyword match). Use macros when judgment is required before action, and use triggers when the action should happen with no human in the loop.

How is a macro different from a canned response?

A canned response only inserts text into the reply field. A macro inserts the reply and modifies the ticket record itself — status, tags, priority, assignee, custom fields. Think of canned responses as a subset of what a full macro can do.

When should I build a new macro?

Build a macro when you spot a ticket type appearing more than ten or fifteen times a week with a predictable resolution. If agents are copying and pasting the same response, or repeatedly setting the same combination of fields, that's a macro waiting to happen. Below that volume, the upkeep cost outweighs the savings.

What metrics measure macro effectiveness?

Track macro usage rate per agent, average handle time on tickets where the macro was applied versus not, first-contact resolution on macro-tagged tickets, and CSAT on macro replies. Also watch for macros with low usage — those signal templates that are stale, hard to find, or no longer relevant and should be retired.

What's the typical cost of using macros?

Macros are a standard feature in nearly every helpdesk platform, so there's no incremental license cost. The real cost is build and maintenance time — expect roughly 15 to 30 minutes to design and test a strong macro, plus quarterly review cycles. A library of 40 to 80 well-maintained macros covers most mid-market support operations.

What tools handle macros?

Most modern helpdesk and ticketing platforms include macro functionality — CRMs with built-in support modules, dedicated customer service platforms, and shared inbox tools all offer some version of it. The depth varies: some only support text templates, others allow full ticket-field manipulation and conditional logic.

How do I implement macros for a small team?

Start by pulling your last 90 days of tickets and grouping them by topic. Identify the top 10 ticket types and build one macro for each. Train agents on naming conventions and keyboard shortcuts. Review usage monthly for the first quarter, then quarterly. A five-agent team can usually go live with a solid macro library in a week.

What's the biggest mistake teams make with macros?

Building too many and never pruning. Macro libraries balloon to hundreds of entries, agents can't find what they need, and they fall back to typing from scratch — defeating the purpose. The fix is ruthless maintenance: archive any macro used fewer than five times a month and keep names short and searchable.

Can macros hurt customer experience?

Yes, when overused or poorly written. Customers spot templated replies that don't address their actual question, which erodes trust fast. Good macros include personalization variables (name, order number, specific issue) and leave room for the agent to add a sentence of context. Macros should accelerate human responses, not replace them.

The AMW Suite