Most support emails are variations on a dozen situations. Writing each reply from scratch is slow, and answers drift between teammates. A small set of templates fixes both, as long as you treat them as a starting point and personalize every one before sending.
Replace anything in square brackets. Keep the tone plain and specific. Customers can tell a copied paragraph from a person who read their email.
1. Automatic acknowledgment
Hi [Name], thanks for getting in touch. We have your message and someone from our team will reply within [one business day]. If you have anything to add, just reply to this email and it will stay in the same conversation. [Your company] support
2. Asking for more details
Hi [Name], thanks for reporting this. To track it down, could you send the steps you took just before it happened, what you expected to see, and a screenshot if you have one? The browser and device you are using helps too. Once we have that, we will dig in.
3. Bug confirmed
Hi [Name], thanks for the details. We have reproduced the problem and it is a bug on our side. Our team is working on a fix, and I will email you as soon as it is live. In the meantime, [workaround].
4. Bug fixed
Hi [Name], good news: the issue you reported with [feature] is fixed. You may need to refresh the page to see it. Thanks again for flagging it. Reports like yours make the product better. Let me know if anything still looks off.
5. Feature request
Hi [Name], thanks for the suggestion. I have shared it with the product team along with how you would use it, which really helps us prioritize. I can't promise a date, but I have noted your email so we can let you know if we build it.
6. How-to answer
Hi [Name], you can do that from [location]: [step 1], [step 2], then [step 3]. Here is the guide with screenshots: [link to guide]. If it doesn't match what you see, reply with a screenshot and I will take a look.
7. Refund approved
Hi [Name], I have refunded [amount] to your original payment method. Depending on your bank, it can take 5 to 10 business days to appear. Sorry it didn't work out, and if there is anything we could have done better, I would love to hear it.
8. Refund declined
Hi [Name], thanks for reaching out. Your [plan] renewed on [date], and our policy covers refunds within [period], so I can't issue a refund this time. I have turned off auto-renewal so you won't be charged again, and your account stays active until [date].
9. Outage or incident
Hi [Name], thanks for letting us know. We are currently seeing an issue affecting [feature] and our team is working on it. You can follow live updates on our status page: [status page link]. I will reply here once it is resolved. Sorry for the disruption.
10. Following up when the customer goes quiet
Hi [Name], just checking in on this. Were you able to [resolve the issue]? If you still need help, reply here and we will pick it up. If I don't hear back, I will close this conversation in a few days. You can reopen it anytime by replying.
11. Handing off to a teammate
Hi [Name], I have brought in [Teammate], who handles [area] and is the best person to help with this. They have the full history of our conversation, so you won't need to repeat anything. You will hear from them [timeframe].
12. Closing the conversation
Hi [Name], glad that is sorted. I am marking this as resolved, but if anything else comes up, just reply to this email and it will come straight back to us. Thanks for using [product].
How to keep templates from sounding robotic
- Start with their name and one line that shows you read their email.
- Edit at least one sentence for the specific situation before sending.
- Cut anything that does not apply. Shorter is better.
- Avoid filler like 'We apologize for any inconvenience this may have caused'. Say what happened and what you are doing.
- Sign with a real name, not just 'The team'.
Keep templates in one shared place
Templates only help if everyone uses the same version. Gmail templates are per person, so answers drift and fixes never spread. A shared inbox with saved replies keeps one copy the whole team can use and update.
In Troppus, canned replies are shared across the workspace and insert into the reply box in one click, ready to personalize. Workflows can send the acknowledgment in template 1 automatically when a new email arrives. Create a workspace to set them up.