Canned Response Examples: 24 Customer Service Templates You Can Use Today

A canned response is a pre-written reply that support agents save and reuse for common questions: refund requests, password resets, bug reports, delays. Good canned responses save time and keep answers consistent across the team. They work best as a starting point the agent personalises, not a finished reply fired off unchanged.

Below are 24 copy-ready templates grouped by scenario, followed by how to personalise them, when they backfire, how they compare with macros and AI-generated replies, and how to keep them from going stale. For the short definition, see our glossary entry on canned responses.

Canned response meaning

“Canned” means prepared in advance. In support tools you will also see saved replies, snippets, quick replies, and templates. They all describe the same idea: text you write once and insert many times.

A macro goes one step further. It inserts text and also does something to the ticket, such as tagging it, changing its status, or assigning it to a group. Every macro contains a canned response. Not every canned response is a macro.

How to use these templates

Placeholders are in square brackets. Replace every one before sending. Each template is short on purpose: add one sentence that refers to the customer’s actual message, and it stops sounding canned.

Acknowledgement templates

1. General acknowledgement

Hi [Name], thanks for getting in touch. I’ve read your message about [issue] and I’m looking into it now. I’ll update you by [time or day], sooner if I have an answer.

2. Acknowledgement outside business hours

Hi [Name], thanks for your message. Our team is offline until [time and time zone], and I’ll pick this up first thing. In the meantime, [link to relevant help article] may help if you need an answer sooner.

3. Need more information

Hi [Name], thanks for the details so far. To get this sorted, could you send me [specific item, for example the order number or a screenshot of the error]? As soon as I have that, I’ll take it from there.

Refund templates

4. Refund approved

Hi [Name], I’ve processed a refund of [amount] to your [payment method]. It usually takes [number] business days to appear, depending on your bank. I’m sorry [product or service] didn’t work out, and thanks for letting us know.

5. Refund not possible, with an alternative

Hi [Name], I’ve checked your account and this purchase falls outside our [number]-day refund window, so I can’t refund it directly. What I can do is [alternative, for example a credit, a plan change, or an extension]. Would that help?

6. Partial refund

Hi [Name], I’ve refunded [amount] for [reason, for example the days the service was unavailable]. The rest of the charge covers [what it covers]. If anything about that doesn’t look right, reply here and I’ll take another look.

Billing templates

7. Explaining an unexpected charge

Hi [Name], I can see why that charge was confusing. The [amount] on [date] is for [plain-English explanation]. You can see the breakdown in [where to find it]. If you’d like to change this going forward, [how to change it].

8. Failed payment

Hi [Name], your last payment of [amount] didn’t go through, most often because a card has expired or been replaced. You can update your details at [link]. Your account stays active until [date], so there’s no rush today.

9. Invoice request

Hi [Name], I’ve attached your invoice for [period]. You can download past invoices any time from [location]. If you need a company name, address, or tax number added, send me the details and I’ll reissue it.

Bug report templates

10. Bug confirmed

Hi [Name], thanks for reporting this, and for the detail. I’ve reproduced the problem with [feature] and passed it to our engineering team. I’ll update you when there’s a fix or a workaround. Until then, [workaround if one exists].

11. Cannot reproduce

Hi [Name], I’ve tried to reproduce this on my side and it’s working as expected for me, which usually means something specific to your setup. Could you tell me [browser and version, device, steps you took], or send a short screen recording? That will help me find it.

12. Bug fixed

Hi [Name], good news: the issue with [feature] you reported on [date] has been fixed. You may need to [refresh, update the app, log out and back in] to see the change. Thanks for your patience, and for flagging it.

Feature request templates

13. Feature request logged

Hi [Name], thanks for the suggestion. I’ve shared it with our product team along with your use case, which is the part they find most useful. I can’t promise a timeline, but requests like this do shape what we build.

14. Feature exists already

Hi [Name], good news: you can already do this. Go to [location] and [steps]. There’s a short guide here: [link]. Let me know if it doesn’t quite do what you need.

Password and account templates

15. Password reset

Hi [Name], you can reset your password at [link]. The reset email comes from [sender address], so check your spam folder if you don’t see it within a few minutes. If it still doesn’t arrive, reply here and I’ll help directly.

16. Account locked or verification

Hi [Name], for security I need to confirm it’s you before making changes to this account. Could you reply from the email address on the account, or confirm [verification detail]? Once confirmed, I’ll unlock it straight away.

17. Account deletion request

