15 canned response templates that do not sound canned

Canned responses have a bad reputation because most of them deserve it. A template that opens with "We apologize for any inconvenience this may have caused" tells the customer one thing: nobody read your message. Done well, canned responses are the opposite: they capture your team's best answer to a situation and make it the default, so speed goes up without the robotic aftertaste.

This guide gives you 15 templates you can copy, organized by situation, plus the editing rules that keep them human. Swap the bracketed parts, cut anything that does not apply, and store them somewhere with shortcuts (Chattypie's shared inbox ships canned responses with slash-command insertion, but the templates work in any tool).

The three rules that keep templates human

1. First sentence answers the question. Apology and context come after the answer, never before it.
2. One template per situation, not per sentence. If agents stitch four templates together, the seams show.
3. Leave a blank the agent must fill. A required [specific detail] slot forces personalization and catches lazy sends.

Refunds and billing

1. Refund approved

Good news: your refund of [amount] is on its way. It should reach your [card/account] within [X] business days. I have also [cancelled the subscription / kept your account active], as you asked. Anything else you need, just reply here.

2. Refund declined, with a reason

I looked into this and I am not able to refund this charge, because [specific reason, e.g. the plan renewed on date X after the cancellation window]. What I can do instead: [concrete alternative, e.g. credit for next month / prorated downgrade]. Would that work for you?

3. Duplicate charge

You are right, you were charged twice on [date]. I have refunded the duplicate [amount]; it should appear within [X] business days. Thanks for flagging it, and sorry for the mess on our side.

Bugs and outages

4. Bug confirmed

Thanks for the clear report. I reproduced the problem: [one-line description]. It is now with our engineers as [ticket reference]. I will update you here when it ships. In the meantime, [workaround if one exists].

5. Cannot reproduce, need more info

I tried to reproduce this and could not, which usually means it depends on something specific to your setup. Could you send me: [browser and version / a screenshot of X / the steps right before it happened]? With that I can dig properly.

6. During an outage

We are having an incident affecting [feature/area] right now. The team is on it, and live updates are at [status page]. You do not need to do anything; I will confirm here when it is resolved. Sorry for the disruption.

Feature requests

7. Request logged honestly

That is a reasonable ask. We do not support [feature] today, and I do not want to promise a date we might miss. I have logged your request with your use case attached, and I will reply here if it ships. Meanwhile, [closest existing alternative] gets you part of the way.

8. Feature exists

Good news: this already exists. Go to [location] and [short steps]. Here is our guide with screenshots: [link]. If it does not behave the way you expect, tell me what you see and I will help.

Expectations and handoffs

9. Need time to investigate

I do not have the answer yet. This needs [a check with engineering / account history digging], which usually takes [realistic time]. I will get back to you by [specific time] at the latest, even if only with a progress update.

10. Escalation handoff

I am bringing in [name/team], who handles [area], so you get an accurate answer rather than my best guess. They have the full history of this conversation; you will not need to repeat anything.

11. Out-of-hours auto-reply

Thanks for the message. Our team is offline right now and back at [time, with timezone]. We answer in the order received, and you are in the queue. If this is about [urgent category], see [self-serve link] for immediate steps.

Closing conversations

12. Solved, checking satisfaction

Glad that fixed it. I will close this conversation now, but replying reopens it any time and it comes straight back to me. If you have a minute, the rating below helps us know how we are doing.

13. Customer went quiet

Just checking in on this one. If [previous suggestion] solved it, great, no reply needed and I will close the thread in a couple of days. If you are still stuck, reply and we will pick it right back up.

14. Saying no clearly

Straight answer: no, we cannot do [request], and I do not expect that to change soon. It is because [honest reason]. If that is a dealbreaker, [alternative tool/approach] may fit you better, genuinely. If not, here is what we can do: [option].

15. Thank-you to a helpful reporter

Your report led us to a real bug that would have bitten others, so thank you. The fix ships in [timeframe]. Notes like yours make the product better, and it does not go unnoticed.

Making templates stick

• Review them quarterly. Templates rot as the product changes; assign an owner.
• Watch the helpful/unhelpful ratings per template if your tool tracks them, and rewrite the losers.
• Let your AI agent learn from them. An AI agent answering from the same approved language keeps automated and human replies consistent.
• Pair them with a good help center. Half of these templates end with a link; our guide on writing help articles people actually find covers the other half of the equation.
• For full email situations (apologies, refunds with context, win-back attempts), snippet templates are too short; we keep a separate set of longer email templates.