Canned responses for customer service: 24 templates teams reuse without sounding canned

Canned responses for customer service are saved replies a team reuses for the messages it answers every day: the acknowledgment, the order number request, the refund confirmation. Written well, they cut the typing without cutting the person out. Written badly, they are the reason a customer writes back asking whether anyone read the message.

This guide covers what a canned response is, when it helps and when it hurts, and how to write one that reads as if a person sent it. Then come 24 templates by situation, notes on keeping a shared library tidy, and how templates work in Gmail, Outlook and shared inbox tools.

What is a canned response?

A canned response, also called a saved reply, a snippet or a response template, is a pre-written reply the team can insert in one click. Gmail, Outlook and shared inbox tools each store them differently, which the last section covers.

The point is to stop retyping the sentences that never change: where to find an order number, how long a refund takes, which hours the team keeps. What the customer wrote, what you found and what happens next still get typed each time. A template that tries to cover those parts too is the one that sounds canned.

When a canned response helps and when it hurts

A template earns its place when the same question arrives often enough that the answer has settled. It fails when it is used to avoid reading the message.

• Helps: the first acknowledgment, where the customer needs to know a person has the message.
• Helps: requests you make every day, such as an order number, a screenshot or a date.
• Helps: facts that must be stated the same way every time, such as refund timelines and policy limits.
• Hurts: complaints, where a reply that does not quote the specific problem reads as a brush-off.
• Hurts: the second and third message in a thread, when the customer has already given the detail the template asks for.

How to write a canned response that does not sound canned

Four rules cover it.

• Short. Two to four sentences. A customer skims a reply on a phone, and a long template hides the one line that matters.
• One job. An acknowledgment acknowledges. A refund confirmation confirms the refund. A template that also pitches the newsletter gets deleted the day someone notices.
• A blank for the specific detail. Placeholders such as {order number} or {date} force the sender to look the detail up. A template with no blanks gets sent without a glance.
• A line the sender must write. Each template below has a {specific line} the sender fills with what they saw in the message. It is the sentence that proves a person read it.

24 canned response examples by situation

Placeholders are in curly braces. Replace every one before sending, and write the {specific line} fresh each time. The templates use a first-name greeting, so drop it where your clients expect a surname.

Acknowledgment

Hi {name}, thanks for writing. I have your message about {topic} and I am looking at it now. {specific line} You will hear back from me by {time or date}.

Hi {name}, thanks for the details. {specific line} I will need until {date} to get you a full answer, and I will write before then if anything changes.

Hi {name}, I am sorry this happened. {specific line} I have passed it to {person or team}, and I will stay on the thread until it is sorted. Expect an update from me by {time or date}.

We are looking into it

Hi {name}, a quick update. We have reproduced the problem with {what} and {person} is working on it. {specific line} I will send the next update by {time}, whether or not it is fixed by then.

Hi {name}, I have brought in {person or team}, who handles {area}. {specific line} They have everything you sent, so there is no need to repeat it. You will hear from one of us by {date}.

Need more information

Hi {name}, happy to help with this. Could you send me the {order number or reference}? It is on {where to find it}. {specific line} Once I have it I can see what happened.

Hi {name}, thanks for flagging this. To find the cause, could you reply with a screenshot of what you see and the steps that led to it? {specific line} Even a photo of the screen works.

Hi {name}, before I change anything on the account I need to confirm it is yours. Could you reply from the email address on the account, or tell me the {detail we ask for}? Please do not send a password; we never need it.

Delay apology

Hi {name}, I owe you an update on {topic}. It is taking longer than I said because {reason}. {specific line} The new date is {date}, and I will hold to it.

Hi {name}, I said you would have {what} by {date we gave} and you do not. That is on us. {specific line} It will be with you by {new date}, and I will confirm the moment it is sent.

Hi {name}, {what} is held up at {third party}. I have chased them today and will again on {day}. {specific line} I will tell you as soon as it moves.

Delivered

Hi {name}, this is now fixed. {specific line} Could you check on your side and tell me if it looks right? If I do not hear back by {date} I will assume it is sorted and close the thread.

Hi {name}, {document or file} is attached. {specific line} Tell me if anything in it needs changing and I will turn it around by {date}.

Refund

