A customer writes a detailed message explaining a specific problem. She has clearly spent time on it.
The reply arrives quickly and is accurate. It also begins with a greeting that does not use her name properly, addresses a slightly different version of her question and ends with a paragraph about how much her custom is valued.
She now knows she was handled rather than helped. The information was correct and the experience was worse than a slower, shorter, human reply would have been.
Mistake 1: sending the template unedited
The core error. A macro is a starting point, and sending one unchanged tells the customer that nobody read what they wrote.
Mistake 2: writing templates to cover every case
Which makes them general, hedged and long, and a general answer to a specific question reads as an evasion.
Mistake 3: leaving the placeholders visible
A greeting with a wrong name or an unreplaced field is the single most damaging small error in support.
Mistake 4: opening with the policy
Templates frequently begin with the rule rather than with the person's situation, which sets an adversarial tone immediately.
Mistake 5: padding with corporate warmth
Paragraphs about valuing custom, which nobody reads and which lengthen a message the customer wants to be short.
Mistake 6: using the same template for angry and neutral messages
The information may be identical and the framing must not be, which is the tone judgement in writing chatbot copy that sounds like your brand.
Mistake 7: never reviewing them
Templates written three years ago describing processes that have changed, sent daily by people who assume somebody checks them.
Mistake 8: having too many
An agent choosing between forty macros spends longer than writing a reply, and picks the nearest rather than the right one.
Mistake 9: writing them in policy language
Rather than in the words customers use, which is the difference between an answer somebody understands and one they have to interpret.
Mistake 10: not measuring which produce follow ups
A template that generates a second message has failed, and nobody tracks which ones do.
Mistake 11: using them as a substitute for training
New agents sending macros they do not understand cannot handle the follow up question, which is the gap in training a small support team without a manual.
Mistake 12: applying them to the wrong channel
A message written for email sent as a chat reply reads as a wall of text at a moment somebody wanted a sentence.
Mistake 13: treating the first line as optional
It is the whole of the difference. Ten seconds acknowledging the specific situation transforms an identical message.
Mistake 14: letting the macro decide the answer
Agents sometimes pick the nearest available template and send it, which answers a question the customer did not ask. A library that is too large actively encourages this, which is why fewer and better templates outperform more of them.
Keep the consistency and lose the tone
An assistant answering the routine questions in the business's own voice, and handing over cleanly with the conversation attached, means the template library shrinks to the cases that genuinely need a person and those get written properly. Draft and adapt with the ai reply generator, the response commitments sit in support tier and response time questions, and the cover question in weekend and holiday cover questions. Start at try, see features, and the sector view sits under small business.