TL;DR:
A saved reply should carry the facts and the steps; the first line should be yours and mention the specific person and problem.
Replace stiff phrases with plain words and say what you will do and by when.
Review each saved reply by reading it aloud and imagining it arriving in your own inbox.
You know the reply the moment you receive it: "Thank you for contacting us. We apologize for any inconvenience this may have caused." Nothing in it says anyone read your message. Saved replies exist to save time on facts and steps. They go wrong when they also stand in for the human part.
When to use a saved reply
Use one when the same question comes up often and the answer is the same every time: how to reset something, where to find an invoice, what a message means. Do not use one when the customer is upset, has a detailed or unusual problem, or has written in more than once. Those need a message written for them.
What to prepare
A list of the ten questions you answer most. Your sent folder or ticket tags will show them.
Your tool's place for saved text. Many inboxes and help desks have one; a notes document works if yours does not.
A short style rule for the team: plain words, one idea per sentence, no stock apologies.
Step by step
Write the answer first: List the steps or the fact the customer needs. This is the part that is the same every time.
Remove the stiff parts: Delete "please be advised", "kindly", "at your earliest convenience" and anything a person would not say aloud.
Leave a gap at the top: Reserve the first line for you. A saved reply should start with a blank, not a fixed greeting.
Add a specific closing action: Say what happens next, such as "Reply here if the new link does not arrive."
Name and store it clearly: Name it by situation ("Invoice not received"), not by number, so you can find it quickly.
Read it aloud before saving: If you stumble, rewrite the sentence.
Worked example: three saved replies rewritten
1. Invoice not received
Before: "Thank you for reaching out. Please be advised that invoices are sent to the billing email on file. Kindly check your spam folder. We apologize for any inconvenience."
After: "[First line, yours: Hi Maya, sorry the invoice for March hasn't shown up.] Invoices go to the billing email on your account. Check your spam folder first. If it isn't there, tell me the billing email you expect and I'll resend it today."
2. Cannot sign in
Before: "We have received your request regarding access issues. In order to proceed, it is necessary that you reset your credentials by following the instructions below."
After: "[First line, yours: Hi Sam, I can see why you're locked out of your account.] Use Forgot password on the sign-in page and we'll email you a link. If it doesn't arrive in a few minutes, check spam. Reply here if it still doesn't work and I'll look at it with you."
3. Feature not available
Before: "Unfortunately, that feature is not currently supported. We value your feedback and have forwarded it to the relevant team."
After: "[First line, yours: Hi Jo, thanks for explaining what you're trying to do with the weekly report.] We don't have that yet. For now you can export the data and sort it in a spreadsheet. I've noted your request with the details you gave me."
Look at what changed. The bracketed first line is the only part you write each time, and it takes ten seconds: the customer's name and the actual problem. The rest keeps the useful steps and drops everything stiff. Each "after" is shorter than its "before" and has a next step.
One caution on the third reply: "I've noted your request" is only true if you do note it. Never promise a feature, a date or a fix you cannot confirm. Write only what you will really do.
A quick test for any saved reply: imagine you wrote in about a problem and received it. Would you know that a person read your message? Would you know what to do next? If either answer is no, the reply is not finished, however polished the wording.
Plain words do most of the work. "Use" instead of "utilize", "help" instead of "assist", "so" instead of "in order to". Short sentences also read as warmer, because people speak in short sentences when they are being straight with you.
Keep a note beside each saved reply of the date you last checked it and what it depends on, such as a screen name or a policy. When that thing changes, you know which replies to update.
Mistakes to avoid
Sending the reply unchanged. The personalized first line is what makes it a reply to a person.
Apologizing automatically. Apologize when something went wrong, in one sentence, with the specific thing. A blanket apology reads as a script.
Hiding the next step. If the customer has to guess what to do, the reply failed.
Letting replies go stale. Product screens and policies change. Review each saved reply on a schedule and after any change.
Using one for an angry customer. Write fresh and keep it short.
Doing it faster
Keep your saved replies in one place with situation names and review them every few months. You can also read a draft aloud to a voice assistant, for example DuckyHelper is always there on Mac, Windows and Linux, but trust your own ear on whether it sounds like you.
Frequently asked questions
How many saved replies should I have?
Start with your ten most common questions. A long list is hard to search and tends to go out of date.
Is it dishonest to use saved text?
No, as long as the content is true and addressed to the person. The risk is not the reuse; it is sending something that ignores what they wrote.
Get started
