Why well-built macros change everything
A macro is a pre-written response an agent can drop in with one click and then personalize. Done well, they free up time AND lift quality (consistent tone, complete responses). Done badly, they turn your conversations into corporate spam.
The golden rule: a macro is never sent as-is. It's a skeleton you personalize in 30 seconds — not a generic send.
Macro 1 — The "human" acknowledgment
You've received a support email, you can't reply right away, but your client shouldn't sit waiting 6 hours with no sign of life.
"Hi [First name], I've received your message about [topic]. I'm looking into it specifically and I'll come back to you by end of day with a complete answer. For context, I've already looped in [team] on point [X] so they can dig in parallel. Talk soon, [Agent first name]."
Why it works: (1) personalized name, (2) a short restatement of the topic (proof you've read it), (3) a specific commitment on timing, (4) a first visible action. The client gets back to their work feeling reassured.
Trap: "We have received your request and will get back to you as soon as possible" — dead wording that commits to nothing. Ban it.
Macro 2 — The clarifying question
The client has asked an incomplete question. You need information to answer, but you want to avoid endless back-and-forth.
"Hi [First name], so I can give you a precise answer on [topic], I'll need 3 quick pieces of info: (1) [info 1], (2) [info 2], (3) [info 3]. Could you send these in reply to this email? As soon as I have them, I'll get back to you within 2 hours with a complete answer. [Agent first name]."
Why it works: you ask for EVERYTHING you need in one go (not info 1, then another, then another). And you commit on timing after receipt, which motivates the client to reply quickly.
Macro 3 — The reasoned decline
The hardest macro to write. The client is asking for something you can't do (a goodwill gesture, a feature, an exception). The craft is in declining without breaking the relationship.
"Hi [First name], I hear you on your request about [topic], and I'm genuinely sorry I can't say yes. The reason: [concrete, honest reason in 1-2 sentences]. What I can offer you instead is: [concrete alternative]. Would that work for you? [Agent first name]."
Why it works: acknowledgment ("I'm sorry") + explanation ("the reason") + alternative ("what I can offer") + opening the dialogue. The client may be disappointed but they understand.
Trap: "Unfortunately that's not possible" with no explanation. Always say why. And always propose an alternative, even an imperfect one.
Macro 4 — The transparent internal escalation
You can't resolve the case yourself, you need to hand off to a colleague / a manager / another team. The client needs to know without feeling they're being bounced around.
"Hi [First name], your request about [topic] needs input from [team/person], who owns this area specifically. I've just forwarded your file to them with a full brief (you won't have to re-explain anything). They'll come back to you within [timeframe]. I'm staying in copy to make sure things move. [Agent first name]."
Why it works: you reassure the client that they won't have to start over from scratch (fear #1 in any escalation), you give them a timeframe, and you stay in copy as a guarantor.
Macro 5 — The proactive close
You've resolved a case. Instead of closing abruptly, you take 30 seconds to polish the exit.
"Hi [First name], your case on [topic] is resolved: [one-sentence summary of the solution]. While we were at it, we also took the opportunity to [useful side action, if applicable]. Don't hesitate to come back to me if you need anything — I know your file. Have a great day, [Agent first name]."
Why it works: explicit confirmation of resolution (the client needs to know it's done), perceived added value ("we also took the opportunity to..."), an invitation to come back to YOU by name ("come back to me," not "to support"). Statistically, this is the macro that drives the most NPS.
The classic mistake that makes a macro useless
Too many variables to fill in. If your macro contains [First name], [topic], [info 1], [info 2], [info 3], [timeframe], [alternative], [explanation]... you're asking so much effort from the agent that they'll end up sending the raw template, or not using it at all.
Rule: maximum 3-4 variables per macro. The rest should be directly usable as-is, or generic enough by default to be acceptable.
Going further
If you want to build out a complete library (30 to 80 macros covering 70-80% of your volume), we do this with you as part of our Outsourced Support offering or Tools & processes.