Saved replies that sound like you.
A saved reply is an answer you write once and reuse whenever the same question comes in. A good one saves typing and gives every customer the same correct answer. A bad one reads like a form letter, and the customer writes back to ask their question again. This guide covers which replies to write first, how to build them, how to keep two languages in step and when to leave them alone. Four templates are ready to copy.
Start with the questions that keep coming back
Skip the big library. Go through the last few weeks of email and chat, and mark the questions you answered more than twice. Those are your first saved replies.
For an online store, they’re often about delivery, returns, changing an order and invoices. For a SaaS product, they’re about logging in, billing, canceling and whether it can do a certain thing.
Start with a handful. A short list that people know by heart gets used. A long one gets scrolled past, and people go back to typing from scratch. Name each reply after the question it answers, such as “Where is my order”, so anyone on the team finds it with the first word that comes to mind.
Give every reply the same shape
Every saved reply needs the same few parts, in the same order. Put the answer near the top. Someone asking about their parcel wants the tracking link first, and a paragraph about how much you value them can go.
Keep sentences short, with one idea per paragraph. Many customers read your reply on a phone, between other things. Numbered steps help when they have to do something themselves.
The opening and the sign-off are where a reply becomes personal. The middle stays the same every time:
- Opening: one line that shows you read their question
- Answer: the facts, in a sentence or two
- Next step: a link, an action or a time frame
- Sign-off: a name
Use placeholders for what changes
Placeholders fill in the parts that differ per conversation: the customer’s name, the brand they wrote to and the name of the person replying. Check which ones your tool offers before you write. In Flagbell, saved replies have placeholders for the customer’s name, the brand and the agent, so one reply works for every brand.
Everything you fill in by hand needs a mark nobody can miss, such as square brackets: [order number]. Read the reply once before you send it. Nothing sounds more canned than “Hi [first name]”.
Plan for missing data. If you don’t know the first name, “Hi” or “Hi there” reads better than an empty gap or a full email address. And decide per address how a reply is signed: a person’s name from support@, the brand from info@.
Write the way you talk to customers
Read every saved reply out loud. If you wouldn’t say a sentence to a customer at the counter, rewrite it.
Leave room for one line that fits only this customer: what they ordered, something they mentioned, thanks for their patience. The saved reply gives you the body. That one line makes it sound written for them.
Tone matters most when someone leaves. Make canceling easy, say thanks and ask one question they can skip. Guilt trips and extra hoops leave a bad last impression.
A few swaps that help in any reply:
- “We apologize for any inconvenience” → “Sorry this took so long”
- “We have received your inquiry” → “Thanks for your message”
- “Please do not hesitate to contact us” → “Reply here if anything’s unclear”
- “At this moment in time” → “now”
Keep English and Dutch in step
If you answer in two languages, every saved reply has two versions, and they drift apart. Someone updates the return period in English, forgets the Dutch one, and your Dutch customers get the old rule.
Keep the facts apart from the wording. Write down which facts each reply depends on, such as the return period, delivery times or prices, and when one changes, update both versions in the same sitting. Flagbell keeps saved replies in English and Dutch, one tab per language, and a conversation gets the brand’s language.
Write the second version the way a native speaker would say it. A word-for-word translation of an English reply often sounds stiff in Dutch, and the other way round. Decide per brand whether Dutch replies use “je” or “u”, and keep it the same in every reply.
Know when to write from scratch
A saved reply fits a question with one right answer. For anything else, start from a blank reply. Or paste the saved one as a starting point and rewrite the opening and every part that doesn’t match what they asked.
If you need time to find out, say so. A short message with what you’re doing and when they’ll hear from you works better than a fast answer that misses the question.
Write the reply yourself in these cases:
- The customer is upset or complaining: answer the person, in your own words
- The question looks like a common one, with a detail the saved reply doesn’t cover
- They’re writing back after a saved reply that didn’t help
- Privacy requests, refunds outside your policy and anything legal
Review them every few months
Saved replies go stale quietly. A price changes, you switch carriers, a button gets a new name, and the reply keeps sending the old version. Put a review in your calendar: every few months, and after every change to your policies or product.
Go through each reply with these questions:
- Are the facts still right: periods, prices, links, button names?
- Do the English and Dutch versions say the same thing?
- Has anyone used it lately? If not, remove it.
- Did customers write back after it with the same question?
- Does it still sound like the brand?
In short
Write saved replies for the questions that keep coming back, each with an opening, the answer, a next step and a name. Leave room for one personal line, keep both languages in step and review them every few months.