Saved replies that sound human
Learn how to write support templates that build trust. Jerry Holt shares his methods for keeping canned responses personal.
The short version
- →Remove greetings from your templates to keep the conversation natural.
- →Use bracketed placeholders to force yourself to add personal details.
- →Address the customer's specific anxiety instead of just stating a policy.
- →Avoid corporate jargon and stick to the language your customers use.
Canned responses sound human when you strip away the corporate greeting and leave placeholders for specific details. Effective templates focus on the customer's immediate anxiety rather than just stating a policy. By keeping the tone direct and leaving room to type a personal observation: you avoid the robotic feel that usually kills customer trust in a support interaction.
I have spent eighteen years running operations for service businesses. I have worked in a two-location restaurant group and a regional dental practice with eleven front desks. I have seen what happens when a front desk person gets overwhelmed. They start looking for shortcuts. They want to give the right answer, but they do not always have the energy to type it out perfectly every single time.
The problem is that most saved replies are written by people who are not in the trenches. They are written to sound professional, but professional usually ends up sounding like a robot. I have watched good leads die in a voicemail box because the response they finally got felt like it came from a machine. People want to know they are talking to a person who understands their problem.
Why do most saved replies feel so cold?
The reason most templates fail is that they try to do too much. They include a "Dear Valued Customer" at the start and a "Kind Regards" at the end. They use words like "inquiry" and "assistance" and "resolution." No one uses those words when they are talking to a friend.
In my dental practice: we noticed that the more formal our scripts were, the more defensive the patients became. If a patient is worried about a bill or a painful tooth, they do not want a formal letter. They want a neighborly answer. They want to know that you see them.
Most support tools make this worse by encouraging you to write long, bloated templates. Out of the twelve tools I have looked at for this kind of work: five of them do not even offer a free version of their software. Of the seven that do offer a free tier: four of them put limits on how many seats your team can have. When you are paying fifty dollars a month per seat: you feel pressured to make everything look "perfect" and corporate to justify the cost.
Why should you leave the greeting out of the reply?
This is the first rule I taught my teams. Do not include "Hi [Name]" in your saved reply. If the greeting is already there: the person sending the message will just click "send" without thinking. It becomes a reflex.
If you leave the greeting out: you force yourself to type the person's name. That one second of typing "Hi Sarah," or "Hey Mark," changes your brain. It reminds you that Sarah is a real person with a real problem. It also allows you to choose the right tone for the greeting. "Hi" might be right for a regular customer, but "Hello" might be better for a new lead.
I once wrote phone scripts at 2am for a restaurant group. I realized that if I gave the hosts a rigid script: they sounded bored. If I gave them the key facts and let them choose their own opening: they sounded like they actually worked there. The same logic applies to your email and chat templates.
How do you write for the anxious version of the customer?
Every customer who contacts a service business is a little bit anxious. They are worried their food will be late, their tooth will keep hurting, or their money is gone. Most canned responses focus on the company's process. They say: "Your ticket has been created."
The customer does not care about your ticket. They care about their problem. A human response addresses the anxiety first. If a customer is asking about a refund: they are worried you are going to steal their money. If they are asking about a delay: they are worried you have forgotten them.
I have watched how a simple change in phrasing can calm a person down. Instead of saying "Our policy is 5-7 business days," you say "I know it is frustrating to wait on a refund." You acknowledge the feeling before you give the fact.
What does the "blank bracket" method look like?
The best way to keep a template human is to leave yourself homework. I use brackets to indicate where a specific, manual detail must be added. This prevents the "copy-paste" look that customers hate.
If you see a bracket: you have to stop and think. You have to look at the customer's previous message or their account history. This ensures that the message you send actually fits the situation.
Here is an example of how this looks in practice.
The Bad Version (The Corporate Robot):
"Dear Customer, thank you for contacting our support team regarding your recent inquiry. We have received your message and a representative will review the details shortly. We appreciate your patience and look forward to assisting you. Sincerely, Support Management."
This message says nothing. It is a waste of the customer's time. It feels like a wall built to keep the customer away from a real person.
The Good Version (The Human Foundation):
"I just saw your message about [Problem]. I am looking into your [Account/Order] right now. I do not have the answer yet, but I wanted to let you know I am on it. I will get back to you by [Time] today."
This version is shorter. It uses plain words. It includes three sets of brackets that require a human to fill them in. When the customer receives this: they see that someone actually read their note and is taking action.
How do you handle technical or policy questions?
Sometimes you have to explain something complicated. In a dental office: explaining why an insurance claim was denied is a nightmare. In a restaurant: explaining why a delivery is late during a rainstorm is tough.
The temptation is to write a long, defensive paragraph that cites your terms and conditions. Do not do that. Keep the policy simple.
The Bad Version (The Defensive Policy):
"Per our company policy as stated on your service agreement: all cancellations must be made forty-eight hours in advance to avoid a fifty dollar fee. This fee covers the cost of the lost time for our providers. Thank you for understanding."
The Good Version (The Human Explanation):
"I saw you needed to cancel for [Day]. I am sorry you cannot make it. Since it is less than two days away: I do have to apply that [Amount] fee we talked about. We had already reserved that room and a nurse for you. I hope everything is okay on your end."
The second version is honest. It explains the "why" without hiding behind "company policy." It concedes that fees are a bummer. It sounds like one person talking to another.
How can you use these templates at scale?
I believe that every business should have a shared inbox and a knowledge base. These tools should not be expensive. In the market right now: things are complicated.
If you look at the Twelve tools I mentioned: several of them have high entry prices. Zendesk starts at roughly fifty-five dollars per agent. Help Scout is around fifty dollars a month. Intercom starts at thirty-nine dollars per seat. For a small business with a few people on the phones: those costs add up fast.
We built LastWorker to be different. We provide a shared inbox, tickets, a knowledge base, and saved replies for free. There is no subscription and no per-seat fee. You can have your whole team in there without a credit card.
We also do not force AI on you. In many modern tools: the AI starts answering for you immediately. We think that is a mistake for most service businesses. AI is off by default here. If you want to use it: it costs four cents to generate a reply on chat or email. It is there if you need it, but a human is always the starting point.
Why is response time more important than a "perfect" message?
In my eighteen years of operations: I have learned that a fast, imperfect message is better than a slow, perfect one. If you wait four hours to send a perfectly crafted email: the customer has already called your competitor.
Saved replies allow you to be fast. If you can respond to a lead in under five minutes: your chances of winning that business go up significantly. But if that fast response looks like a generic auto-reply: the customer will ignore it.
The goal of a canned response is to buy you time to solve the problem while letting the customer know they are heard. You use the template to acknowledge the receipt of the message: you fill in the brackets to show you are a person: and then you go do the work.
How do you keep your team from getting lazy with templates?
Even with the best templates: people get tired. I have seen front desk staff start to skip the brackets when the phones are ringing off the hook.
The fix for this is regular reviews. I used to spend thirty minutes every Friday looking at the messages we sent that week. I was not looking for "synergy" or "metrics." I was looking for humanity. I would point out the messages that felt cold and ask how we could have made them warmer.
I also made sure the team knew they had permission to ignore the templates. If a situation is weird: do not use a saved reply. Type something from scratch.
If you are a solo entrepreneur: you have the same problem. You get tired of answering the same five questions. That is why we made the help center and knowledge base features free. You can put the answers to those common questions in a public help center so people can find them without emailing you.
What should you do next?
Take a look at the last ten emails you sent to customers. If they all start with the same sentence: you have a problem.
Try the bracket method. Create five templates for your most common situations: like booking a new appointment or handling a billing question. Remove the greetings. Put in the brackets. See if the tone of your conversations changes.
At LastWorker: you can set this up in about five minutes. Our live chat and email support are free forever. You get unlimited conversations and unlimited teammates. If you want to add a phone number: it is one dollar a month. If you want a phone call answered by a human-sounding AI: it is ten cents a minute.
I have watched too many businesses struggle with expensive software that makes them sound like a big, faceless corporation. You do not need a fifty dollar a month subscription to talk to your customers like a human being. You just need a simple tool and a better way of writing.
Frequently asked questions
How do I make a canned response feel personal?
You make it personal by leaving the greeting out of the template and using brackets for specific details. This forces the person sending the message to type the customer's name and a unique detail manually.
Are saved replies better than typing every message manually?
Yes, they prevent errors and save time during busy shifts. The key is to use them as a foundation rather than a finished product.
When should I not use a saved reply?
Avoid them when a customer is expressing high levels of frustration or when the situation is unique. In those cases, a fully custom message is the only way to show you are listening.
Jerry Holt has spent eighteen years running customer operations for service businesses, from a two-location restaurant group to a regional dental practice with eleven front desks. He has hired receptionists, written phone scripts at 2 a.m., and watched good leads die in a voicemail box. These days he writes about what actually moves the needle on the phones, in the inbox, and over chat, and where AI earns its place versus where it gets in the way.
Keep reading
Stop letting customers go to voicemail.
Set up in about fifteen minutes. Live chat and email are free forever, so there is no bill to weigh up before you try it.