What is a canned response in customer service?

A canned response is a pre-written reply an agent inserts for a recurring situation, like acknowledging a new ticket or asking for an order number. It saves typing time, but it only works when the agent personalizes it with case-specific details before sending.

How do you make canned responses not sound robotic?

Write them the way one competent agent would actually type, keep them under four sentences, leave placeholders for at least one case-specific detail, and refresh the wording every few months. If a customer could tell two different people received the identical message, it needs editing.

How many canned responses should a support team have?

Most teams do well with 15 to 30. Fewer and agents retype the same things; many more and nobody can find the right one. Cover your five most common moments first: acknowledging, updating, asking for info, resolving, and closing.

Can AI replace canned responses?

AI drafting replaces the brittle part, which is one frozen wording per situation. Instead of inserting the same paragraph every time, you paste the conversation and generate a fresh draft that covers the same ground with the customer's specifics already included. Many teams use both: canned responses for one-liners, AI drafts for anything longer.

15 Canned Responses That Don't Sound Canned

Canned responses have a bad reputation they mostly earned. Everyone has received the “Dear valued customer, thank you for contacting us” reply that answers nothing and sounds like it was written by a committee in 2009. But the fix isn’t abandoning canned responses; no support team survives typing every acknowledgment from scratch. The fix is writing better ones and personalizing them fast.

Below are 15 canned response examples grouped by the five moments where they earn their keep: opening a ticket, updating status, asking for information, delivering a resolution, and closing. Fifteen, not a hundred: giant template dumps look generous but nobody can find the right one under pressure, and unfindable templates get replaced by improvisation. Each of these is short on purpose. A canned response should be a skeleton you dress in ten seconds, not a wall of text you’re afraid to touch.

After the templates, we’ll cover the ten-second personalization routine and how a tone-rewrite pass keeps your library from going stale.

Openers: received and looking into it

The job of an opener is to kill uncertainty. The customer now knows a human has the ticket, nothing more.

1. Received, on it

Hi [Name], thanks for the details. I’ve got your ticket and I’m looking into [specific issue] now. You’ll hear from me by [time/date] even if I don’t have a full answer yet.

2. Received, complex issue

Hi [Name], I’ve read through what happened with [specific issue]. This one needs some digging on our side, so I want to set expectations: I’ll have a proper update for you by [date]. If anything changes before then, I’ll write sooner.

3. Received, wrong queue

Hi [Name], thanks for reaching out. Your question about [topic] is handled by our [team] team, so I’ve moved it over with all the context you’ve provided; no need to repeat anything. [Teammate/Team] will reply within [timeframe].

Note the pattern: every opener commits to a next contact time. An acknowledgment without a deadline just postpones the customer’s anxiety.

Status updates

Silence is where trust dies. These exist so “no news yet” still gets sent.

4. Still working, no news

Hi [Name], quick update on [issue]: still working on it. So far we’ve [what’s been checked/done], and the next step is [next step]. I’ll update you again by [date]. Nothing needed from you right now.

5. Progress, partial answer

Hi [Name], an update on [issue]: we’ve confirmed [finding]. That means [what it means for the customer in plain terms]. We’re now [remaining step], and I expect to close this out by [date].

6. Delay, revised timeline

Hi [Name], I told you we’d have this resolved by [original date], and we won’t. I’m sorry. [One-sentence honest reason.] The new date is [date], and I’ll check in on [interim date] either way.

Template 6 does double duty as a micro-apology. When the delay caused real damage, escalate to a full apology instead; we’ve broken down that structure in how to write an apology email to a customer.

Asking for information

Ask for everything you need in one message. Nothing burns customer patience like four rounds of “one more thing.”

7. Logs or error details

Hi [Name], to pin this down I need two things: the approximate time it last happened (with timezone), and [the log file / the exact error text, and where to find it: settings menu, path]. With those I can trace what our system saw on your account.

8. Screenshot

