How does a macro work?
- Write the reply once in plain language, leaving placeholders for the customer name, order number or date.
- Attach the housekeeping: status, priority, tag and assignment, so the agent does not set four fields by hand.
- Group macros by topic so agents find the right one without scrolling through a list of ninety.
- Review usage monthly, retire anything nobody applies and rewrite the ones agents edit every single time.
A worked example
A small orthodontic lab in Michigan answered the same four questions all week: case status, shipping dates, remake policy and impression quality. Its remote agent built four saved replies, each with a placeholder for the case number and one line the technician fills in. Applying one also sets the ticket to pending and tags it by topic. Reply time on those questions fell from most of a day to under an hour, and the monthly tag report now shows which question belongs on the website.
Where does a macro show up in your tools?
Zendesk and Gorgias call these macros and support variables that pull in customer fields; Freshdesk calls them canned responses, and Help Scout and Intercom call them saved replies. HubSpot offers the same idea as snippets and templates inside the conversations inbox.
Common mistakes
- Firing one off without reading the customer's actual question, so the reply answers something nobody asked.
- Letting the library grow past what anyone can scan, which pushes agents back to typing from scratch.
- Writing in stiff corporate language that reads nothing like the rest of your emails.
Why does a macro matter?
Most support volume is the same handful of questions wearing different clothes, and retyping each answer wastes the hours you are paying for. Saved replies make the common case quick and identical every time, which frees the agent to think hard about the unusual ticket. They also make a new agent useful in days rather than weeks.
How does AssistBPO handle a macro?
AssistBPO agents build your saved reply library during onboarding out of the emails you already send, then keep it current as products and policies change. Every one is written in your brand voice and approved by you before it goes live. The team lead checks a sample of tickets answered this way each month and coaches anyone sending a canned answer to a question that was not standard.