Canned responses examples that do not sound canned
69 editable canned responses examples, organized by scenario — the pre-written replies a support team keeps ready for the questions it answers over and over. Refunds, billing disputes, order status, angry customers, outages, SaaS bugs, SLA breaches, security reviews, SSO and MFA, B2B onboarding, escalations, closing the loop. Copy one, replace the brackets, send. 12 of them have a chat version as well as the email version. And the honest line where canned responses stop being the right tool.
templates
69
scenarios
17
chat versions
12
Last updated 11 September 2026. Free to copy — no sign-up, no email wall.
What is a canned response?
A canned response is a pre-written reply an agent sends for a question the team answers over and over: a refund request, a return, a password reset, an outage notice. It is called canned for the same reason as the food, prepared in advance and stored, ready to open. Helpdesks call them saved replies, macros or snippets; the good ones hold the structure and the facts, and the agent edits in the specifics before sending.
Why most canned responses fail
Not because they are canned. Because most canned responses are written to protect the company instead of to answer the person. Thank you for reaching out. We apologize for any inconvenience this may have caused. Your satisfaction is our top priority. Nobody has ever said those sentences out loud to another human being, and customers read them as what they are: a form letter wearing a name tag.
Good canned responses do the opposite. They answer in the first four words, state the specific fact or decision, give one clear next step with a date on it, and leave room for the agent to add the one detail that proves a human read the message. Every template below follows that shape. Every one takes a position, including the uncomfortable ones where the answer is no.
Three editing rules before you copy anything. Replace every bracket, because a leaked [first name] does more damage than no template at all. Cut any sentence you would not say across a table. And read it once as the customer, in the mood they are in, before you send it.
How this library is organized
There are 17 scenario categories and 6 families. Each template includes a title and a one-line “when to use”. The body of the template carries every variable in [brackets], for names, dates, amounts and links. 12 of the templates also include a chat version below the email version, because the same scenario often takes one line on live chat and four sentences in an inbox.
Figure 1. What the library covers: 69 templates across 6 scenario families.
Ecommerce and orders 7%
Money 23%
Emotion and escalation 13%
Product and incidents 20%
Access and security 18%
Onboarding, queue and closing 19%
Percentages are rounded to whole numbers and sum to 100; the table beneath carries the exact template counts.
The 69 templates by scenario family, with the categories in each family.
Family
Categories
Templates
Share
Ecommerce and orders
Order status and shipping
5
7%
Money
Refunds and billing · Billing disputes and invoices · Subscriptions: pause, downgrade, cancel
16
23%
Emotion and escalation
The angry customer · Escalations · SLA breaches and missed promises
9
13%
Product and incidents
Outages and incidents · Product questions and bugs · SaaS bugs and regressions · Feature requests and the roadmap
14
20%
Access and security
Account and access · Team access: SSO, MFA and admins · Security, privacy and compliance
12
18%
Onboarding, queue and closing
B2B onboarding and go-live · Queue management and closing · Closing the loop
The one category where canned responses are the second-best tool. A template can only say what is true for everyone. If you can pull the customer's live order status instead, do that. These are for when you cannot.
1
Order status, tracking exists
When to use: The order shipped and there is a tracking link to give.
Email
Hi [first name],
Your order [order number] shipped on [date] with [carrier]. Track it here: [tracking link].
The current estimate is [delivery date]. If that date passes and nothing arrives, reply to this email and I will chase the carrier myself.
[Your name]
Chat
Hi [first name] — [order number] shipped [date] with [carrier], due [delivery date]. Tracking: [tracking link]. If that date passes with nothing, message me here and I will chase the carrier.
2
Order delayed, tracking has gone quiet
When to use: The scan history stalled and the customer noticed before you did.
Email
Hi [first name],
You are right, your package has not scanned since [date]. That usually means it is moving between carrier hubs without being logged, not that it is lost.
Here is what I have done: opened a trace with [carrier] and set a reminder to check it on [date]. If there is no movement by then, I will send a replacement or a refund, your choice. You will hear from me either way.
[Your name]
3
Package marked delivered, customer has nothing
When to use: The scariest WISMO variant. Lead with belief, not with a checklist.
Email
Hi [first name],
I believe you, and I am sorry. A package marked delivered that is not there is maddening.
Two quick checks while I open a claim with [carrier]: neighbors and any safe spot the driver uses, since drivers sometimes scan before the doorstep. If it has not turned up within [timeframe], I will ship a replacement at no cost. You do not need to fight the carrier. That is my job.
[Your name]
4
Return instructions
When to use: A standard return request inside the return window.
Email
Hi [first name],
Done, your return is approved. Here is the whole process:
1. Print the prepaid label attached to this email.
2. Pack the item with its tags or accessories.
3. Drop it at any [carrier] location within [number] days.
Your refund of [amount] goes back to your original payment method within [number] business days of the warehouse scan. I will email you when it lands.
[Your name]
5
Exchange, requested item out of stock
When to use: You cannot give them what they asked for. Say so in the first sentence.
Email
Hi [first name],
Bad news first: the [item] in [size or color] is out of stock, so a direct exchange is not possible right now.
Three options, pick whichever suits you:
1. A full refund of [amount], processed today.
2. Store credit of [amount plus bonus] as a thank you for the hassle.
3. I can email you the moment it restocks, expected [date].
Reply with 1, 2 or 3 and I will handle it same day.
[Your name]
Money questions get read twice and forwarded to spouses. Every number in these canned responses needs to be exact before you hit send.
6
Refund approved
When to use: The request qualifies. Lead with the yes.
Email
Hi [first name],
Yes, refund approved. [Amount] is on its way back to your [payment method] and should appear within [number] business days. Banks add the delay, not us, so if day [number] passes without it, reply here and I will send you the transaction reference to give them.
Sorry it did not work out this time.
[Your name]
Chat
Refund approved. [Amount] is on its way back to your [payment method], usually [number] business days. If it is not there by [date], come back to me and I will send you the transaction reference.
7
Refund declined, outside policy
When to use: You have to say no. Say it early, explain once, and offer what you can.
Email
Hi [first name],
I am sorry, I cannot refund this one. Your order was delivered on [date], and our return window is [number] days, which closed on [date]. I checked for wiggle room before writing this and there is not any I can offer.
What I can do: [alternative, e.g. store credit, a discount on a replacement, troubleshooting help]. If the item is faulty rather than unwanted, tell me, because that is a different policy and a different answer.
[Your name]
8
Refund in progress, customer chasing it
When to use: They were promised a refund and it has not landed yet.
Email
Hi [first name],
Your refund of [amount] was issued on [date], reference [transaction ID]. It is real and it is moving.
Banks typically post it within [number] business days, which means [date] at the latest. If it is not there by then, send me a note and I will escalate with our payment provider the same day.
[Your name]
9
Duplicate charge
When to use: The customer was billed twice. Fix first, explain second.
Email
Hi [first name],
You are right, you were charged twice on [date], and I have already refunded the duplicate [amount]. It will be back on your card within [number] business days.
Why it happened: [one honest sentence, e.g. the payment retried after a timeout]. It will not recur, and I am sorry we made you do the accounting for us.
[Your name]
10
Failed payment, account at risk
When to use: Dunning. Be a helpful human, not a warning label.
Email
Hi [first name],
Heads up: your payment of [amount] on [date] did not go through, usually an expired card or a bank decline. Nothing is broken and your account is untouched so far.
Update your card here: [billing link]. If nothing changes by [date], your plan pauses, and everything comes back the moment a payment lands. If the charge failed for a reason we caused, reply and I will sort it.
[Your name]
11
Cancellation, confirmed without a fight
When to use: They asked to cancel. Do it, then leave one door open.
Email
Hi [first name],
Done. Your subscription is cancelled and you will not be charged again. You keep access until [date], and your data stays exportable for [number] days after that.
No survey, no retention offer. One question, only if you feel like answering: what was the moment you decided to leave? One sentence helps us more than any form.
[Your name]
Disputes are a refund with a lawyer in the room. The number one rule that keeps you out of trouble is the boring one: never argue about a number you have not opened the account and checked. Every template here assumes you have done that.
12
Chargeback filed, asking them to withdraw it
When to use: The bank told you before the customer did. Be useful, not wounded.
Email
Hi [first name],
Your bank told us you disputed the charge of [amount] from [date]. That is your right and I am not going to argue with you about it.
One thing worth knowing: a chargeback takes [number] to [number] days to resolve and locks the money in the meantime. If the problem is [likely cause, e.g. an unrecognized descriptor, a renewal you did not expect], I can refund it directly today, which is faster for you than the bank's process. Tell me which you would rather do and I will act on it either way.
[Your name]
Chat
Your bank flagged a dispute on the [amount] charge from [date]. Happy to sort it directly if you would rather: a refund from us lands today rather than at the end of the bank's [number]-day process. Which would you prefer?
13
Copy of an invoice, with tax details
When to use: Finance asked them for paperwork. Give all of it in one message.
Email
Hi [first name],
Invoice [invoice number] for [amount] on [date] is attached, and every past invoice is downloadable any time at [billing link].
It already shows our legal entity, address and [tax ID label, e.g. VAT number]. If your finance team needs your own [tax ID label], a PO reference or a different billing address on it, send me the exact text and I will reissue it today with the same number.
[Your name]
14
Disputed charge, you need to check before deciding
When to use: They may be right and you do not know yet. Do not promise, do not stall.
Email
Hi [first name],
I am looking at the charge of [amount] on [date] now. I do not want to give you an answer I have to take back, so here is the honest state: I need to check [what you are checking] before I can tell you whether it stands.
That takes me until [specific time]. You will hear from me then with a yes or a no and the reasoning, not with another holding message. I have put a hold on further charges while I look.
[Your name]
15
Price increase, customer pushing back
When to use: The increase is real and it is not being reversed for one person. Say that kindly.
Email
Hi [first name],
Fair question, and I would rather answer it straight than send you the announcement again. Your plan goes from [old amount] to [new amount] on [date], a [number]% change, the first since [date or 'you joined'].
I cannot hold your old price, and I am not going to pretend I am asking someone. What I can do: [concrete option, e.g. move you to annual billing at the current rate, or down to the plan that covers what you actually use]. If the new number does not work for you, tell me and I will help you export cleanly rather than let it fail at renewal.
[Your name]
16
Proration confused the customer
When to use: An upgrade mid-cycle produced a charge that looks wrong and is not.
Email
Hi [first name],
That invoice is right, and it is genuinely confusing. Here is the arithmetic.
You upgraded on [date], [number] days into a [number]-day cycle. We credited the unused part of [old plan], [amount], and charged the remaining days of [new plan], [amount]. Net today: [amount]. From [next billing date] it settles at [amount] every cycle and stays there.
If that does not match what you see, send me a screenshot of the line you are looking at and I will walk through it with you.
[Your name]
You may be tempted to make leaving hard. That works about as well as a locked exit door in a restaurant. Ask once, at most, and only if you have something real to offer. Then do what they asked in the same message.
17
Pause instead of cancel, offered once
When to use: A seasonal or temporary reason to leave, and you actually have a pause.
Email
Hi [first name],
I can cancel this today, and I will if you say so. Before I do, one option you may not know about: I can pause your account for up to [number] months. No charges while paused, your data and settings stay exactly as they are, and one click brings it back.
Since you mentioned [their reason], pausing may fit better than starting over later. Reply pause or cancel and I will do it in the next few minutes. No follow-up either way.
[Your name]
Chat
I can cancel that right now if you want. One option first: a pause for up to [number] months, no charges, everything kept exactly as it is. Say pause or cancel and it is done in a minute.
18
Downgrade confirmed
When to use: They want a smaller plan. Tell them exactly what they lose, before they find out.
Email
Hi [first name],
Done, you are on [new plan] from [date] at [amount] per [period].
What changes for you: [feature or limit] drops to [number], and [feature] is no longer included. Nothing is deleted, it just becomes read-only, so if you go back up it is all still there. Your next invoice is [amount] on [date].
If any of that is a surprise, tell me now rather than at the end of the month.
[Your name]
19
Cancelling and asking for the unused period back
When to use: They cancelled mid-cycle and want the remainder refunded.
Email
Hi [first name],
Cancelled, and you will not be charged again.
On the refund for the rest of the cycle: our policy is [policy in one plain sentence]. In your case that means [the actual answer for them, with the amount and the date]. If the answer is no, you keep full access until [date], so the time is not lost even though the money is not coming back.
If you cancelled because something broke rather than because you were done with it, say so, because that is a different conversation and I would like to have it.
[Your name]
20
Annual plan, wants out mid-term
When to use: The commitment is real. Do not hide behind the contract, and do not give away the company.
Email
Hi [first name],
Straight answer: your annual term runs to [date] and the [amount] for it is non-refundable under [the agreement you both signed]. I am not going to bury that in a paragraph.
What I can offer, in order of how much it helps you: [option 1, e.g. transfer the remaining term to another team in your company], [option 2, e.g. pause and resume the balance later], [option 3, e.g. credit against a future restart]. If none of those work, you keep everything until [date] and I will make sure the export is clean before then.
[Your name]
21
Win-back, only because they asked to be told
When to use: They left over a specific missing thing and asked to hear when it landed. Never send this otherwise.
Email
Hi [first name],
When you left in [month], you said the blocker was [the specific thing]. That shipped on [date], and you asked to be told, so here I am, once.
What it does now: [one or two plain sentences]. If you want to look, your old account and its data are still there until [date] and [link] takes you straight in. If not, no hard feelings and this is the last email you will get from me about it.
[Your name]
The template holds the structure so your head can stay calm. Acknowledge specifically, own it plainly, give a time-boxed next step. Never paste one of these unedited, because an angry customer can smell a macro through the screen.
22
First reply to an angry message
When to use: Heat in the inbox. Reply fast, even before you have the fix.
Email
Hi [first name],
You are right to be frustrated, and I am sorry. [Restate their specific problem in one sentence, in your words, so they know a human read it.]
Here is what happens next: I am [specific action] right now and will have an answer for you by [specific time]. If I miss that time, you will still hear from me at that time with a status.
[Your name]
23
Follow-up with the fix
When to use: You promised an answer by a set time. This is that message.
Email
Hi [first name],
As promised, here is where things stand. The problem was [plain-language cause]. I have [what you did], and on your side [what changes for them, or nothing needed].
To make up for the trouble: [gesture, sized to the harm]. And if any part of this is not actually fixed for you, reply directly to me, not to the queue.
[Your name]
24
We were plainly in the wrong
When to use: No spin available. Take the hit in the first line.
Email
Hi [first name],
We got this wrong. Not a misunderstanding, not an edge case. [One sentence naming exactly what your company did.]
Here is the repair: [refund, replacement, or fix], done today. Here is what changes so it does not happen to the next person: [one concrete change]. Thank you for telling us instead of quietly leaving.
[Your name]
An escalation is when a customer tells you that your current path is not working. Do not argue about whether they are right. Arguing spends the one thing they have left, which is time. Move it, name who has it now, and give a time.
25
Escalating to a manager, as asked
When to use: They asked for your manager. Do it without defending yourself.
Email
Hi [first name],
Yes, of course. I have passed this to [manager name], [role], with the full history so you do not have to repeat any of it.
They will reply to you by [specific time]. I have also written down what I think went wrong from our side, so the review starts from an honest account rather than my version. If anything I did made this worse, I would rather they hear it from me.
[Your name]
Chat
Passing this to [manager name], [role], now, with the full history so you do not repeat yourself. They will come back to you by [time].
26
Escalating to engineering, and saying what that means
When to use: It has left support. The customer deserves to know what changes and what does not.
Email
Hi [first name],
This is now with our engineering team as [ticket reference], raised at [priority level].
What that means in practice: they investigate the cause rather than the symptom, which is slower and more permanent. What it does not mean is that you now wait in silence. I stay your contact, and I will send you an update every [interval] until it closes, including the updates that say nothing has changed.
Current expectation: [timeframe, or say honestly that you do not have one yet and name the date you will].
[Your name]
27
An executive complaint arrives over the top of the queue
When to use: Someone senior on their side wrote to someone senior on yours. Answer as the owner, not the messenger.
Email
Hi [first name],
[Executive name] forwarded your message to me and I own it from here.
What I can already confirm: [the facts you have verified, in one or two sentences]. What I do not yet know: [the honest gap]. I am not going to fill that gap with a guess at your expense.
You will have a full account and a decision from me by [specific time]. If [executive name] should be on that reply, say so and they will be.
[Your name], [role]
The hardest message in support is the one where you are late and you have to say so first. The difference between a missed target and a lost customer is sending this message before the customer chases you down. None of these templates apologize twice.
28
We missed the first response time we promised
When to use: The clock ran out before anyone replied. Send this the moment you notice.
Email
Hi [first name],
We promised a first reply within [number] hours and you waited [actual duration]. That is on us and I am not going to explain it away.
I have read your message in full and here is where I actually am: [substantive first answer, because a late apology with no answer is two failures]. Next step is [action] by [time].
The reason, for what it is worth: [one honest sentence]. What changed today so it does not repeat: [one concrete thing].
[Your name]
Chat
We owed you a reply within [number] hours and took [actual duration]. Sorry. Here is where I am on the actual question: [answer]. Next step [action] by [time].
29
We missed the resolution deadline and it is still open
When to use: The fix date passed and there is no fix. Do not move the date silently.
Email
Hi [first name],
I told you this would be resolved by [original date]. It is not, and I should have told you that before the date passed rather than after.
Where it actually stands: [plain status]. What is blocking it: [the real blocker, named]. My new estimate is [new date], and I am giving you the reasoning so you can judge it yourself: [one sentence].
If that date matters to something on your side, tell me what it is and I will say honestly whether we can meet it or whether you should plan around us.
[Your name]
30
SLA credit, offered before it is asked for
When to use: The contract entitles them to something. Give it without being invoiced for it.
Email
Hi [first name],
Our agreement commits us to [the target] and we delivered [the actual] in [period]. That triggers a credit of [amount], which I have applied to your account today. You did not have to ask and you should not have had to.
The credit is the small part. The larger part is [what you changed], which is in place as of [date]. If you want the incident detail behind the numbers, say the word and I will send the summary.
[Your name]
During an outage, speed beats polish and honesty beats both. These three canned responses are built to send fast: use the first one before you fully understand the problem, and say that you do not fully understand it yet.
31
First acknowledgment, cause unknown
When to use: Within minutes of confirmed impact. Do not wait for a diagnosis.
Email
Hi [first name],
You are not imagining it: [product or feature] is currently down, and it is affecting other customers too, not just you. We are on it now.
I do not yet know the cause, so I will not guess. Live updates are at [status page link], and I will reply here the moment it is restored. You do not need to keep testing it.
[Your name]
32
Mid-incident update
When to use: Every 30 to 60 minutes during a long outage, even with nothing new.
Email
Hi [first name],
Update on the [product] outage: we have identified [what is known] and a fix is in progress. Current estimate for restoration is [time], and I will correct that estimate if it moves.
Your data is safe and nothing on your side needs to change. Next update by [time] regardless of progress.
[Your name]
33
Resolved, with the plain-language postmortem
When to use: Service is restored and verified. Close the loop with everyone who wrote in.
Email
Hi [first name],
[Product] is back up as of [time], and we have verified your account specifically is working.
What happened, without the jargon: [two sentences a non-engineer can follow]. What we changed so it does not repeat: [one concrete measure]. Total downtime was [duration], and if it caused you a real cost, reply and we will talk about making it right.
[Your name]
The two failure modes here are pretending a bug is user error and promising features that will never ship. These canned responses are built to make both lies harder to type.
34
Bug confirmed
When to use: You reproduced it. Tell them they were right.
Email
Hi [first name],
Confirmed: that is a bug on our side, not something you did. I reproduced it in [context] and it is now with our engineers as [ticket reference].
Workaround until the fix ships: [steps, or say honestly that there is not one]. I will email you on this thread when it is fixed, not just close the ticket.
[Your name]
35
Feature request, honestly logged
When to use: A reasonable ask that is not on the roadmap. Do not say soon.
Email
Hi [first name],
Good idea, and I have logged it word for word for our product team. Honest expectations: I cannot promise it will be built or give a date, and I would rather tell you that than say soon and mean maybe.
What might get you most of the way today: [existing workaround, if one exists]. If this becomes something we ship, you will hear it from me on this thread first.
[Your name]
36
Feature request, declined
When to use: You know it will not be built. The kindest answer is a clear no.
Email
Hi [first name],
Straight answer: we are not going to build this. It pulls against [the product's core direction] and pretending it is under consideration would just waste your patience.
If it is essential to how you work, [alternative tool or approach] handles it well, and I would rather point you somewhere useful than string you along. For what you are trying to do inside our product, [closest existing path] gets you part of the way.
[Your name]
37
How-to question with a doc that answers it
When to use: The answer exists in your documentation. Answer first, link second.
Email
Hi [first name],
Quick answer: [the actual answer in one or two sentences, right here in the email].
The full walkthrough with screenshots is here: [doc link]. And if the doc did not surface when you searched, tell me what you typed, because that means our docs failed you before I could.
[Your name]
Software support has failure modes retail never sees: something that worked on Friday and does not on Monday, a bug that exists only on one customer's setup, a bug that makes data disappear. Each has a template below, and each starts with what you know rather than what you hope.
38
Regression after a release
When to use: It worked before your deploy. The customer is right and you shipped it.
Email
Hi [first name],
You are right, and it is our doing. [Feature] worked until our release on [date] and it does not now. We have reproduced it.
What is happening: [engineering fix, rollback, or both], with a fix expected by [time]. What to do until then: [workaround, or say plainly that there is not one]. Nothing you configured has been lost.
I will message you when it is verified fixed on your account specifically, not when it is merged.
[Your name]
Chat
Confirmed, that broke in our release on [date]. Not you. Fix expected by [time], and until then [workaround]. I will ping you here when it is verified on your account.
39
Bug we cannot reproduce
When to use: You have tried and it works for you. Do not imply they imagined it.
Email
Hi [first name],
I believe you, and I cannot make it happen on my side yet, which means the cause is something specific to your setup rather than something universal.
Three things would close the gap fast: [browser or app version], a screen recording of the exact steps, and the time and timezone of the last time it happened so I can find it in our logs. With those, I can look at your session directly instead of guessing.
If it is intermittent, the timestamp matters more than anything else. Send whatever you have and I will work with it.
[Your name]
40
Data loss or corruption, confirmed
When to use: The worst message in SaaS support. Facts, scope, and what is recoverable, in that order.
Email
Hi [first name],
Confirming what you found: [what was lost, precisely], affecting [scope, e.g. records created between two dates]. This was our fault and I am sorry.
What is recoverable: [the honest answer, with the source, e.g. a backup from [time]]. What is not: [the honest answer, without softening]. Restoring takes until [time] and I will not start it without telling you what it overwrites.
Once you are whole again I will send you the cause and the change that prevents it. Right now the only thing that matters is getting your data back.
[Your name]
41
The cause is a third-party integration, not us
When to use: True, and useless to the customer on its own. Own the fix anyway.
Email
Hi [first name],
Found it: the failures started when [integrated service] changed [what changed] on [date]. It is not something in your account and it is not something you did.
I say that as an explanation, not as a hand-off. We are updating our side to handle the change, expected [date], and I have opened [reference] with them as well. Until then, [workaround].
You should not have to run two support conversations to get one thing working, so keep talking to me and I will carry the other one.
[Your name]
Almost every feature request has one of three answers: it already exists and we hid it, it is coming and you are not getting a date, or it shipped and nobody told you. The fourth answer, a straight no, is in the product questions section above.
42
It already exists, and our docs hid it
When to use: They asked for something you built. The failure is yours, not theirs.
Email
Hi [first name],
Good news and a small confession: that already exists. [Where it is, in one specific path or click sequence].
The confession is that you searched for it and did not find it, which means our documentation failed before you wrote to me. Tell me what you typed when you looked and I will get the wording fixed so the next person finds it without asking.
[Doc link] has the full walkthrough.
[Your name]
43
It is on the roadmap, without a date
When to use: It is genuinely planned. Say planned, never soon.
Email
Hi [first name],
This one is actually on our roadmap, which I say rarely enough that it means something. It is in [stage, e.g. design, in build], and I am not going to give you a date, because every date I have given from this stage has been wrong.
What I will do instead: put you on the list for this specific thing and write to you the week it ships, before the announcement. Between now and then, [closest existing workaround].
If a date is what you need for your own planning, tell me and I will find out what can honestly be committed to.
[Your name]
44
The feature you asked for just shipped
When to use: Months later. The highest-value message in your outbox.
Email
Hi [first name],
In [month] you asked for [the specific request]. It shipped on [date] and you asked first, so you hear first.
How to use it: [one or two sentences, or a path]. It works slightly differently from what you described, in that [the honest difference], so have a look before you rebuild anything around it.
Thank you for the original write-up. It went into the spec more or less as you wrote it.
[Your name]
High urgency, low complexity. Speed is the whole game, which is exactly what canned responses are for.
45
Password reset
When to use: A locked-out customer. Every extra sentence delays them.
Email
Hi [first name],
Reset link: [link]. It works for [number] hours.
If it does not arrive or does not work, reply here and I will reset it manually from our side. If you did not request this, ignore the link and tell me, because someone else may have tried.
[Your name]
Chat
Reset link sent, good for [number] hours: [link]. If it does not arrive, say so here and I will reset it manually. If you did not ask for this, tell me, someone else may have tried.
46
Account deletion and data request
When to use: A departure with legal weight. Confirm scope and dates precisely.
Email
Hi [first name],
Confirming your request: your account and its data will be permanently deleted on [date], which gives you [number] days to change your mind or export anything you need. Export link: [link].
After [date] the deletion is not reversible by you or by us. If you want it done sooner, reply confirm now and I will run it today.
[Your name]
47
Suspicious activity notice
When to use: You spotted something on their account before they did.
Email
Hi [first name],
We noticed a sign-in to your account from [location or device] on [date] that did not match your usual pattern, so we have [action taken, e.g. required a re-verification].
If this was you, sorry for the speed bump, and you are already done. If it was not you, reset your password now at [link] and reply here so a human reviews the account with you.
[Your name]
Business accounts lock differently from personal ones. The person writing to you often cannot prove they own anything, which is also where an attacker would be when you receive the email. Every template here does the same two things: move fast and verify anyway.
48
SSO login failing after an identity provider change
When to use: Their side changed something. Yours is the error message they see.
Email
Hi [first name],
The error you are seeing is [error, in plain words], and it started at [time]. That pattern almost always means a change on the identity provider side, usually [likely cause, e.g. a rotated certificate or a changed attribute mapping].
Two things to check with whoever administers [identity provider]: [check 1] and [check 2]. Meanwhile, I have enabled [temporary access route] for [number] hours so your team is not locked out while that gets sorted.
Send me the request ID from the error screen if you want me to read our side of the exchange.
[Your name]
Chat
That error usually means something changed on your [identity provider] side, most often [likely cause]. I have opened [temporary access route] for [number] hours so nobody is locked out. Can your IdP admin check [check 1]?
49
Lost MFA device
When to use: They cannot get in and cannot prove who they are the easy way.
Email
Hi [first name],
I can reset this, and I have to verify you first, because the same message from someone else would read identically.
Either of these works: your account administrator [admin's role, not name] confirms in writing from their own address, or you complete [the verification path, e.g. our identity check at this link]. Once one of those lands, the reset takes about [duration] and I will walk you through re-enrolling.
If you have a backup code from setup, that skips all of this. Worth checking first.
[Your name]
50
The admin left the company and nobody can get in
When to use: A real business emergency with a real impersonation risk.
Email
Hi [first name],
This is fixable and it will not be fast, and I would rather tell you that now than at step three.
To transfer ownership away from [former admin's role] I need proof the request comes from the company rather than from an individual: [requirement 1, e.g. a request from a verified company domain] and [requirement 2, e.g. written confirmation from a named officer or the billing owner]. Once both are in, the change takes [duration].
I have started the file and put [reference] on it, so nothing has to be repeated. If the account is at risk of lapsing while we do this, tell me and I will hold it.
[Your name]
51
Seat and permission change
When to use: Routine, high volume, and easy to get wrong. Confirm the exact end state.
Email
Hi [first name],
Done. To be certain we mean the same thing, here is the state I have left your account in:
1. [Person or role] now has [permission level].
2. [Person or role] removed, effective [date], and their [work, e.g. assigned conversations] reassigned to [destination].
3. Seat count [number], billed at [amount] from [date].
If any line is wrong, reply with the number and the correction and I will fix it today.
[Your name]
Security and compliance questions arrive late in a deal and on somebody else's deadline, and they come from a person who does not use your product and who decides whether anyone at their company can. That person does not care about adjectives. They care about documents and dates. If you do not have the certification, say no. A security reviewer trusts a clean no far more than a vague yes.
52
Security questionnaire from a prospect's review
When to use: A spreadsheet with 200 rows arrives. Get ahead of it.
Email
Hi [first name],
Happy to complete this. To save your team time, most of it is probably answered already in [the security page or document], which covers [what it covers] and is current as of [date].
Send the questionnaire over and I will return it within [number] business days with every row answered, including the rows where the answer is no. Anything I cannot answer from documentation I will route to [role, e.g. our security lead] rather than guess.
If there is a deadline on your side, tell me the date and I will work to it.
[Your name]
53
Where our data lives
When to use: A data-residency question, usually with a real legal constraint behind it.
Email
Hi [first name],
Direct answer: customer data is stored in [region], with backups in [region]. Processing happens in [region].
If your requirement is that data stays inside [their required region], the honest position is [the true answer, including 'we cannot do that today' if that is the case]. I would rather you find that out from me now than from an auditor later.
[Document or page] has the detail your reviewer will want, including subprocessors and retention periods.
[Your name]
Chat
Customer data sits in [region], backups in [region], processing in [region]. If you need it to stay inside [their region], the honest answer is [answer]. Full detail is in [document] if your reviewer wants it.
54
Subprocessor list, and a change notice
When to use: Contractual, dull, and the kind of thing that loses renewals when handled badly.
Email
Hi [first name],
The current subprocessor list is at [page], last updated [date], with what each one processes and where.
One change to flag: from [date] we [add or remove] [subprocessor] for [purpose]. Under [the agreement] you have until [date] to object. Nothing about your data changes in the meantime and I will confirm here once the change is live.
If your legal team wants the notice in a particular format, send me the template and I will fill it in.
[Your name]
55
Data processing agreement or a privacy request
When to use: Legal on their side, deadlines that are not negotiable.
Email
Hi [first name],
Our standard [agreement name] is at [link], already signed on our side, so countersigning is usually the whole process. If your team needs changes, send the redline and I will get it to [role] rather than negotiate it in an inbox.
On the request itself: [access, export, deletion] for [subject scope] takes us [duration] and the statutory clock ends [date]. I have logged it as [reference] and will confirm here when it completes.
[Your name]
56
Vulnerability report from a researcher
When to use: An unsolicited security report. Answer quickly and without defensiveness.
Email
Hi [first name],
Thank you, genuinely. This is with our security team as [reference] as of [time], and I am your point of contact until it closes.
What happens next: we validate, we fix, and we tell you what we found either way, including if we conclude it is not exploitable. Our disclosure policy and scope are at [link]. Please hold off on publishing until [date or 'we have confirmed the fix'], and tell me if that timeline does not work for you rather than assuming we will be difficult about it.
[Your name]
The onboarding message gets the most careful reading. The customer is still deciding whether they made a good decision. Keep it short, specific, and never have a checklist of things you need from them, but always include one thing that you have already done.
57
Kickoff, what happens in week one
When to use: The contract is signed. Replace the welcome email that says nothing.
Email
Hi [first name],
Welcome. Here is week one, so nothing is a surprise.
1. Today: your workspace is live at [link] and [number] seats are ready. Nothing else is needed from you yet.
2. [Day]: [the setup call or the import], [duration], with [role]. Bring [the one thing you need from them].
3. [Day]: you send your first [real usage], and I watch it with you.
I am your contact for all of it, on this thread. If something is unclear before then, it is worth asking rather than working around.
[Your name]
58
Data import ready for review
When to use: You migrated their data. Show the numbers before they find a gap.
Email
Hi [first name],
Your import from [source] is done and ready for you to check at [link].
The numbers: [number] [records] imported, [number] skipped. The skips were [reason], and the list is at [link] so you can decide whether any of them matter. [Anything that changed shape in the move, stated plainly].
Have a look and tell me by [date] if anything is missing. It is much cheaper to re-run this now than after your team starts working in it.
[Your name]
59
Training session follow-up
When to use: Right after the call, while it is still in their head.
Email
Hi [first name],
Good session. Three things we said we would do:
1. [Action you own], by [date].
2. [Action they own], whenever suits.
3. [Open question], which I am checking with [role] and will answer by [date].
The recording is at [link] and the two things people forget in week one are [thing] and [thing]. Everything else can be looked up.
[Your name]
60
Go-live day, and who to reach
When to use: The day it becomes real. Make the escalation path obvious before it is needed.
Email
Hi [first name],
You are live as of [time]. [What is now switched on, in one sentence].
For today: I am watching your account directly and replying on this thread within [number] minutes during [hours]. If something is urgent outside those hours, [the escalation route]. Anything cosmetic can wait until tomorrow and I will collect it in one list.
One week from now I will send you what actually happened, with the numbers, and we will decide what to change.
[Your name]
Chat
You are live as of [time]. I am watching your account today and answering here within [number] minutes during [hours]. Outside those hours, [escalation route]. Anything cosmetic, send it over and I will batch it.
The unglamorous canned responses that keep an inbox honest. Most teams improvise these fresh every time, which is how sat here for three days with no reply happens.
61
Need more information
When to use: You cannot act on what they sent. Ask for everything at once.
Email
Hi [first name],
I want to fix this on the next message, so I need three things in one reply:
1. [Specific detail]
2. [Specific detail]
3. A screenshot of [specific screen], if you can.
The moment those arrive, this goes to the front of my queue. Asking for everything at once beats four rounds of one question each.
[Your name]
62
Backlog acknowledgment, replies running slow
When to use: Peak season or an incident aftermath. Buy time by being honest about it.
Email
Hi [first name],
Your message is in our queue and a real person will answer it. Honest timing: we are running about [number] hours behind right now because of [plain reason], and you can expect a reply by [date].
If your question is about [top current issue], the answer is probably here: [link]. If it is urgent in the meaning of money or access, reply with URGENT and it will be pulled forward.
[Your name]
Chat
You are in the queue and a person will answer. Honest timing: we are about [number] hours behind because of [plain reason], so expect a reply by [date]. If this is about money or access, say URGENT and I will pull it forward.
63
Closing a resolved conversation
When to use: The problem is fixed and confirmed. Close it warmly and stop.
Email
Hi [first name],
Glad that is sorted. I am closing this conversation now, and replying to this email reopens it instantly with the whole history intact, so you never have to explain from scratch.
Thanks for your patience while we worked through it.
[Your name]
64
Follow-up after silence
When to use: You answered, they went quiet, and the ticket is aging.
Email
Hi [first name],
Checking in once: did my last message fix things, or did it miss?
If I do not hear back by [date], I will close the conversation so it does not nag you, and any reply after that reopens it automatically. Silence will be taken as good news, but only this once.
[Your name]
65
Replying to a public negative review
When to use: Public, permanent, and read mostly by future customers, not the reviewer.
Email
Hi [name],
You are right about [the specific failure], and I am sorry. That was our mistake, not a misunderstanding.
I have sent you a direct message to make it right, and here is what we changed because of your review: [one concrete change]. Anyone reading this later: this is what our worst day looks like, and this is how we respond to it.
[Your name], [role]
These are the messages that nobody sends, because the ticket is already closed and nothing forces them. They cost a minute each and they are the reason why a customer describes your support as good years later. Send them.
66
The bug you reported is fixed
When to use: Weeks or months after the ticket closed. Reopen the thread on purpose.
Email
Hi [first name],
You reported [the bug] back on [date]. It is fixed as of [date] and I said I would tell you, so I am.
What changed: [one plain sentence]. Nothing on your side to do. The workaround you have been using still works, but you can drop it.
Thank you for the report. It was a good one and it was specific enough to find the cause.
[Your name]
67
The incident change we promised is done
When to use: You said you would prevent a repeat. Prove it, unprompted.
Email
Hi [first name],
After the [incident] on [date] I told you we would [the promised change]. That went in on [date].
Concretely: [what is different now, in a sentence a non-engineer can check]. It does not undo the [duration] you lost that day, and it does mean the same cause cannot produce the same outage.
No action needed. I just do not think a promise like that should be something you have to chase.
[Your name]
68
Your refund landed
When to use: The money arrived. Tell them so they stop checking.
Email
Hi [first name],
Your refund of [amount] settled on [date], reference [transaction ID]. You can stop watching your statement.
If your bank still shows nothing, that reference is what they will ask for, and I am here if you need me to chase it from our end.
[Your name]
69
What we changed because of your feedback
When to use: A customer complained about something structural and you actually fixed it.
Email
Hi [first name],
In [month] you told us [the criticism, in their words as far as you can]. It was fair and it stung a little, which is usually the sign.
What is different now: [the change, specific and checkable]. It is not everything you asked for, and [the honest remaining gap].
You did not have to take the time to explain it. This is what it turned into.
[Your name]
Most of the 69 templates above are written as emails, because that is where the awkward messages go. A refund decline, a missed deadline, a security answer and a data-loss confirmation all need a paragraph and a record. Chat gets the fast ones, and 12 of the templates have a chat version for that reason.
Three things change when a canned email response goes out instead of a chat reply:
The subject line does work. Put the decision in it. “Refund approved, [amount]” beats “Re: my order” and saves the customer opening it to find out whether they won.
It will be forwarded. Somebody's partner, finance team or lawyer may read your canned email response before you hear back. Write every one as though it will be quoted, because the good ones are.
There is no typing indicator. On chat, silence is visible and short. In an inbox, silence is a week. Every email template above ends with a date or a time on the next step for that reason.
Where the templates live. In a helpdesk they are saved replies or macros. In Gmail, they are templates: turn on Templates in Settings, then Advanced, write the message, and save it from the three-dot menu in the compose window. In Outlook, the equivalent is Quick Parts or My Templates in the newer clients. The mechanics differ, but the writing is the same, and the writing is what decides whether the customer notices.
The same question arrives fourteen ways
Here is one reason a library needs to be wide rather than deep. Over the 90 days to 3 September 2026, our own Search Console recorded 14 distinct phrasings landing on this page: canned responses, canned answers, canned email response templates, customer service canned responses, live chat canned responses examples, and nine more. All for the same request. And 3 of those 14 contained the word email.
Figure 2. The same question, 14 ways. Search queries that reached /guides/canned-responses, Outlearn's own Search Console, 90 days to 3 September 2026. Impressions per query; the 3 phrasings containing "email" are highlighted.
Phrasing contains "email"
Other phrasings
42 impressions in total, 0 clicks, average position around 60. Exact figures, with the average position per query, in the table beneath.
Search queries that reached this page in Outlearn's Search Console, 90 days to 3 September 2026, with impressions and average position.
Search query
Impressions
Average position
best canned responses
7
31
canned response examples
6
62
canned answer
4
52
customer service canned responses
4
45
canned email responses
3
60
canned responses
3
60
canned responses examples
3
61
canned responses for customer service
3
45
canned answers
2
55
canned email response
2
69
canned email response templates
2
61
customer support canned responses
1
53
live chat canned responses examples
1
59
what is a canned response
1
50
Total
42
—
Two honest notes on that table. The numbers are small because the page was 29 templates sitting at position 60, and nobody clicks position 60. And publishing our own weak search data on our own marketing page is unusual, but it is the clearest explanation we have for why the library went from 29 examples to 69: people were asking for more than we had written.
When a canned response is the wrong tool
There is a clean line through every scenario above, and it is worth knowing even if you never automate anything. Canned responses work when the correct answer is the same for everyone: your refund policy, your return steps, what happens during an outage. They break when the correct answer depends on that customer's own data. Look at the order status templates again. The honest ones hedge, because the template cannot know where the package actually is. The customer does not want your shipping policy. They want the fact. There is a middle ground as well, where agent assist drafts the reply from your knowledge and a person still decides to send it.
Questions on the data side of the line, like order status, account state, plan limits and billing history, are where AI agents connected to live systems earn their keep, because they can look up the specific answer and reply in seconds at any hour. The clearest case is ecommerce: order lookups on a Shopify store answer with the order's actual status, not the shipping policy. That is what we build at Outlearn, and this library stays free and useful whether or not you ever try it. Plenty of teams run happily on templates alone. The point is to stop asking templates to do a lookup's job, and to stop paying a person to do a template's.
A practical split for a team of any size: templates for policy and emotion, automation for facts and lookups, humans for judgment. The angry customer templates above should never be fully automated. The password reset should never touch a human. The first metric that split moves is average handle time, because templates cut the typing and lookups cut the searching.
There is a third failure a template cannot fix, and it is the one that made us build Outlearn. Half the messages above end with the agent promising to do something: issue the refund, apply the credit, open the seat, pause the subscription. A template can write the sentence. It cannot take the action. Outlearn reads the documentation you already keep, answers from it, and then carries out the action inside the conversation rather than describing the form the customer should go and fill in. When it should not act, it hands over to a person with the full transcript attached, so nobody starts by asking the customer to explain again. Templates for the words, lookups for the facts, actions for the work, and a handoff to a human for everything that deserves one.
Questions people ask about canned responses
What are canned responses?
Canned responses are pre-written reply templates for the questions a support team answers repeatedly: refunds, order status, password resets, outage notices. Most helpdesks call them saved replies, macros or snippets. The good ones hold the structure and the facts while the agent edits in the specifics before sending.
What does it mean to give a canned response?
It means replying with a prepared template instead of writing the answer from scratch. Done well, the agent picks the template for the scenario, replaces the brackets with the customer's details, and adds the one line that proves they read the message. Done badly, the customer gets a paragraph that answers a question they did not ask.
Why is it called a canned response?
Same reason as canned food: it was prepared in advance and stored, ready to open and serve. The word carries a sneer in everyday use, which is fair, because a template sent without editing tastes like it came from a can. The examples on this page are built to be edited, not served straight.
What is canned communication?
Any pre-written message a company reuses: saved replies in a helpdesk, macros, chat snippets, auto-replies, outage notices. Canned responses are the support-team subset, the templates an agent sends by hand. The line to watch is the one this page keeps returning to: canned communication works when the answer is the same for everyone and fails when it depends on the customer's own data.
Do customers know when they get a canned response?
Yes, when it is a bad one. The tells are answers that do not address the specific question, greetings that skip the name, and phrases nobody says out loud. A well-edited template is invisible because it reads like a person who has answered this before, which is exactly what it is.
How many canned responses does a support team actually need?
Fewer than you think. Pull your last 200 tickets, sort by topic, and write canned responses for the top 15 to 25 scenarios. That usually covers 60 to 80% of volume. A library of 200 canned responses fails because nobody can find the right one faster than typing.
When is a canned response the wrong tool?
When the correct answer depends on the customer's own data. Order status, account state, plan limits, billing history. A template can only say what is true for everyone, so for those questions it degrades into check your email or let me look into that. That is the boundary where AI answers connected to live systems take over.
Should I let AI write my canned responses?
Draft, yes. Send, no, at least not unedited. Have it draft canned responses against real past tickets, then cut every sentence you would not say across a table. The templates on this page are free to copy and edit, and they will beat a generic generated draft because each one takes a position.
Can you provide an example of a canned response?
Here is one of the shortest on the page: "Reset link: [link]. It works for [number] hours. If it does not arrive or does not work, reply here and I will reset it manually from our side." Two sentences, one action and one fallback, and the only thing that changes between customers is what goes inside the brackets. The other 68 are above, grouped by scenario.
What is a canned question?
A canned question is the same idea in reverse: a question you have saved and reuse whenever you need the customer to tell you something. The "need more information" template above is one of them. It works because it asks for everything at once instead of one thing per round trip, which is what turns a five-message exchange into two. Survey forms and chatbot menus are canned questions too.
What is a canned AI response?
A canned AI response is a machine-generated reply that is fluent, generic and not about the customer. It happens when the model is asked to answer without access to the customer's account or your documentation, so it returns the average of everything ever written about the topic. The cure is not better prompting, it is giving the system the specific facts, which is the same rule as the section above.
How do I do canned responses in Outlook?
Outlook does not use the phrase. The closest thing is Quick Parts, which stores blocks of text that you insert while composing, or My Templates, which is an add-in that stores short reusable replies in the side panel. Both hold plain text only, so if you leave a bracket in a canned response in Outlook, you are the one who has to remember to fill it in. Gmail's version is called Templates and sits under Settings, then Advanced.
Templates handle the policy questions. See what happens when the fact questions answer themselves.
Outlearn reads your docs and your live systems, answers customers directly, takes the action in the conversation, and hands off to a person with the full transcript when it should not act. No card required on the free tier.