Write one good answer for each question customers ask repeatedly, keep those answers in one shared place, and adapt the saved answer to each email instead of retyping it. Then work upstream: if a question keeps arriving, something on your website, checkout, invoice or onboarding email is unclear. Fix that, and fewer customers need to write in at all.
How do I find out which questions repeat?
Look at what you already sent. Your sent folder is a record of every question you answered.
- Take a month of replies. Skim your sent folder, or the shared mailbox’s, for customer threads.
- Write down the underlying question, not the wording. “Where’s my parcel?”, “has it shipped?” and “no tracking yet” are one question.
- Tally. One line per question, one mark per time it came in.
- Search for your own phrases. If you find yourself typing “the return label is in”, search the sent folder for it. The hit count is a quick measure of how often you give that answer.
The top of the list is usually short and stable. Those questions are where saved answers pay off first.
How do I write an answer I can reuse?
Write it once, carefully, with every part the customer needs to act. A reusable answer has five parts:
| Part | Example for “Can I change my delivery address?” |
|---|---|
| Short answer | Yes, until the order is packed. |
| Condition | Orders are usually packed the morning after they are placed. |
| Steps | Reply with the full new address and the order number. |
| Exception | If it is already packed, we can ask the courier to redirect it, which adds a day. |
| Link | The shipping page, for customers who want the details. |
When you use it, write the first sentence fresh so it reacts to the customer’s email (“Yes, and good news: your order hasn’t been packed yet”), then paste the rest and adjust anything specific to their case. Reply templates that don’t sound canned goes deeper into keeping reused text from reading like a form letter.
Where should reusable answers live?
Somewhere everyone who answers email can reach in a few seconds. The right place depends on who answers and who else reads the answer.
| Option | Good for | Watch out for |
|---|---|---|
| Gmail or Outlook templates | One person answering from their own account | Personal to each account; teammates cannot see your updates |
| A shared document | A small team on one support@ address | Needs one owner, or versions drift |
| Help center articles | Questions customers could answer themselves | Written for customers, so keep internal notes out |
| FAQ or product pages | Questions asked before buying | Easy to forget when a policy changes |
A common setup: the shared document is the internal source, and the answers that customers can use on their own also become help articles. Reply with a short answer plus the link, and the article does the rest.
How do I stop customers asking the question at all?
Ask where the question comes from. A question that arrives every week points to a gap you can close.
| Repeat question | Likely cause | Upstream fix |
|---|---|---|
| “Where is my order?” | No tracking link, or it arrives late | Send tracking in the shipping email; say when it becomes active |
| “Can I change my order?” | Confirmation email does not say how | Add one line: how and until when |
| “Why was I charged twice?” | A pending card authorisation looks like a second charge | Explain it on the payment page and the receipt |
| “How do I cancel?” | Cancel option hard to find | Put it where customers look: account settings, the receipt |
| “Do you ship to…?” | Shipping countries only in the terms | List them on the product page and at checkout |
Each fix removes a share of that question for good, which saves more time than answering faster. The causes in the table are common examples; your tally shows your own.
When should a repeat question get a help article?
Write an article when the answer is the same for every customer, needs more than a few sentences, or includes steps with screenshots. Keep it in email when the answer depends on the customer’s account, order or situation.
A simple test: if you could send the answer without looking at anything about the customer, it can be an article. Link it from the reply, the auto-reply and the page where the question arises.
How do I keep repeated answers the same across the team?
Different people answering the same question in different ways confuses customers, especially when the answers disagree on a fact.
- One owner per answer: when a policy changes, one person updates the saved answer, the help article and the facts page together.
- A date on each answer: “Last checked 12 September” tells a teammate whether to trust it.
- Retire old versions: delete the superseded answer instead of keeping both.
- Listen for follow-ups: if customers answer your saved reply with the same follow-up question, add the answer to it.
Can software answer repeat questions for me?
It can write the first version, as long as it draws on the answers you already gave. ReplyPen reads your past replies, help pages and website, and leaves a Draft for each new customer email in your Gmail or Outlook thread. The Check note under the Draft lists which past emails and articles it used, so you can see whether it picked up your current answer or an old one before you send. When you edit a Draft, ReplyPen records what changed in its Knowledge log, a list you can read and correct, and uses it when the question comes in again.
Repeat questions are one part of a faster, more reliable inbox. The full routine, from filtering mail to measuring quality, is in How to answer customer email faster without lowering quality. To decide how quickly these answers should go out, see What response time should a small team aim for on customer email?.
