How to Use Macros and Canned Responses to Speed Up Support
Every support team has them: the questions that come up five times a day, every day. How do I reset my password? What are your hours? Can I get a refund? Can I change my billing?
You know the answers. Your team knows the answers. But without a system, agents type them out over and over, slightly differently each time, and your team's day evaporates into repetition.
That's where macros and canned responses come in. They're pre-written answers that agents can insert with a click or a keyboard shortcut. Done well, they don't make support feel robotic — they just free your agents to spend their time on things that actually need thinking.
What are macros and canned responses?
The terms get used interchangeably, but there's a useful distinction.
Canned responses are snippets of text that agents insert into a reply. They fill in the message body but don't touch anything else about the ticket. Think of them as message templates.
Macros are broader. A single macro can insert a canned response and perform ticket actions at the same time: change the status, add a tag, move it to a queue, add internal notes. One click, multiple things happen.
In practice, most modern helpdesks combine both concepts. When people say "macros," they usually mean a saved action that includes text, status changes, tags, and field updates — the whole package.
Why this matters: time and consistency
The numbers here are straightforward.
If one agent handles 40 tickets a day and 15 of them can be fully or partially answered with a macro, even a two-minute time saving per macro adds up to 30 minutes a day. That's roughly 10 hours a month per agent. Scale that across a five-person team, and you're looking at 50 hours of reclaimed time monthly — time that goes toward complex cases, not repetition.
More importantly: consistency. When every agent writes their own refund-policy explanation, customers get slightly different information depending on who they reach. A macro ensures the same question always gets the same accurate answer. No typos, no forgotten steps, no "did I mention the 3-to-5 business day timeline?"
For new hires, a curated macro library is gold. Instead of memorising everything, they can start handling common queries almost immediately — using macros as a reference while they build expertise. And when you're setting up SLAs or running quality assurance reviews, consistency becomes measurable.
Building a macro library that works
A macro library is only as useful as its organisation. A chaotic collection of 200 macros that nobody can find is barely better than having none.
Start with your most common tickets
Pull a report of your ticket categories over the last 30 to 90 days. Identify your top 20. These are your starting point.
For most teams, the top 20 categories will cover 60 to 80 percent of total ticket volume. That means a relatively small, focused library has enormous impact. You don't need to solve everything.
Organise into categories
Billing, account management, technical issues, shipping, returns, onboarding. Agents should find the right macro in seconds — either browsing categories or typing a search term. A 200-macro library is useless if it takes three minutes to locate the password-reset macro.
Use personalisation variables
A macro should never read like a form letter. Include placeholders that pull in the customer's name, account details, or the specific product they're asking about. Most helpdesks support dynamic variables: {{customer.first_name}}, {{ticket.subject}}, {{order.id}}.
A macro that opens with "Hi {{customer.first_name}}" and references their specific issue feels personal, even though the bulk of the text is pre-written.
Write like a human
Your macros should sound like your team. If you're conversational and friendly, your macros should be too. Avoid overly formal language unless your industry demands it.
Read each macro aloud before saving it. If it sounds like a legal department wrote it, rewrite it. The UK government's Service Manual guidance on writing for users is a good benchmark for plain language.
Make macros action-oriented
The best macros don't just answer a question — they guide the customer toward the next step. Instead of "Your refund has been processed," say: "Your refund of £{{amount}} has been processed and should appear in your account within 3 to 5 business days. If you don't see it after that, just reply and we'll investigate."
Every macro should tell the customer exactly what happens next.
Macro best practices
Keep them short. Customers don't want a five-paragraph essay. Aim for three to five sentences for straightforward questions. Two or three short paragraphs for complex topics, and that's the ceiling.
Review and update quarterly. Products change. Policies change. A macro that was accurate six months ago might be misleading today. Assign someone ownership so it doesn't become "we'll update these eventually."
Track usage and refine. Most helpdesks show which macros get used constantly and which have never been touched. Use that data. High-usage macros deserve extra polish. Unused ones should be reviewed — either they're hard to find, they address a problem that no longer exists, or the naming is confusing.
Let agents customise before sending. A macro is a starting point, not a straitjacket. Customers' situations often have nuances the standard response doesn't cover. Agents need the freedom to edit. You save time without sacrificing empathy.
Create macros for internal work too. You can build macros for escalating to specialists, flagging tickets for follow-up, adding investigation steps in internal notes, or moving tickets between queues. Automate the internal routine and agents have more space to focus on the customer-facing work.
Examples you can steal
Password reset
Hi {{customer.first_name}},
You can reset your password by clicking "Forgot password" on the login page. We'll send a reset link to your email address.
If you don't get it within a few minutes, check your spam folder. If it's still not there, let us know and we'll sort it out.
Actions: Set status to pending, add tag "password-reset"
Refund confirmation
Hi {{customer.first_name}},
Your refund of {{amount}} has been processed. You should see it in your account within 3 to 5 business days depending on your bank.
Any other questions, just reply.
Actions: Set status to solved, add tag "refund-processed"
Feature request
Hi {{customer.first_name}},
Thanks for the suggestion. I've logged this with our product team. I can't promise a timeline, but feedback like yours directly influences what we build next.
We'll let you know if it makes a future release.
Actions: Set status to solved, add tag "feature-request"
When you're handling common requests like refunds and returns, consider pairing macros with approval workflows so tickets route to the right person automatically.
Going further: advanced techniques
Some helpdesk platforms support conditional macros — macros that behave differently based on ticket properties. A billing macro might include different text depending on whether the customer's on a free plan or paid plan. Fewer similar macros, cleaner library.
Multi-step macros can trigger a sequence: insert a closing message, set the ticket to solved, and trigger a satisfaction survey — all in one click. When you're implementing workflow automation, these compound actions save real time.
There's also a useful distinction: shared macros (available to the whole team) and personal macros (created by individual agents for their own workflows). Keep a curated shared library as your primary resource, but let agents build personal ones for their common patterns.
Measuring what actually changed
After you've built a macro library, track these:
- Average handle time — Should drop as agents spend less time typing
- First response time — Should improve on high-volume questions
- Consistency in QA reviews — Response quality should become more uniform across the team
- Agent satisfaction — People prefer interesting problems to repetitive typing
You can measure these directly in your helpdesk's analytics or pull them from custom reports and dashboards.
The balance between speed and empathy
The common worry: macros make support feel impersonal. It's a valid concern, but it's a problem of execution, not the concept itself.
A well-designed macro with personalisation, human tone, and room for agent customisation feels no different from a typed response to the customer. The agent saves time, the customer experience stays the same (or improves because the answer is accurate and arrives faster). Win-win.
The real benefit is freeing agents to focus where it matters: the complex, emotionally charged, or unusual situations that need genuine human judgment. The routine questions get handled efficiently, and the difficult ones get the attention they deserve.
Frequently Asked Questions
How many macros should we create? Start with macros for your top 20 ticket categories. That covers 60–80% of volume and keeps the library manageable. Add more as you identify patterns, but maintain quality over quantity. A 30-macro library that's well-organised and regularly used beats a 200-macro graveyard.
What if a macro doesn't fit the situation perfectly? That's why agents should always be able to customise before sending. A macro saves time on the 80% of cases where it applies directly. The 20% where the customer's situation is unusual? Agents edit it. You've still saved time overall, and the customer gets a thoughtful response.
Should we let individual agents create their own macros? Yes, but with structure. Personal macros are fine for individual workflows. But maintain a curated shared library that the whole team uses. That's where consistency happens. You might review popular personal macros and move them to shared if they'd help the whole team.
How often should we update our macros? At minimum, quarterly. Set a calendar reminder and assign ownership to someone. Products change, policies change, pricing changes — a macro that was accurate six months ago might be misleading now. Stale macros erode trust faster than no macros at all.
Can macros work for complex technical questions? For the initial response, sometimes. A macro might say "Thanks for reporting this. Let me escalate to our technical team — you'll hear back within 4 hours." That still saves time. But the actual troubleshooting usually needs to be written fresh. Use macros where they genuinely apply.
What if agents resist using macros? Usually it's because the macros are hard to find, poorly named, or don't match how the agent thinks. Involve agents in building the library. Ask them what questions they get asked most. Let them name macros in ways that make sense to them. Adoption jumps when agents feel ownership.
How do we ensure macros don't make us sound robotic? Voice matters. Write your macros the way your team actually talks. Include personalisation variables. Let agents customise. A professional tone that's also human is possible — it just requires thinking past "insert template, send." Treat macros as a tool that frees agents to be more thoughtful, not less.
What's the difference between macros and chatbots? Macros are agent tools — a human is still writing and sending the response (with a template as the starting point). Chatbots are automated responders that handle questions without a human in the loop. Macros scale human efficiency. Chatbots replace the human entirely. Both have a place depending on the question type.