---
title: "Canned Responses Examples: 70+ Free Templates"
description: "Over 70 free canned responses examples for customer service, sorted by situation. Copy one, fill it for your customer, or rewrite your own reply."
canonical: https://luckpanda.app/chatbot/tools/canned-responses-library
updated: 2026-10-14
---

# Canned responses examples for customer service

Canonical URL: https://luckpanda.app/chatbot/tools/canned-responses-library
Language: en
Updated October 14, 2026

Saved replies for the questions you answer every day, sorted by situation. Copy one as it is, personalize it for one customer, or paste your own draft and rewrite it.

Free tool: https://luckpanda.app/chatbot/tools/canned-responses-library (widget, customer-service)

Agents: run it over MCP (https://luckpanda.app/mcp) with chatbot_public_tool_run { "tool": "canned-responses-library", "lang": "en", "inputs": { … } }; chatbot_public_tool_list gives the inputs.

## Greetings and first response

The first reply sets the pace. Say who is answering, show you read the message, and say what happens next.

### Live chat greeting

_A visitor opens a chat with a question_

```text
Hi [customer name], this is [your name] from [business]. I've read your message about [topic] and I'm checking it now. Give me a minute or two.
```

### Email: we're on it

_A new ticket that needs some work before you can answer_

```text
Hi [customer name], thanks for writing in about [topic]. I'm [your name] and I'll look after this. I need to check [what you are checking] with [team], and I'll reply by [day and time] with an answer or an update.
```

### Asking for the one detail you need

_The message is missing a fact you need to help_

```text
Hi [customer name], I can help with this. Could you send me [the order number / the email on the account / a screenshot of the error]? As soon as I have it, I'll [what you will do].
```

### Someone you've helped before

_A returning customer writes again_

```text
Hi [customer name], good to hear from you again. I can see our last conversation about [earlier topic]. Is this about the same thing, or something new?
```

### Outside opening hours

_A message arrives when the team is offline_

```text
Hi [customer name], thanks for your message. Our team is offline now and back at [time and time zone] on [day]. Your message is saved, and the first person in will reply. If it's about [common topic], this page may answer it sooner: [help page link].
```

### Busy day, longer wait

_Replies are slower than usual_

```text
Hi [customer name], we're answering more messages than usual today, so replies are taking about [time]. You don't need to write again: your message is saved and keeps its place.
```

### Passing it to the right team

_Another team owns the answer_

```text
Hi [customer name], questions about [topic] are handled by our [team name], who can see [what they can see]. I've passed them your message with everything you sent, so you won't need to repeat it. They usually reply within [time].
```

## Order status and shipping

The most-asked question in most online stores. Lead with the fact: where the order is and when it arrives.

### Where is my order: on its way

_The order has shipped and tracking is moving_

```text
Hi [customer name], your order [order number] left us on [date] with [carrier]. Tracking number [tracking number], and you can follow it here: [tracking link]. The carrier expects to deliver it by [date].
```

### Not shipped yet

_The order is still being prepared_

```text
Hi [customer name], your order [order number] is being packed and should ship by [date]. You'll get an email with the tracking link as soon as it leaves us. If you need it by a particular date, tell me and I'll check what's possible.
```

### Tracking hasn't moved

_No tracking update for several days_

```text
Hi [customer name], the tracking for [order number] hasn't updated since [date], which is longer than it should be. I've opened a trace with [carrier] today and will write to you by [date] with what they find. If the parcel is lost, we'll [send a replacement / refund you], whichever you prefer.
```

### Marked delivered, but not there

_The carrier says delivered and the customer has nothing_

```text
Hi [customer name], the carrier marked [order number] as delivered on [date] at [time]. Could you check with neighbors, a building reception or a safe place near the door? If it hasn't turned up by [date], reply here and I'll open a claim with [carrier] and arrange [a replacement / a refund].
```

### Change the delivery address

_The customer gave the wrong address_

```text
Hi [customer name], I can change the address while the order is still [status]. Please send the full new address, including the [postal code], and I'll confirm once it's updated. If it has already shipped, I'll ask [carrier] to redirect it, which they can't always do.
```

### Customs and import charges

_An international order and a question about duties_

```text
Hi [customer name], orders to [country] go through customs, and import duties or taxes are set by the destination country, not by us. For your order, [they are included in your total / the carrier collects them on delivery]. Delivery usually takes [number] business days after the order leaves us.
```

### Order arriving in parts

_Items were sent in more than one parcel_

```text
Hi [customer name], your order was sent in [number] parcels because [reason]. [Item] is in the second parcel, tracking number [tracking number], due on [date]. There's nothing extra to pay.
```

### Cancel before it ships

_The customer wants to cancel an order_

```text
Hi [customer name], I've canceled order [order number] before it shipped. The refund of [amount] goes back to your [payment method] today, and banks usually show it within [number] business days.
```

## Returns and refunds

Give the window, the steps and the timing in one message, so the customer doesn't have to ask three times.

### How to start a return

_The customer asks how to send something back_

```text
Hi [customer name], you can return [item] within [number] days of delivery. Start here: [returns link]. You'll get a label by email. Pack the item [condition], drop it at [drop-off point], and we'll refund you within [number] business days of receiving it.
```

### Return received

_The returned item has arrived_

```text
Hi [customer name], your return for [order number] arrived today. We've checked it and refunded [amount] to your [payment method]. You'll see it within [number] business days, depending on your bank.
```

### Where is my refund

_The refund was sent but the customer can't see it_

```text
Hi [customer name], we refunded [amount] to your [payment method] on [date], reference [refund reference]. Banks usually take [number] business days to show it. If it isn't there by [date], send me a screenshot of the statement and I'll chase it with our payment provider.
```

### Outside the return window

_The request comes after the return period_

```text
Hi [customer name], [order number] was delivered on [date], so it's outside our [number]-day return window and I can't refund it as a change-of-mind return. What I can do is [repair / store credit / exchange]. If the item is faulty, tell me what's wrong, because that is handled differently.
```

### Arrived damaged

_The item was broken or damaged on arrival_

```text
Hi [customer name], that's not how it should have arrived. Could you send a photo of the item and the box? Once I have it, I'll send [a replacement / a full refund] straight away. [You don't need to send the damaged item back / I'll email you a free return label].
```

### Wrong item sent

_The customer got something they didn't order_

```text
Hi [customer name], you ordered [item] and we sent [wrong item]. That's our mistake. The right one ships [today / on date], tracking to follow. For the wrong one, [here's a free return label / you can keep it].
```

### Exchange for another size or color

_The customer wants a different variant_

```text
Hi [customer name], happy to swap it. I've reserved [new size or color] for you. Send the original back with this label: [label link], and we'll ship the new one [as soon as it's scanned by the carrier / when it reaches us].
```

### Item that can't be returned

_The item is excluded from change-of-mind returns_

```text
Hi [customer name], [item] was sold as [final sale / made to order], so it can't be returned because you changed your mind. This doesn't affect your rights if it's faulty or not as described. If something is wrong with it, tell me what, and I'll sort it out.
```

## Billing and payments

Money questions make people anxious. Name the amount and the date, explain what the charge is, and say when it resolves.

### Charged twice

_Two charges for one order_

```text
Hi [customer name], I can see two charges of [amount] on [date]. The second one was a duplicate, and I've refunded it today, reference [refund reference]. Your bank usually shows the refund within [number] business days. I'll check again on [date] to make sure only one charge remains.
```

### Payment failed

_A card payment didn't go through_

```text
Hi [customer name], your payment for [plan or order] on [date] didn't go through. The bank gave the reason as [reason]. You can update your card here: [billing link]. Your [account / order] stays [active / reserved] until [date].
```

### A charge they don't recognize

_The customer doesn't know what a charge is for_

```text
Hi [customer name], the charge of [amount] on [date] shows on statements as [statement descriptor]. It's for [what it was], ordered with the email [email]. If that doesn't match anything you or someone on your account ordered, tell me and I'll [cancel / refund] it and help you secure the account.
```

### Copy of an invoice

_The customer needs an invoice or receipt_

```text
Hi [customer name], here is the invoice for [order or period]: [invoice link]. You can download every past invoice yourself under [where to find them].
```

### Company name or tax ID on an invoice

_The invoice needs different billing details_

```text
Hi [customer name], I've reissued invoice [invoice number] with [company name] and [tax ID]. The new copy is here: [invoice link]. Future invoices will use these details too.
```

### Upgrade or downgrade

_The customer wants a different plan_

```text
Hi [customer name], I've moved you to [new plan] from [date]. The difference, [amount], is charged [today / at your next renewal]. Nothing else changes in your account.
```

### Cancel a subscription

_The customer asks to stop paying_

```text
Hi [customer name], I've canceled your [plan] subscription. You won't be charged again, and you keep access until [date], the end of the period you paid for. If you want a copy of your data first, here's how to export it: [link].
```

### Asking to pay in parts

_The customer can't pay the full amount at once_

```text
Hi [customer name], thanks for telling me. For [invoice or order], we can split the [amount] into [number] payments, the first on [date]. Reply "yes" and I'll set it up and send you the schedule.
```

## Account and login

Be helpful and careful at the same time. Never ask for a password, a full card number or a one-time code.

### Password reset

_The customer can't remember their password_

```text
Hi [customer name], you can reset your password here: [reset link]. The link works for [number] minutes. If the email doesn't arrive, check spam and promotions, and make sure it's going to [the email on the account]. We'll never ask you for your password.
```

### Account locked

_Too many failed sign-in attempts_

```text
Hi [customer name], your account was locked after several failed sign-ins, to protect it. It unlocks by itself at [time], or you can reset your password now to get straight back in: [reset link].
```

### Lost two-step verification

_The customer lost the phone or app with their codes_

```text
Hi [customer name], I can help you back in. Before I turn off two-step verification, I need to confirm it's you: please reply from the email on the account and include [verification detail, such as your last invoice number]. Once that's confirmed, I'll reset it and you can set it up again.
```

### Change the sign-in email

_The customer wants to use a new address_

```text
Hi [customer name], you can change your email under [where in settings]. We'll send a confirmation link to the new address, and the change takes effect when you click it. Your old address gets a notice too, so you'll know if anyone else ever tries this.
```

### Delete my account

_The customer asks you to delete their account or data_

```text
Hi [customer name], I can delete your account and the personal data linked to it. This removes [what is removed] and can't be undone. We're required to keep [what is kept, such as invoices] for [period]. Reply "Yes, delete" and I'll do it within [number] days and confirm by email.
```

### Asking about someone else's account

_The person writing isn't the account holder_

```text
Hi [customer name], to protect [account holder]'s privacy I can only discuss the account with them or someone they've added as [an authorized user]. If they reply from the email on the account, or add you under [where], I'll be glad to help.
```

### Suspicious sign-in

_The customer saw a sign-in they don't recognize_

```text
Hi [customer name], thanks for flagging it. Please reset your password now ([reset link]) and turn on two-step verification under [where]. I've signed out every other session on your account. Then tell me if you see anything changed that you didn't do.
```

## Product questions

Answer the question, then add the one thing they need to know to succeed with it.

### How to do something

_A how-to question with a short answer_

```text
Hi [customer name], here's how:
1. [step]
2. [step]
3. [step]
There's a short guide with screenshots here: [link]. If it looks different on your screen, send me a screenshot and I'll point to the right place.
```

### Will it work with mine?

_A compatibility question_

```text
Hi [customer name], yes, [product] works with [their device or system] from [version] on. The one thing to know is [limitation]. The setup guide is here: [link].
```

### It doesn't do that

_The product lacks the feature they want_

```text
Hi [customer name], [product] doesn't [feature] today. The closest option is [workaround], which gets you [what it gets them]. I've passed your request and your use case to our product team. I can't promise it will be built, but it helps them decide.
```

### Thanks for a feature idea

_The customer suggests an improvement_

```text
Hi [customer name], thanks for the idea about [feature]. I've added it to our list with your example of [their use case], which makes it much easier for the team to judge. If it's built, I'll let you know.
```

### Back in stock

_An item or size is sold out_

```text
Hi [customer name], [item] in [size or variant] is sold out. We expect more on [date], though supplier dates can move. You can get an email when it's back here: [link]. [Similar item] is in stock now if you need one sooner.
```

### Helping them choose

_The customer can't decide between two options_

```text
Hi [customer name], the main difference is [difference]. If you mostly [use case A], go for [option A]. If you [use case B], [option B] is the better fit. Tell me a little about how you'll use it and I'll say which one I'd pick.
```

### Reporting a bug

_The customer reports something broken_

```text
Thanks for reporting this, [customer name]. To find it quickly, could you send what you clicked just before it happened, your [browser / app version], and a screenshot if you have one? I'll try to reproduce it today and tell you what I find.
```

## Delays and outages

Say what is affected, what is not, what you are doing, and when the next update comes. Silence makes delays feel longer.

### Known outage

_Something is down and you know about it_

```text
Hi [customer name], you're right: [feature] isn't working for some customers since [time and time zone]. Our engineers are on it. Your data is [safe / not affected]. Updates are posted here: [status page], and I'll reply to you when it's fixed.
```

### Reported, not confirmed yet

_You're still finding out if there is a wider problem_

```text
Hi [customer name], thanks for telling us. I'm checking now whether this is affecting others or just your account. I'll update you within [time]. If you can, send a screenshot of what you see.
```

### Outage fixed

_The problem is resolved_

```text
Hi [customer name], [feature] is working again as of [time]. The cause was [plain-language cause]. [What we are changing so it doesn't happen again.] If anything still looks wrong on your side, reply here and I'll look at your account directly.
```

### Shipping delay on many orders

_A batch of orders will be late_

```text
Hi [customer name], orders placed between [date] and [date] are shipping [number] days later than we said, because [reason]. Your order [order number] should now ship on [date]. If that no longer works for you, I can cancel it for a full refund.
```

### Appointment running late

_A booked service or visit is delayed_

```text
Hi [customer name], we're running about [time] behind on today's [appointments / visits]. Your [appointment] is now expected at [new time]. If that doesn't work, reply and I'll offer you the next free slot instead.
```

### Planned maintenance

_You're telling customers ahead of downtime_

```text
Hi [customer name], [product] will be unavailable on [date] from [time] to [time] [time zone] while we [reason]. You don't need to do anything. Anything you save before [time] is kept.
```

## Complaints and upset customers

Use these as a starting point only. Read the whole message, then change the line that responds to what they said.

### First reply to a complaint

_A customer complains and you need time to check_

```text
Hi [customer name], thank you for telling us. [Restate what happened in one sentence], and that shouldn't have happened. I'm looking into [specific thing] now and will reply by [time] with what went wrong and what we'll do about it.
```

### We got it wrong

_The mistake was yours_

```text
Hi [customer name], you're right: we [what went wrong]. I'm sorry. I've already [fix done], and [what else you will do]. If this cost you [time / money], tell me and I'll see what we can do.
```

### Not our error, still helping

_The cause was outside your control_

```text
Hi [customer name], that sounds like a frustrating day. The delay came from [carrier / bank / partner], so I can't fix it directly, but I can [what you can do], and I've already [action]. I'll keep an eye on it until it's resolved.
```

### Passing it to a manager

_Someone with more authority needs to decide_

```text
Hi [customer name], I've passed this to [name or role], who can [approve a refund / review the decision]. I've sent them the whole conversation so you won't need to repeat it. They'll contact you by [time].
```

### Reply to a negative review

_A public review on your page or a review site_

```text
Hi [first name], thank you for the review. [The specific problem] isn't what we want anyone to experience. We'd like to put it right: please email [support email] with your [order number] and mention this review. [Your name], [business]
```

### Setting a boundary

_The customer is abusive or threatening_

```text
I want to help you sort this out, and I'll keep working on it. I can't continue the conversation if [the insults / the threats] continue. If you prefer, we can carry on by email at [address].
```

### Offering a goodwill gesture

_You want to make up for a bad experience_

```text
Hi [customer name], the fix is done, but it doesn't undo the hassle. To make up for it, I've added [credit / discount / free item] to your account. It's there now, no code needed.
```

## Closing and follow-up

A clear close tells the customer the problem is solved, or exactly what happens next if it isn't.

### Checking it's solved

_You've given an answer and want to confirm_

```text
Does that solve it, [customer name]? If anything still isn't working, reply here and I'll pick it straight back up.
```

### Ending a chat

_The conversation is finished_

```text
I'll close this chat now. If you need anything else about [topic], start a new chat or reply to the transcript email, and you'll reach us. Have a good [day / evening].
```

### No reply from the customer

_You're waiting on them and they've gone quiet_

```text
Hi [customer name], I haven't heard back about [topic], so I'll close this ticket on [date]. If you still need help, reply to this email and it reopens with all the details.
```

### The follow-up you promised

_You said you would check back_

```text
Hi [customer name], as promised, I checked on [issue] today. [What you found.] [Next step, or "Nothing else for you to do."] I'll close this ticket unless you tell me otherwise.
```

### Asking for feedback

_After a resolved conversation_

```text
Thanks for your time today, [customer name]. Could you tell us how we did? It's one question: [survey link]. If something wasn't right, reply here instead and I'll read it myself.
```

### Someone else will continue

_Your shift ends before the issue is closed_

```text
Hi [customer name], my shift ends at [time], so [colleague name] will continue from here. I've shared everything we've discussed, so you won't need to explain it again. You'll hear from them by [time].
```

### Fixed after the conversation ended

_The fix landed after the customer left_

```text
Hi [customer name], good news: [issue] is fixed as of [date]. [What they need to do, if anything, such as refresh the page.] Thanks for reporting it.
```

## Sales and pre-sales

Someone asking before they buy wants a straight answer and one next step. Answer, recommend, and offer the link.

### Pricing question

_A visitor asks how much it costs_

```text
Hi [customer name], [plan or product] is [price] [per month / one time] and includes [the two or three things that matter most]. Most [type of customer] start with [plan] because [reason]. Would you like the link to start, or a quick call to check it fits?
```

### Booking a demo

_The visitor wants to see it first_

```text
Hi [customer name], happy to show you. Pick a time that suits you here: [booking link]. It takes [length], and if you send me [what to prepare] beforehand, I'll show it with your own example.
```

### Trial question

_A visitor asks about trying before buying_

```text
Hi [customer name], you can try [product] free for [length], and [you don't need a card / your card isn't charged until the trial ends]. Everything you set up during the trial carries over if you stay. Start here: [link].
```

### Asking for a discount

_The visitor asks for a lower price_

```text
Hi [customer name], our prices are the same for every customer, so I can't discount [plan]. What I can offer is [yearly billing, which costs less per month / a smaller plan / a longer trial]. Would that help?
```

### Comparing you with a competitor

_A visitor asks how you differ from another product_

```text
Hi [customer name], good question. The main difference is [difference]. [Competitor] is a better fit if [their strength], and we're a better fit if [your strength]. What matters most to you?
```

### Bulk or wholesale order

_A business wants a larger quantity_

```text
Hi [customer name], yes, we take orders of [quantity] and up. To quote you, I need the [items], quantities, delivery [city and country] and the date you need them. I'll send a quote within [time].
```

### Following up on a quote

_You sent a quote and heard nothing_

```text
Hi [customer name], I'm checking in on the quote for [what] I sent on [date]. It's valid until [date]. If anything in it doesn't fit, tell me which part and I'll see what I can change.
```

### When you're not the right fit

_The product won't do what they need_

```text
Hi [customer name], thanks for explaining what you need. Honestly, [product] isn't built for [their need], and I'd rather tell you now than after you've paid. [Type of product or tool] would suit you better.
```

## What a canned response is

> A canned response is a reply you write once and reuse for a question you answer often, such as "Where is my order?" or "How do I reset my password?". A good canned response names the customer, confirms their specific problem, gives the fact or link they need, and ends with one next step. Keep [slots] for order numbers and dates, and change at least one sentence for every customer.

Every team calls them something different: saved replies, macros, snippets, quick replies, templates. They all do the same job. They save you typing the same answer twenty times a day, and they keep the facts in those answers the same from one agent to the next.

1. **Find the situation.** Search for a word such as "refund" or "password", or pick a situation above the list.
2. **Copy it, or personalize it.** Copy the entry as it is, or press Personalize and add the customer's name, your business and the facts. The AI fills the slots it can and leaves the rest in brackets.
3. **Fill every slot.** Replace each [square-bracket] slot with the real fact before you send. A reply that still says [order number] tells the customer it came from a template.
4. **Rewrite your own draft.** Open Rewrite my reply, paste a reply you wrote, and get a version that names the problem once, keeps every fact you wrote and ends with one next step.
5. **Save the ones you use.** Paste the final text into your help desk's saved replies, under a name that says the situation, such as "Refunds / Refund issued".

## How to write canned responses that don't sound canned

Customers spot a canned reply when it could have been sent to anyone. The fix is not to avoid templates. It is to write them so the specific part does the work.

- Open with their situation, not your greeting. "Your order 4821 left us on Monday" reads as written for them. "Thank you for contacting us" does not.
- Put a slot wherever a specific fact goes: [order number], [date], [what they already tried]. A template with no slots is a form letter.
- Answer first, explain second. The fact they asked for belongs in the first two sentences.
- Apologize once at most, and only for something that actually went wrong.
- End with one next step and a time: what you will do and when, or what they need to do.
- Write the way your team talks. If nobody on your team would say "We apologize for any inconvenience caused" out loud, don't save it.
- Change one sentence every time. Read their message again and adjust the line that responds to it.

| Sounds canned | Sounds written for them |
| --- | --- |
| Thank you for reaching out to us. We have received your inquiry and will respond at our earliest convenience. | Hi Lena, I've got your message about the missing charger. I'm checking with the warehouse and will reply by 3 pm today. |
| We apologize for any inconvenience this may have caused. | You waited four days for an answer, and that's too long. Here it is. |
| Please be advised that refunds take 5 to 10 business days. | We refunded you on Tuesday. Your bank should show it by next Wednesday at the latest. |
| Is there anything else I can help you with today? | Does that fix it? If the button is still grey, send me a screenshot and I'll look at your account. |

## The shape of a reply you can reuse

Most good canned responses follow the same four parts. Save the pattern, and new templates become quick to write and easy to check.

**A pattern for any canned response**

```text
Hi [customer name],

[One line that shows you read their message: the order, the error, the date.]

[The answer, or the fact they asked for, with the link if there is one.]

[What happens next: who does it, and by when.]

[Your name]
[Business]
```

Live chat drops the sign-off and keeps each part to one sentence.

| Part | Why it matters | Example |
| --- | --- | --- |
| Their situation | Proves a person read the message | Your order 7702 shipped on 3 October. |
| The answer | It is what they came for | It's with the carrier and due on Thursday. |
| The next step | Stops the follow-up "any update?" | If it isn't there by Friday, reply and I'll send a replacement. |
| Your name | People write back more calmly to a person | Priya, Northwind Coffee Roasters |

## How to organize a canned response library

A library nobody can find things in gets ignored, and agents go back to typing from memory. A few habits keep it usable.

- Start with the questions you answer every day. For most teams that is ten to fifteen replies, not a hundred. Add more only when a question keeps coming back.
- Name each reply by situation, then by case: "Shipping / Tracking stuck", "Billing / Charged twice". Agents search by the problem, not by a clever title.
- Use short shortcuts if your tool supports them, such as /ship-late or /refund-done, and keep them consistent.
- Give every folder one owner who updates it when a policy, a price or a delivery time changes.
- Date each reply when you change it. Review anything older than six months, and delete what nobody uses.
- Keep one language version per reply, and write each one natively rather than translating word for word.

| Folder | Replies in it | Who keeps it current |
| --- | --- | --- |
| Greetings | First reply, after hours, busy day, wrong team | Support lead |
| Orders and shipping | On its way, stuck, delivered but missing, address change | Operations or fulfillment |
| Returns and refunds | How to return, refund issued, outside the window | Whoever owns the returns policy |
| Billing | Charged twice, failed payment, invoices, cancellations | Finance or billing |
| Product | How-tos, compatibility, feature requests, bugs | Product or a senior agent |
| Incidents | Outage, fixed, maintenance | Engineering on call, with support |

## When not to use a canned response

Templates make the easy replies faster. In some conversations they make things worse, because the customer already feels unheard and a stock answer proves it.

- The customer wrote a long, upset message. Answer what they said in your own words, then use a template for the facts.
- They already got that template and it didn't help. Sending it again tells them nobody read their reply.
- Something personal is involved: a death, an illness, a safety concern, a legal threat. Write from scratch, and pass legal or safety matters to the right person.
- The answer depends on their account and you haven't looked yet. Look first.
- The policy in the template has changed. Fix the template before you send another one.

For the hard ones, start from an empathy statement rather than a full template, and add the facts yourself. The empathy statements library has openers for each of these situations.

## Canned responses by channel

| Channel | Length | Greeting and sign-off | What to watch |
| --- | --- | --- | --- |
| Live chat | One to three short sentences per message | First name, no sign-off | Send the answer in parts rather than one long block |
| Email | Three to six sentences | Greeting and your name | Put the answer in the first paragraph, not after the pleasantries |
| Direct messages on social apps | Under 300 characters | First name, no sign-off | Never ask for passwords, card numbers or codes |
| Public comments and reviews | One or two sentences | Their first name, your name | No order details or personal data in public; move it to a private channel |
| Text and WhatsApp | One or two sentences | Business name at the start | Include how to reach a person if the message is automated |

## The first replies to save, by type of business

| Business | Save these first |
| --- | --- |
| Online store | Where is my order, tracking stuck, how to return, refund issued, wrong item, customs charges |
| Software and apps | Password reset, two-step verification, how-to steps, bug report, plan change, cancellation |
| Restaurants and cafes | Opening hours, table booking, allergen questions sent to staff, delivery area, large group booking |
| Hotels and travel | Booking changes, check-in times, cancellation terms, payment questions, special requests |
| Clinics, salons and studios | Book or move an appointment, running late, what to bring, prices sent as [price] slots |
| Courses and coaching | Course start dates, payment plans, access problems, certificates, refunds before the start date |
| Agencies and services | Quote follow-up, project status, invoice copies, scope changes, booking a call |

Questions about health, allergies or legal terms should always get a reply checked by the person responsible, not a template alone.

## Common mistakes

- Leaving a slot in: "Hi [customer name]" is the fastest way to tell someone they got a template. Read the reply once before you send it.
- The wrong name. Check the name in the reply matches the name on the message, especially after copying from another ticket.
- An old policy. A template that still says "30 days" after you moved to 14 days creates a second complaint.
- "Thank you for your patience" to someone who had no choice but to wait. Say what happened instead, and thank them for something they actually did.
- Asking for details they already gave. Read the thread first.
- Stacking apologies. One sorry for the real problem is enough; three sound automatic.
- Answering a different question. A refund template sent to someone asking about an exchange sends the conversation round twice.

## How an AI agent answers the same questions from your website

A canned response still needs a person to read the message, choose the reply and fill in the slots. An AI customer service agent does that step for the questions your website already answers. It reads your pages, documents and FAQs, replies in the tone you set, and fills in the facts from your own content instead of from a template. It doesn't invent prices or policies, and it hands the chat to a person on the topics you choose, such as refunds or complaints.

*A return question on a store's website, at 11:40 pm*

Visitor: hi can i still return the boots i got last week? they're too small

Chatbot: Yes. You have 30 days from delivery to return unworn shoes, so you're well within the window. Start the return on the Returns page and you'll get a free label by email. Would you like to swap them for a bigger size instead? _(Searched knowledge: return window shoes)_ _(From the page: Returns and exchanges)_

Visitor: actually i want my money back, and the box got thrown out

Chatbot: Our returns page doesn't say whether a return without the original box is accepted, so I've passed this to the team to confirm. They're back at 9 am and will reply here and by email. _(Handed to a person: refund)_

**Let the agent answer**
- Order and delivery questions your pages cover
- Return windows and how to start a return
- Opening hours, prices and plans from your site
- How-to questions from your help pages

**Keep for your team, with canned responses**
- Refund decisions and exceptions
- Complaints and upset customers
- Anything that needs a look at one account
- Personal or sensitive situations

**Answer the repeat questions at 2 a.m. too** Build a support agent from your own website pages. It answers from what you publish and hands the rest to your team. [See the AI customer service agent](https://luckpanda.app/chatbot/ai-customer-service-agent)

## Questions people ask

### What is an example of a canned response?

A reply to "Where is my order?": "Hi [customer name], your order [order number] left us on [date] with [carrier]. You can follow it here: [tracking link]. It should arrive by [date]." The slots are filled for each customer, so the reply is the same in structure but specific in its facts.

### Are canned responses bad for customer service?

Not when they are written well and used for the right questions. They keep answers fast and consistent. They hurt when they are sent unchanged to someone who is upset, when a slot is left unfilled, or when they answer a different question from the one the customer asked.

### What is the difference between a canned response, a saved reply and a macro?

A canned response and a saved reply are the same thing: stored text you insert into a message. In many help desks a macro can also act on the ticket, for example set its status, add a tag or assign it to a team, as well as inserting the text.

### How many canned responses should a support team have?

Start with the questions you answer every day, often ten to fifteen. Add a reply only when a question keeps coming back, and remove replies nobody has used in months. A short library that is kept current is more useful than a long one that is out of date.

### How do I make canned responses sound more human?

Open with the customer's situation, put slots where specific facts go, answer in the first two sentences, apologize once at most, and end with a clear next step. Then change one sentence for each customer so it responds to what they actually wrote.

### Can an AI chatbot replace canned responses?

For questions your website and documents already answer, an AI agent can reply directly, at any hour, with the facts filled in from your content. Your team still needs canned responses for the conversations a person should handle: refunds, complaints and anything that needs a judgment.

Try it on your website: https://luckpanda.app/chatbot/try