Start from what you already send
Do not write macros in a meeting. Look at the last month of replies and find the answers that appear again and again. If your team has sent essentially the same reply five or more times, it deserves a macro. Flatdesk's AI macros do exactly this search for you and write the first draft, but a spreadsheet and half an hour does the same.
Write it as a person would
The test: read it aloud as if to a friend who had this problem.
- Lead with the answer, not an apology. “You can change the email on your account under Settings, Profile” beats “We apologize for any inconvenience”.
- Use the customer's name and the specific thing they asked about, not “your inquiry”.
- One ask per reply. If you need three details, number them so it takes one round trip.
- Give a time and keep it. “By Thursday at 3pm”, not “shortly”.
- Say no plainly, with an alternative if you have one.
Leave blanks where it must be edited
A macro is a starting point. Mark the parts that change in [brackets] so nobody sends “Hi [name]” by accident, and leave room for one sentence that shows you read the message. A macro that cannot be edited is the kind customers can smell.
Make it do the follow-up work
The best macros do more than reply: they tag the ticket, assign it, and set its status. A refund macro that also tags the ticket “refund” and closes it saves a second click on every ticket, and keeps your reports honest.
Keep a small set and review it
Twenty macros people trust beat two hundred nobody can find. Name them by the customer's situation (“Refund, within 30 days”), not by internal jargon. Once a quarter, retire the ones nobody used and fix the ones agents keep editing the same way. That last signal matters: if people change a macro in the same way every time, the macro is wrong.