Hi [Name], I’ve started the deletion of your account and associated data. This completes within [timeframe], and you’ll get a confirmation email when it’s done. If you change your mind before then, just reply here.

Delay templates

18. Taking longer than expected

Hi [Name], I wanted to update you rather than leave you waiting. This is taking longer than I expected because [honest reason]. I’m still on it, and I’ll update you again by [specific time], even if there’s no new news.

19. Known outage or incident

Hi [Name], we’re aware of an issue affecting [feature or service] and our team is working on it now. You can follow live updates at [status page link]. I’m sorry for the disruption, and I’ll confirm here once it’s resolved.

Escalation to engineering templates

20. Escalated to a specialist team

Hi [Name], this needs a closer look from our [engineering or billing] team, so I’ve passed it to them with everything you’ve told me, so you won’t need to repeat yourself. I’m still your point of contact and I’ll update you by [time or day].

21. Engineering update with no fix yet

Hi [Name], a quick update on [issue]: our engineers have [what they have found or tried] and are still working on a fix. I don’t have a date yet, but I’ll check in again on [day] either way.

Closing templates

22. Confirming the issue is resolved

Hi [Name], glad that’s sorted. I’ll mark this as resolved. If anything related comes up, just reply to this email and it will come straight back to me.

23. Closing after no reply

Hi [Name], I haven’t heard back, so I’ll close this for now. If you still need help with [issue], reply here any time and we’ll pick it up where we left off.

Angry customer template

24. Acknowledging frustration

Hi [Name], I’m sorry. [Specific thing that went wrong] shouldn’t have happened, and I understand why you’re frustrated, especially after [what they have already tried or waited for]. Here’s what I’m doing right now: [concrete action]. I’ll update you by [time].

Use this one as a skeleton only. An angry customer needs to see that a person read their message. The specific sentences matter far more than the template.

How to personalise a canned response

A canned response becomes a good reply with three small edits:

1. Use their words. Mirror the specific thing they described: “the export button on the reports page” rather than “the issue”.
2. Add one sentence only they could receive. Refer to their plan, their order, something they tried, or a detail from an earlier ticket.
3. Cut what does not apply. If the template covers three possibilities and only one fits, delete the other two.

It also helps to write templates in a plain, human voice from the start. Avoid phrases customers associate with scripts, such as “we apologise for any inconvenience caused” or “your satisfaction is our priority”.

When canned responses hurt

Canned responses are a tool, and there are situations where they do more harm than good:

• The customer is upset. A generic reply to an angry message reads as dismissive, even if it is accurate.
• The template does not fit. A reply that answers a slightly different question tells the customer nobody read their message. That usually produces a second, angrier contact.
• The customer has already tried it. Sending the password reset link to someone who says the reset link does not work is the most common version.
• The information is out of date. Old prices, retired features, or changed policies in a template create new problems at scale.
• Several agents send the same text in one thread. Customers notice immediately.

Canned response vs macro vs AI-generated reply

The three are not competitors. Many teams use AI for the high-volume documented questions, macros for structured workflows such as refunds, and canned responses as the agent’s toolkit for everything in between. Our guide to writing help docs AI can answer from covers the maintenance side of AI replies.

How to keep canned responses current

Templates go stale quietly. Nobody notices until a customer quotes an old price back to you. A light process prevents that:

• Give each template an owner. Billing templates belong to whoever owns billing policy, product templates to whoever tracks releases.
• Date them. Add a “last reviewed” date in the template name or description.
• Review the most-used ones monthly. Most helpdesks show usage counts. The top ten templates are worth ten minutes a month.
• Review everything quarterly, and retire templates nobody has used.
• Update on change. When pricing, policy, or a key feature changes, search your templates for every mention before the change goes live.
• Listen to agents. If agents are routinely editing the same sentence, rewrite the template.

Where Fidiora fits

Fidiora includes a shared inbox, macros, tags, and SLAs at no extra cost, with no seat fees. Its AI answers customer questions directly from your help content, so the repetitive questions your canned responses were written for can be resolved before they reach an agent, and anything it cannot resolve is handed to your team free. You pay $0.69 per genuine resolution, dropping to $0.45 above 1,000 a month, abandoned chats are never billed, and a spend cap keeps the monthly total predictable.

Start with your top five

Pull the five canned responses your team used most last month. Read each one as if you were the customer, fix anything out of date, and add a placeholder that forces a personal sentence. That small change improves more replies than writing twenty new templates.