Templates & Canned Responses Done Right
"Dear valued customer, thank you for contacting the IT Service Desk. Your request is important to us and has been assigned reference number 7724. A member of our team will be in touch shortly." The requester is a colleague called Priya who sits two floors up and has worked there for nine years. Priya has just told the desk that the payroll export is broken on the day payroll runs. The message is not wrong. It is addressed to nobody, about nothing, and promises a time called shortly. Canned responses get a bad name from messages like this, and they deserve it. But the alternative is not typing every acknowledgment by hand at 09:04 with nine tickets waiting. The alternative is a better can.
This series is about the better can. It covers what canned responses are for and the messages that must never be canned. It covers writing a template that does not sound canned, with a personal slot and one ask. It covers personalizing one in ten seconds, which is the whole difference. Then come the twenty templates every desk needs, with the trigger for each. It covers keeping the library alive so the stale ones are retired and the shared ones stay shared. And it covers knowing whether templates help, by the numbers and by the complaint that says "it sounded automated". A template is a draft written by your calmest colleague. It is still your message once you send it.
Articles in This Series
- What Canned Responses Are For, and Not For
Speed and consistency on the routine message, the robotic failure and where it comes from, the messages that must never be canned, and the purpose card. - Writing a Template That Does Not Sound Canned
The personal slot, plain voice, short, one ask per message, no corporate filler; good and bad pairs for the same purpose; and a template skeleton with its slots marked. - Personalizing a Canned Response in Ten Seconds
The three things to always change, the one added sentence, the read-aloud test, and the personalization checklist. - The Twenty Templates Every Help Desk Needs
The list with purpose and trigger: acknowledgment, missing information, ETA, status update, resolved, cannot reproduce, out of scope, duplicate, waiting on vendor and the rest; and the library index. - Keeping the Template Library Alive and Trusted
Ownership, naming, shared versus personal, the quarterly review, retiring the stale ones, the template that drifted, and the review sheet. - Knowing Whether Your Templates Actually Help
Reply time, back-and-forth, satisfaction, the 'it sounded automated' complaint, which templates are used and which are not, and the template scorecard. - Ticket Acknowledgement Templates
Twelve first replies that say when: the automatic receipt, the standard reply, missing information, outage, after hours, VIP, chat, request with approval, duplicate and transferred, written out with the slots marked.
Explore More Topics
This series is part of the QuerySolv helpdesk topic library. It covers the foundations, processes, communication, knowledge, tooling, metrics, classic ticket domains, people and strategy behind a support desk that works. The library pairs well with the software we build: QuerySolv. It is a self-hosted help desk that runs as one Windows service on your own network. It is licensed once per installation, not per agent per month.