Short answer: Good customer service response templates give your team a tested starting point for common situations so replies are fast, consistent, and complete, without sounding scripted. The trick is to template the structure (acknowledge, answer, next step) and personalize the specifics every time. Below are fifteen templates for the situations support teams hit most, from angry customers and refunds to bugs, delays, and saying no, each written to be adapted rather than pasted.
Last updated: July 2026
How to use templates without sounding like a robot
A template is a skeleton, not a script. The fastest way to make a customer feel like a ticket number is to send them a reply that obviously was not written for them. So use these to lock in the structure and the must-say details, then change the opening line, name the customer's actual problem in their words, and cut anything that does not apply. Every strong support reply does three things in order: it acknowledges the situation, it answers or acts, and it states the clear next step. Keep that spine and vary everything else.
One rule before the examples: never open a reply to an upset customer with a template greeting like "Thank you for reaching out." Lead with their problem. "You are right that this invoice was charged twice, and I am fixing it now" earns more trust in one sentence than a paragraph of pleasantries.
Angry or frustrated customer
1. Customer is angry and mostly right.
Hi [Name], you are right to be frustrated, and I am sorry. [Restate exactly what went wrong in one sentence.] Here is what I am doing about it right now: [specific action]. You do not need to do anything on your end. I will follow up by [time] to confirm it is resolved.
2. Customer is angry and partly mistaken.
Hi [Name], I understand why this looked wrong, and I want to walk you through exactly what happened so it makes sense. [Plain explanation, no jargon, no blame.] To make this right, I can [option]. Would that work for you?
With heated tickets, the words matter less than the sequence: acknowledge the feeling, take ownership of the part that is yours, and move immediately to action. If a conversation is escalating past what a first reply can fix, it belongs in a defined path, which is what an escalation matrix gives your team.
Refunds, billing, and charges
3. Approving a refund.
Hi [Name], I have approved your refund of [amount], and it is on its way. You will see it back on your [card or method] within [realistic window]. Sorry for the trouble this caused, and thank you for your patience while we sorted it out.
4. Declining a refund, kindly.
Hi [Name], thank you for explaining. After looking into this, I am not able to refund [item] because [honest, specific reason tied to policy]. What I can do is [concrete alternative], which I think will help with [their underlying goal]. Want me to set that up?
5. Explaining a duplicate or unexpected charge.
Hi [Name], I looked into the charge you flagged. [What it actually was.] If that is not what you expected, I can [reverse it / adjust it] right away. Just confirm and I will take care of it today.
Billing questions are where trust is easiest to lose, because the customer is watching their own money. Answer them fast and in plain numbers. The wider pattern of getting billing communication right is covered in our piece on the billing experience and the invoicing mistakes that cost customer trust.
Bugs and technical problems
6. Confirming a bug you can reproduce.
Hi [Name], thanks for the detailed report, that is genuinely helpful. I reproduced the issue on my end, so this is on us, not your setup. I have logged it with our engineering team as [priority]. I will update you by [date] with a fix or a timeline, whichever comes first.
7. Asking for more detail on a bug.
Hi [Name], I want to get this fixed for you and I need two quick things to pin it down: [specific detail 1] and [specific detail 2]. A screenshot of [screen] would help too. Once I have those I can move fast.
8. A known issue with no fix yet.
Hi [Name], you have hit a known issue our team is already working on. I do not want to give you a fake date, so here is the honest status: [status]. In the meantime, [workaround]. I have added you to the list to be notified the moment it is fixed.
Delays, waits, and follow-ups
9. Setting expectations on a longer wait.
Hi [Name], this one is going to take a bit longer than a standard request because [honest reason]. Realistically you are looking at [timeframe]. I will not go quiet on you: I will check in on [date] even if I do not have the full answer yet.
10. Proactive update when you promised one.
Hi [Name], quick update as promised. [Where things stand.] Nothing you need to do right now. Next update from me by [date].
11. Following up on a quiet ticket before closing.
Hi [Name], I wanted to check in on this before I close it out. Did [solution] sort things for you, or is there still something open? If I do not hear back in a few days I will assume it is resolved, but you can always reopen it and I will pick right back up.
The reason these follow-up templates matter is that response speed is one of the clearest signals a customer reads about how much you value them. If your team struggles to reply consistently, the fix is usually structural, which is where shared inbox management and clear ownership come in rather than more canned text.
Saying no, and setting boundaries
12. Declining a feature request without dismissing it.
Hi [Name], thank you for this, it is a genuinely reasonable ask. I am not going to pretend it is on the roadmap when it is not, but I have passed it to our product team with your use case attached, because that is what actually moves these decisions. If [alternative] helps in the meantime, I am happy to set it up.
13. Enforcing a policy the customer does not like.
Hi [Name], I hear you, and I wish I had a different answer. Our policy on [thing] is [policy], and I am not able to make an exception here because [reason]. What I can do is [the thing you actually can do]. I know that is not everything you wanted.
14. Redirecting an out-of-scope request.
Hi [Name], this one sits outside what our team can change directly, but I do not want to just send you away. The right place for this is [where], and here is exactly how to get there: [steps]. If you hit a wall, come back to me and I will help you find the right person.
Closing and thanking
15. Closing a resolved ticket warmly.
Hi [Name], glad we got this sorted. I am closing the ticket, but it is never really closed from your side: reply any time and it reopens straight to me. Thanks for your patience while we worked through it.
Where should you store your templates?
Store templates where agents already work, in your help desk or shared inbox as saved replies or snippets, so using them is faster than not using them. If they live in a separate document nobody opens, they will not get used. Keep the library small and current: a handful of strong, well maintained templates beats fifty stale ones. Review them quarterly, retire the ones that no longer match your product or tone, and let agents suggest new ones from real tickets. Templates and a well organized knowledge base reinforce each other, since the same clear explanations serve both.
How many templates does a support team need?
Most teams are well served by fifteen to thirty templates covering their genuinely recurring situations, not hundreds. The situations customers write in about follow a predictable distribution: a small number of scenarios account for most tickets. Template those first, measure which ones get used, and only add more when a new recurring pattern earns it. Too many templates slows agents down because they spend longer searching for the right one than they would writing a fresh reply.
The point of a template is speed with a human on top
Templates exist so your team never starts a common reply from a blank box, and so the important details never get forgotten under pressure. They are not there to replace judgment. The best support orgs template the structure and the facts, then trust agents to make each reply sound like a person wrote it, because that combination is what makes support feel both fast and human. That balance between efficient process and genuine care is the heart of good customer experience operations.