Here are recurring support tickets: [TICKETS] Build a macro library: 1. Group them by the underlying problem, not the wording the customer used 2. For each group, write one macro reply with [FILL IN] tokens marked where it must be personalised 3. Name each macro so an agent can find it under pressure 4. Note the one detail an agent must check before sending, so the macro is not sent blind 5. Flag any group where the right fix is a product change rather than a better reply — those are the expensive ones Tone: [TONE]. Sort the library by volume, most common first.
Owns the problem, says what changed, and skips the phrases that make people angrier.
The handoff note that stops the customer having to explain it a third time.
Turns a one-off reply into a documented article so the ticket stops recurring.