Hi [Name], could you send a screenshot of what you’re seeing on [screen/page]? Ideally with the full window visible, including the address bar. Small details there often point straight at the cause.

9. Order or account identifier

Hi [Name], happy to sort this out. I just need to find the right record: could you send your [order number / account email]? You’ll find the order number in your confirmation email, subject line [subject pattern].

Telling people where to find what you’re asking for (templates 7 and 9) cuts a full round-trip out of most tickets.

Resolutions: fixed, workaround, won’t fix

10. Fixed

Hi [Name], good news: [issue] is fixed. The cause was [one plain-language sentence]. [What the customer should now see / do to confirm.] If it misbehaves again, reply here and it comes straight back to me.

11. Workaround while we fix it

Hi [Name], we’ve found the cause of [issue] and a proper fix is scheduled for [timeframe]. In the meantime, here’s a workaround that takes about [time]: [numbered steps]. It’s not the long-term answer, but it unblocks [the task] today.

12. Won’t fix / not planned

Hi [Name], I checked with the team, and I’ll be straight with you: [request] isn’t something we’re going to change, because [honest reason, e.g., a design decision or platform limitation]. What I can offer is [closest alternative]. I know that’s not the answer you were hoping for, and I appreciate you taking the time to raise it.

The “won’t fix” is the hardest one to write and the one most worth having canned, because improvised versions tend to either overpromise or condescend.

Closers

13. Anything else

Hi [Name], glad that’s sorted. Is there anything else about [topic/product] I can help with while we’re here? If not, no reply needed. I’ll close the ticket, and it reopens automatically if you write back.

14. Closing an inactive ticket

Hi [Name], I haven’t heard back since my last message on [date], so I’ll close this ticket for now to keep things tidy. Nothing is lost: reply any time and it reopens with the full history, and I’ll pick it right back up.

15. Feedback ask

Hi [Name], one last thing: if you have 30 seconds, [rating link] tells us how this went. One click, no login. Either way, thanks for your patience while we worked through [issue].

If a closed ticket deserves a check-in later (a workaround that should be replaced, a fix worth verifying), that’s a follow-up, not a closer. We’ve covered timing and templates for those in follow-up emails in customer service.

How to personalize a canned response in 10 seconds

A canned response goes robotic the moment it ships unedited. The ten-second routine, in order of impact:

Fill the [specific issue] placeholder with the customer’s own words. If they wrote “checkout freezes on the payment step,” your reply says that, not “your technical issue.” Two seconds, and it’s the single strongest signal a human read the message.
Adjust the first sentence to the emotional temperature. A furious customer and a curious one shouldn’t get the same opener. Often it’s one added clause: “I can see this has cost you real time.”
Make the next step concrete. Replace [date] with an actual date you can keep. A specific commitment is what separates service from autoresponders.

That’s it. Name, their words, real date. Everything else in the template can stay canned, because customers don’t object to reused sentences — they object to feeling unread.

Keeping the library fresh with tone rewrites

Every canned response library rots the same way: it’s written once, in one person’s voice, and eighteen months later half the team finds the phrasing stiff while long-time customers start recognizing the boilerplate. Rewriting 20 templates by hand is the kind of task that stays on the backlog forever.

This is a place where an AI drafting tool earns its spot. In Replydesk, you paste an existing template into the tone rewrite workflow and get it back clearer, warmer, firmer, or more concise, with the facts and commitments untouched. Running the whole library through a “warmer and more concise” pass takes minutes, and doing it quarterly keeps the responses from calcifying. The free tier’s 20 drafts per day is enough to refresh a full library in a session or two; for how the drafting side works more broadly, see our overview of the free AI email draft generator.

The same workflow handles the situations templates can’t: when a ticket is too specific for any canned response, paste the whole thread and generate a fresh reply draft instead of forcing the nearest template to fit. Canned responses for the one-liners, generated drafts for the rest — that split is what keeps a fast queue from sounding like a machine.