Hi {name}, your refund of {amount} is approved and was issued on {date}. Card refunds take {number} working days to show, depending on the bank. {specific line} Reply here if it has not arrived by {date}.

Hi {name}, I have your refund request for {order number}. I need to check {what} before I can confirm it, which takes until {date}. {specific line} You will hear from me either way.

Cannot do that

Hi {name}, we cannot do {what they asked}, because {plain reason}. {specific line} What I can do is {alternative}. Tell me if that works and I will set it up.

Hi {name}, this one falls outside our {policy name}, which {what the policy says in one clause}. {specific line} The closest I can offer is {alternative}, and I am glad to do that today.

Hi {name}, this is not something our team handles, so I do not want to guess at it. {who does} is the right place, and I have copied them here. {specific line}

Closing the loop

Hi {name}, {what was fixed or delivered} is done, so I am closing this thread. {specific line} If anything else comes up, reply here and it reopens with the history attached.

Hi {name}, a while ago you asked for {what}, and I said I would tell you when it was ready. It is. {specific line} Here is {link or instructions}.

Chasing a silent customer

Hi {name}, I sent {what} on {date} and have not heard back. {specific line} Is there anything you need from me before you can reply? No rush if it is still in progress.

Hi {name}, I will close this thread on {date} unless I hear from you, since I do not want to keep writing if the matter is settled. {specific line} A one-line reply keeps it open.

Out of hours

A rule can send these two on the team's behalf, so they carry no {specific line}. More of that kind are in auto reply email templates.

Hi {name}, thanks for your message. Our team answers {hours} in {time zone}, so you will hear from a person after {time}. If this cannot wait, {urgent route}.

Hi {name}, we are closed from {start date} to {end date} and will read your message on {return date}. Orders placed before {cutoff} still ship on time. For anything urgent, {urgent route}.

How to keep a shared library tidy

A library of 15 good templates gets used. A library of 140, with four versions of the acknowledgment, gets ignored. Four habits keep it small.

• One owner per template. The person who wrote it, or the lead for that situation, edits it. Everyone else suggests changes.
• A review date. Put a date in the template's description and check it when it comes up. Prices, hours and policy lines go stale first.
• Retire the unused ones. If a template has not been sent in a quarter, remove it. If someone misses it, bring it back with a reason.
• Name by situation. 'Refund approved' is findable in a hurry. 'Thanks so much v2' is a mystery by March.

How templates work in Gmail, Outlook and shared inbox tools

Gmail templates

Gmail's templates are off by default. Turn them on under Settings, See all settings, Advanced, Templates. Then write a reply, open the three-dot menu in the compose window, choose Templates, and Save draft as template. Inserting one uses the same menu, and a filter can send a template as an automatic reply to matching mail.

Each account keeps its own templates, so a team library means copying text around or adding a tool on top.

Outlook Quick Parts and My Templates

Classic Outlook on Windows has Quick Parts: select text in a message, open Insert, Quick Parts, and Save Selection to Quick Part Gallery. They live on that computer. The My Templates add-in, in new and classic Outlook and on the web, keeps short templates with the mailbox, so they follow you between devices. Neither is shared with the team unless everyone works from one mailbox.

Shared inbox tools

A shared inbox keeps one library, visible to everyone who answers from that inbox. Look for an optional subject, placeholders filled from the thread, and a rule that can send a template when a message matches.

Where Sektra fits

We build Sektra, an AI shared inbox for client-facing teams, so read this with that in mind. Its templates are shared across the team, carry an optional subject, and are inserted from the composer on email and WhatsApp. The library is one list, so the review habits above apply in one place.

The assistant drafts replies in the thread's context, reading what the customer wrote and what the team promised, and a person reviews the draft before it goes. For settled cases, a rule the admin sets up can send a template reply when a message matches. The match can be a normal check, such as the sender's domain, or an AI check, such as whether the message asks for a refund.

On WhatsApp, the reply templates above work inside the 24-hour reply window. Outside it, WhatsApp only delivers Meta-approved message templates, a separate thing, and the composer switches to them. See the WhatsApp integration page and templates and the 24-hour window. The feature list is on /product.

Start with the ten replies you send most, give each an owner and a review date, and keep the {specific line} in every one.