The same four sentences get typed again. A form came in, the reply is some version of "this has arrived, someone will look at it by Thursday, here is who to contact if it is urgent", and that message has been written from memory eleven times this month, slightly differently each time. Canned messages are the obvious fix. For one person handling their own mail, they are a good fix.
For a team sharing the work, they solve the typing and leave the harder problem alone. The harder problem is not composing the reply. It is knowing which submissions have been answered, by whom, and with what promise attached. Gmail's template feature has nothing to say about that, and most of the trouble people run into with canned messages comes from expecting it to.
The feature exists, under a different name
Gmail shipped this as Canned Responses when it lived in Labs. It now ships as Templates, and it starts switched off. Open the gear icon, choose See all settings, open the Advanced tab, set Templates to Enable, and save. The setting belongs to the account, so everybody on a team does this separately.
Once it is on, the three dot menu in the bottom corner of a compose window gains a Templates entry. Saving starts from a draft: write the message, open Templates, choose Save draft as template, then save it as a new one. Inserting works the same way in reverse, and the text lands inside whatever compose window is open, so a template can be dropped into a reply and then edited before it goes.
The other half of the feature sits in filters. A filter can take Send template as its action, and that is the only way Gmail sends one of these without a person pressing anything. Most automatic acknowledgements built on Gmail are exactly this: a filter that matches the mail the form sends, with a template attached.
Two details decide whether that is enough. The template is stored in the account that created it, not in a shared place. And the body is plain text with no merge fields, so the name in the greeting is typed by hand on every send. Almost everything below follows from those two facts.
Which replies are worth templating
The replies that repay the effort share three properties. They go out often, they carry the same promise every time, and the part that changes is short and obvious. An acknowledgement of a form submission qualifies on all three. So does a request for a document that was left out, a rejection at the application stage, a scheduling message offering two slots, and the message that says a request has been handed to another team.
The gain is not typing speed. Typing is the cheapest part of answering somebody. The real gains are elsewhere.
The promise gets written once and checked once. How long a reply takes, what happens next, who to contact in the meantime: those sentences are hard to get right and easy to get wrong under pressure. Writing them once, calmly, is worth more than writing them quickly forty times.
The reply stops varying with the hour of the day. A message sent at nine in the morning and a message sent at six in the evening should promise the same thing. Without a template they rarely do, and the difference is visible to anybody who compares notes with a colleague.
The decision shrinks. Answering becomes picking from a short list rather than starting a small piece of writing, and small pieces of writing with no deadline are exactly the tasks that get deferred until the pile is unmanageable.
There is a quieter fourth gain. A set of templates is a written record of what a team promises. When the promise changes, there is one place to change it, and anybody new can read what the team says before they are asked to say it.
The four places this breaks for a team
Each template lives in one account
A template saved by the person who wrote it is invisible to everybody else. The usual workaround is to paste the wording into a shared document and have each person save their own copy, which works until the wording changes. From then on there are as many versions as there are people, and no way to tell which one somebody used.
Nothing records that the reply went out
The only record is the sent folder of whoever sent it, which nobody else can read. When the question is "did this applicant ever hear back", the answer takes a search through someone else's mailbox, and a negative result is not proof. This is how the same person receives two replies and another receives none.
The submission itself carries no state
Mail has read and unread. Work has not started, waiting on the applicant, ready to decide, closed. A shared inbox flattens all of that into whether somebody happened to open the message. Stars and labels are a way of faking it, and they fail in the same place every time: when two people are working the list at once, nothing stops both from picking up the same item.
The variable is a human being
With no merge fields, the name, the role and the date are typed in by the sender. That is the mechanism behind the single most damaging failure in this whole area, which is a message that opens with the wrong person's name. A template makes that mistake more likely, not less, because the surrounding text looks finished and invites less checking than a message typed from scratch.
Automatic replies through filters, and what to plan for
A filter plus a template is a real auto reply, and it is the right tool for the acknowledgement that goes to everybody. It has edges worth knowing before it is switched on.
The filter matches mail, not people. Somebody who submits a form three times gets three acknowledgements. That is usually correct for a form and usually wrong for an email thread, which is why filters for this should be narrowed to the notification address the form sends from rather than applied to a whole label.
It cannot branch on what was answered. Every submission gets the same text, so the template has to be true for all of them. A message that promises a same day reply is a liability the moment one category of request takes a week.
It answers whatever address is in the reply field. Forms that pass the submitter's address through correctly are fine. Forms that send from a no reply address of their own turn the acknowledgement into a message the submitter never sees, and nobody notices because the send itself succeeded.
Loops are rare but expensive. Two systems each answering the other automatically will keep going. Restricting the filter to mail from one known sender, rather than to everything with a given subject, removes the risk almost entirely.
Finally, the acknowledgement is not the reply. An automatic message that promises attention and is followed by silence is worse than nothing, because it converts an ordinary wait into a broken promise. The filter is only safe when somebody is genuinely working the list behind it.
Four ways to hold shared wording
| Approach | Where the wording lives | Who can use it | Fills in names automatically | Records the send against the person | Tracks status |
|---|---|---|---|---|---|
| Gmail templates | The account that saved it | One person | No | Sent folder only | No |
| Shared document of wording | A file everybody opens | Anybody who finds the file | No | No | No |
| Shared inbox or help desk tool | The tool, shared | The team | Usually, for sender details | Yes, per conversation | Yes, per conversation |
| Form tool with response management | The tool, shared | The team | Yes, from the submitted answers | Yes, against the submission | Yes, per submission |
The distinction that matters in that table is the second to last column. Wording is the easy half of this problem and every option handles it. The record of what was sent to whom is the half that decides whether a team can answer a question about its own work, and the last two rows are the only ones that produce it without somebody keeping a spreadsheet by hand.
The difference between those two rows is where the answers live. A help desk tool starts from an email thread, so the form answers arrive as a block of text inside a message. A form tool with response management starts from the fields, so the name, the role applied for and the date requested are separate values that can be dropped into a reply and filtered on in a list.
Writing one that does not read canned
The tell is not that a message is a template. It is that the template was written to cover every case and therefore says nothing.
Lead with the outcome or the state. "This has arrived and is with the admissions team" is information. "Thank you for contacting us" is not, and it pushes the useful sentence below the preview line on a phone.
Name the specific thing that arrived. The form, the role, the date. Anybody who has submitted three applications this week cannot tell which one this is about otherwise, and an unnamed acknowledgement reads like a mass mailing even when it is not.
Make one promise, with a date in it. A named day beats a duration, because a duration starts an argument about which day counts as the first. If the honest answer is that it varies, say the longest case and beat it.
Bracket the variables and leave the brackets visible. A slot that reads [name] is caught when it is not filled. A slot that reads Hello there looks finished and ships broken.
Subject: Received: [form name], [date]
Hello [name],
Your [form name] submitted on [date] has arrived and is with
[team]. A reply will reach you by [day], and if anything is
missing from the submission that message will say what.
For anything urgent before then, reply to this message and it
will reach the same person.
[sender name]
[organisation]
Two things not to put in a template. Do not apologise for a delay in advance, because an apology that arrives before the delay reads as an excuse and it is still there months later when the delay has been fixed. And do not write "as soon as possible", which promises nothing and is read as a refusal to commit.
Keeping them true after they are written
A template is a promise in storage, which means it goes stale quietly. Four events should trigger a read through of the whole set.
The response time changes. A team that has shrunk is still sending the message that promises a reply within one working day. This is the most common stale template and the most damaging, because every send makes a commitment the team already knows it will miss.
Somebody leaves. Their name is in the signature of the templates they wrote and possibly in the body. Mail sent in the name of somebody who has gone is a small thing that erodes confidence quickly.
The form changes. A template that asks for a document the form now collects makes the sender look as though they did not read the submission.
The season changes. Closures, holidays and intake deadlines all sit inside wording that was written when they were months away.
Naming makes the review possible. A flat list of twenty templates with titles like "reply 2" cannot be audited. Prefixing by stage, so that everything beginning with the same word belongs to the same part of the process, turns the list into something a person can read top to bottom and one person can be made responsible for. Without an owner, the set grows and nobody prunes it.
When the reply belongs next to the submission
The honest summary of Gmail templates is that they fix composition for an individual and leave coordination untouched. If one person answers everything, that is the whole problem solved and there is no reason to look further.
Coordination becomes the bottleneck at a specific point: when more than one person answers from the same list, or when somebody has to answer the question "what happened to this submission" weeks later. At that point the useful move is not a better template. It is putting the reply on the same screen as the answers, so the state of each item, its owner and the record of what was sent are properties of the submission rather than facts scattered across several mailboxes.
That is the shape worth comparing against. The features of a response screen come down to four things: a status on every item, a named owner, saved wording with the submitted values filled in, and a history of every message that went out. The situations where this pays off are the ones with a queue and more than one person working it. Anybody who wants to see whether that changes the day to day can work through a live form and its responses faster than they can rebuild a shared template document.
What to change first
Count how many people on the team have their own copy of the acknowledgement wording, then read those copies side by side. The differences are the size of the problem, and they will be larger than expected. Fix the wording in one place first, and if more than one person is answering from the same list, Halict keeps one copy of the wording next to the queue, with a record of what was sent against each submission before building the shared document that will be out of date by next month.
Q1. Why can I not find Canned Responses in Gmail any more?
It was renamed. The feature is now called Templates and it is switched on under See all settings, in the Advanced tab. Once enabled, it appears in the three dot menu of a compose window rather than anywhere in the main settings screen.
Q2. Can a Gmail template be shared with the rest of the team?
Not by Gmail itself. A template belongs to the account that saved it, so sharing means each person saving their own copy of the same wording. Keeping those copies identical over time is the part that fails, which is why teams end up with several versions in circulation.
Q3. Can a template fill in the recipient's name automatically?
No. Gmail templates hold plain text with no merge fields, so the name and any other detail are typed by the sender on each send. Automatic filling of a submitter's own answers requires a tool that holds those answers as separate fields.
Q4. How do I send a canned message automatically when a form is submitted?
With a filter. Create a filter that matches the notification the form sends, and set Send template as its action. Narrow the filter to that one sender address rather than to a subject line, because a broad match is what produces duplicate and looping replies.
Q5. Is an automatic acknowledgement better than no reply at all?
Only when somebody is genuinely working the queue behind it. An acknowledgement that promises attention and is followed by silence turns an ordinary wait into a broken promise, and the person who chases it then costs more time than the original reply would have.