Canned responses for customer service are pre-written replies that agents insert into tickets, chats, and emails to answer common questions in seconds. They cut repetitive typing, keep your tone consistent, and protect response times when volume spikes. The stakes are high, because 85% of CX leaders say a single unresolved issue is enough to lose a customer, according to a 2026 CX research release.
This guide gives you 54 customer service templates organized by scenario, so you can copy, adjust, and send. Whether you need customer service email templates, live chat scripts, or social media replies, you will find a starting point below. You will also learn how to make each reply sound human and how to keep your library clean as your team grows.
●A clear definition of canned responses, and when they help or hurt
●54 copy-paste templates for shipping, returns, billing, apologies, and follow-ups
●A five-step method for writing replies that do not sound robotic
●Tips for organizing and maintaining your template library
What Are Canned Responses for Customer Service?
Canned responses are pre-written messages that support agents insert into tickets, chats, and emails to answer frequent questions quickly. Agents trigger them with a shortcut or a menu, then edit the details before sending. Teams use them to speed up replies, reduce errors, and keep their voice consistent across every channel.
Canned Responses vs. Macros vs. Saved Replies (Terminology Explained)
Different helpdesks use different names for the same core idea. The label changes, but the job stays the same: reusable replies that save agents time.
➔Canned responses: The most common term, used by Freshdesk and many live chat tools, for text snippets inserted into a reply.
➔Macros: The term used by Gorgias and Zendesk. A macro can insert text, and it can also apply tags, change ticket status, or assign the ticket.
➔Saved replies: The term used by Help Scout and Intercom. They work like canned responses and often live in shared folders.
When to Use Them (and When Not To)
Templates work best for questions that repeat daily and have one correct answer. Speed matters here: 88% of customers expect faster responses than they did a year ago, and 74% expect 24/7 service, according to a 2026 summary of Zendesk's survey data.
➔Use them for: order status, tracking, return instructions, policy explanations, password resets, and acknowledgments.
➔Skip them for: emotionally charged complaints, complex multi-issue tickets, VIP accounts, and any message where the customer shares something personal. For these, write from scratch and use a template only as a starting point.
Canned Responses for Customer Service: 50+ Copy-Paste Templates
These customer service templates are built for E-Commerce support teams, but most work for any business that ships products or sells subscriptions. Replace everything in [brackets] before you send. Then add one personal detail, such as the product name or a line from the customer's message, so the reply feels written for them.
Greeting and Acknowledgment Templates (5)
➔1. First response to a general inquiry: "Hi [Customer Name], thanks for contacting [Brand]. I'm [Agent Name], and I'm happy to help with your question about [topic]. I'm looking into this now and will update you within [timeframe]."
➔2. Ticket received: "Hi [Customer Name], we've received your message and opened ticket #[Number]. A member of our team will reply by [date and time]. If you have photos or order details to add, reply to this email and we'll attach them."
➔3. Live chat welcome: "Hi [Customer Name], welcome to [Brand]! I'm [Agent Name]. How can I help you today?"
➔4. Returning customer greeting: "Hi [Customer Name], good to hear from you again. I can see your recent order #[Number], so I'll start from there. Tell me what's going on and I'll get it sorted."
➔5. Request for more information: "Hi [Customer Name], thanks for the details. To move this forward, could you send [order number, photo, or the email on your account]? Once I have it, I'll [next action] right away."
Order Status and Shipping Templates (8)
➔6. Order confirmed and processing: "Hi [Customer Name], your order #[Number] is confirmed and being prepared. Orders usually ship within [X business days]. You'll get a tracking link by email as soon as it leaves our warehouse."
➔7. Where is my order (in transit): "Hi [Customer Name], your order #[Number] is on its way with [Carrier]. Here is your tracking link: [link]. The latest scan shows [status], and the estimated delivery date is [date]."
➔8. Shipping delay (carrier): "Hi [Customer Name], your package is running behind because of delays with [Carrier]. The updated delivery estimate is [date]. I'm sorry for the wait, and I'll keep watching the tracking for you."
➔9. Shipping delay (stock or production): "Hi [Customer Name], your order #[Number] is taking longer than planned because [reason]. We now expect to ship by [date]."
➔10. Tracking not updating: "Hi [Customer Name], I see the tracking for order #[Number] hasn't updated since [date]. This can happen when a package moves between carrier hubs. I've asked [Carrier] to investigate and will follow up by [date]."
➔11. Lost package: "Hi [Customer Name], I'm sorry your order #[Number] hasn't arrived. I've opened a claim with [Carrier], and I'd like to make this right. I can send a replacement or issue a refund. Which would you prefer?"
➔12. Address change request: "Hi [Customer Name], thanks for letting us know. Your order #[Number] hasn't shipped yet, so I've updated the address to [new address]. If you spot anything wrong, reply within [timeframe] and I'll fix it."
➔13. Delivered but not received: "Hi [Customer Name], the carrier shows order #[Number] as delivered on [date] at [location]. Could you check with neighbors and around your entry points? If it still isn't there by [date], reply and I'll start an investigation."
Returns, Refunds, and Exchange Templates (8)
➔14. Return instructions: "Hi [Customer Name], I'm sorry the [product] didn't work out. You can start your return here: [link]. Once you print the label and drop off the package, we'll process your refund within [X days] of receiving it."
➔15. Return window expired: "Hi [Customer Name], thanks for reaching out. Our return window is [X days], and your order was delivered on [date], so I can't process a standard return. What I can offer is [store credit, exchange, or discount]. Would that work for you?"
➔16. Refund approved: "Hi [Customer Name], good news: your refund of [amount] has been approved and sent to your original payment method. Please allow [X business days] for it to appear on your statement."
➔17. Refund processing time: "Hi [Customer Name], I checked your refund for order #[Number]. It was issued on [date], and banks can take up to [X business days] to post it. If it hasn't appeared by [date], reply with your bank's reference and I'll dig in."
➔18. Exchange request: "Hi [Customer Name], I'd be glad to set up an exchange for your [product]. Please confirm the [size, color, or variant] you'd like. I'll send your new item as soon as the return scans with the carrier."
➔19. Damaged item received: "Hi [Customer Name], I'm so sorry your [product] arrived damaged. Could you send a photo of the item and the packaging? As soon as I have it, I'll ship a replacement or refund you, whichever you prefer."
➔20. Wrong item received: "Hi [Customer Name], that's our mistake, and I apologize. I'll send the correct [product] today with express shipping."
➔21. Return received, inspection in progress: "Hi [Customer Name], your return for order #[Number] arrived at our warehouse on [date]. Our team is checking it now. You'll hear from me within [X days] with the next step."
Product Question and Stock Templates (5)
➔22. Product recommendation: "Hi [Customer Name], great question! Based on what you're looking for, I'd suggest [product] because [one specific benefit]. If you tell me more about [use case], I can narrow it down further."
➔23. Sizing and fit: "Hi [Customer Name], thanks for asking. Our [product] runs [small, true to size, or large]. If you're between sizes, I'd go with [size]. Here is our size guide: [link]. We also offer free exchanges if it doesn't fit."
➔24. Out of stock: "Hi [Customer Name], [product] is sold out right now. We expect to restock around [date]. You can join the back-in-stock list here: [link], and I'm happy to suggest a similar item in the meantime."
➔25. Materials, ingredients, or compatibility: "Hi [Customer Name], here is what I can confirm for [product]: [materials, ingredients, or compatibility details]. If you have a specific concern, such as an allergy or a device model, tell me and I'll check with our team."
➔26. Discount code not working: "Hi [Customer Name], sorry about the trouble with code [CODE]. It looks like [reason, such as expired or not valid on sale items]. I've applied [alternative offer] to your order so you don't miss out."
Billing, Payment, and Subscription Templates (6)
➔27. Payment failed: "Hi [Customer Name], your payment for order #[Number] didn't go through. This is usually caused by [common reason, such as a billing address mismatch]. You can retry here: [link], or reply and I'll help another way."
➔28. Duplicate charge: "Hi [Customer Name], I see two charges of [amount] on [date]. I've confirmed only one order was placed, and I'm refunding the duplicate now. It should post within [X business days]. I apologize for the confusion."
➔29. Invoice or receipt request: "Hi [Customer Name], here is the receipt for order #[Number], attached to this message. If you need it addressed to a company or include a tax ID, send me the details and I'll reissue it."
➔30. Subscription cancellation request: "Hi [Customer Name], I'm sorry to see you go. Before I cancel, would [pause for X weeks, a lower frequency, or a one-time discount] help? If not, no problem. Just say the word and I'll cancel today."
➔31. Subscription pause or skip: "Hi [Customer Name], done! I've [paused or skipped] your next shipment. Your subscription will resume on [date]. You can change this anytime from your account at [link]."
➔32. Price adjustment request: "Hi [Customer Name], thanks for asking. Our policy allows price adjustments within [X days] of purchase. Your order qualifies, so I've refunded the [amount] difference. It will appear in [X business days]."
Apology, Complaint, and Escalation Templates (7)
➔33. General apology: "Hi [Customer Name], I'm sorry about [specific problem]. That isn't the experience we want you to have. Here is what I'm doing to fix it: [action]. I'll update you by [date]."
➔34. Late reply apology: "Hi [Customer Name], thank you for your patience, and I'm sorry for the slow reply. We had a higher volume of messages than usual. I've reviewed your request, and here is the answer: [answer]."
➔35. Product quality complaint: "Hi [Customer Name], thank you for telling us about the [issue] with your [product]. We hold ourselves to a higher standard than this. I've shared your feedback with our product team, and I'd like to [replace, refund, or credit] your order."
➔36. Upset customer de-escalation: "Hi [Customer Name], I understand why you're frustrated, and I would feel the same way. Let me take ownership of this. I'm going to [specific action] right now, and I'll message you again by [time]."
➔37. Escalation to a manager or specialist: "Hi [Customer Name], I want to be sure this gets the right attention, so I've passed your case to [Name, Role]. They have your full history, so you won't need to repeat anything. Expect a reply by [date and time]."
➔38. Policy decline with an alternative: "Hi [Customer Name], I wish I could say yes. Our policy doesn't allow [request] because [short reason]. Here is what I can do instead: [alternative]. Would that help?"
➔39. Service recovery gesture: "Hi [Customer Name], thank you for giving us the chance to make this right. As an apology for the trouble, I've added [credit, discount, or free shipping] to your account. It will apply automatically on your next order."
Technical Support and Troubleshooting Templates (4)
➔40. Login or password reset: "Hi [Customer Name], I've sent a password reset link to [email]. It expires in [X hours]. If you don't see it in a few minutes, check your spam folder, and let me know if it still doesn't arrive."
➔41. Troubleshooting steps: "Hi [Customer Name], let's get this working. Please try these steps: 1) [step one], 2) [step two], 3) [step three]. If the issue continues, reply with a screenshot and your [device or browser], and I'll take a closer look."
➔42. Known issue or outage: "Hi [Customer Name], thanks for flagging this. We're aware of an issue with [feature or service], and our team is working on it. We'll post updates at [status page link], and I'll message you as soon as it's resolved."
➔43. Bug report received: "Hi [Customer Name], thank you for the detailed report. I've logged it with our product team under reference [ID]. I can't promise a timeline yet, but I'll update you when we have news. In the meantime, here is a workaround: [workaround]."
Live Chat and Social Media Templates (4)
➔44. Please hold during a lookup: "Thanks for your patience, [Customer Name]. I'm checking this with our [team or system] and need about [X minutes]. I'll stay right here, and I'll message you the moment I have an answer."
➔45. Public social reply, moving to a private message: "Hi [Name], we're sorry to hear this and want to help. Could you send us a direct message with your order number? We'll take it from there right away."
➔46. Chat transfer handoff: "[Customer Name], I'm bringing in [Name] from our [team], who can handle this best. I've shared everything we discussed, so you won't need to start over. They'll join you in a moment."
➔47. Thank-you for a positive mention: "Thank you so much, [Name]! Comments like this make our day. We're glad you love your [product], and we can't wait to help with your next order."
Follow-Up, Closing, and CSAT Request Templates (5)
➔48. Check-in after resolution: "Hi [Customer Name], I'm following up to make sure [issue] is fully resolved. If anything still looks off, reply here and I'll pick it back up personally."
➔49. Closing an unanswered ticket: "Hi [Customer Name], I haven't heard back, so I'm closing this ticket for now. Nothing is lost. Reply to this email anytime and we'll reopen it right away."
➔50. Issue resolved confirmation: "Hi [Customer Name], I've [action taken], so this should be all set. Here is a quick summary for your records: [summary]. Is there anything else I can help with today?"
➔51. CSAT survey request: "Hi [Customer Name], thanks for chatting with us today. Could you take 30 seconds to rate your experience? Your feedback helps us train our team and improve: [survey link]."
➔52. Review request: "Hi [Customer Name], we hope you're enjoying your [product]! If you have a minute, a short review would help other shoppers decide. You can leave one here: [link]. Thank you for supporting [Brand]."
After-Hours and Auto-Reply Templates (2)
➔53. After-hours auto-reply: "Thanks for contacting [Brand]! Our team is offline right now. Support hours are [days and hours, time zone], and we'll reply on the next business day. For quick answers, visit [help center link]."
➔54. Holiday or peak season delay: "Thanks for your message! We're handling a high volume of requests during [season or holiday], so replies may take up to [X hours]. Your ticket is in the queue, and we'll get to it as fast as we can."
How to Write Canned Responses That Don't Sound Robotic
The best canned responses read like a helpful person wrote them five minutes ago. Use this five-step method whenever you build a new template or rewrite an old one.
01
Start with your top ticket reasons
➔Pull the last 90 days of tickets and rank them by volume. Build templates for the top 10 reasons first.
➔Copy the best past replies from your strongest agents, then clean them up.
02
Write the first line for a human
➔Open with the customer's situation, not your policy. "I'm sorry your order is late" beats "Per our shipping policy."
➔Use contractions and plain words. Read the template out loud, and rewrite anything you would never say to a customer's face. Clear
brand voice guidelines help the whole team stay consistent.
03
Add personalization fields
➔Insert variables for first name, order number, product, and carrier so agents never type them by hand.
➔Leave one open line for the agent to reference something the customer said. This single sentence makes a template feel personal.
04
Include the next step and a timeline
➔End every reply with what happens next and when. Customers hate silence more than bad news.
➔Keep each template to one main idea. If a reply needs three topics, send three focused replies or write it fresh.
05
Test and review every quarter
➔Track CSAT and reopen rates by template. A template with low scores or many follow-ups needs a rewrite.
➔Retire anything that references old policies, prices, or shipping times. Outdated templates create more tickets than they close.
How to Organize and Maintain Your Template Library
➔Use a clear naming system. Start every name with the category, such as "Shipping | Delay | Carrier," so agents find it by typing two letters.
➔Group by ticket reason. Create folders that mirror the groups in this guide, and keep each folder under 15 templates.
➔Assign owners and review dates. One person owns each folder and checks it every quarter against current policies.
Canned Response Mistakes That Hurt Customer Satisfaction
Templates save time only when they are accurate and relevant. Many retail teams learn this the hard way when one careless macro goes out to hundreds of customers. Avoid these common errors.
✕
Sending without editing. Leftover brackets, wrong names, or a mismatched product instantly reveal a copy-paste job. Always scan the reply before you hit send.
✕
Ignoring the customer's tone. A cheerful template sent to an angry customer feels dismissive. Match the mood, or write the reply by hand.
✕
Answering only half the question. A template that handles one issue while the customer asked about two forces another round of back-and-forth.
✕
Writing in legal language. Long policy paragraphs read as cold. Summarize the rule in plain words, and link to the full policy for those who want it.
✕
Letting the library grow without limits. Hundreds of near-duplicate templates slow agents down. Merge similar ones and delete the unused.
✕
Never updating for new policies. A template that quotes last year's return window creates disputes. Assign an owner for every template group.
Canned Responses vs. AI Automation: Where Each Fits
Canned responses and automation solve different problems. Templates speed up a human reply, while automation, backed by solid ticket deflection strategies, can answer simple questions without a human at all. The strongest support setups use both, and let agents focus on the conversations that need judgment.
Which Tickets to Template, Which to Automate, Which to Keep Human
➔Automate: Order tracking, simple policy questions, and password resets.
Ticket deflection automations handle these repeat questions around the clock.
➔Template: Returns, refunds, billing fixes, and follow-ups. These need a human to confirm details, but the wording stays the same.
➔Keep human: Complaints, escalations, high-value orders, and emotional situations. Use
pre-sale chat specialists for shoppers who are close to buying, because a personal answer can decide the sale.
Speed and tone matter even more for food and delivery brands, where a late order cannot wait for a perfect reply. Build your templates for urgency first, then refine the wording.
How Shop the Scenes Built Out Customer Service Processes
Strong templates are only one part of a support system. They work best alongside a documented customer service SOP, trained agents, and clear escalation paths. Shop the Scenes learned this early, and TalentPop helped the brand build both.
The brand was brand new when it came to TalentPop, and many of its processes were not yet built out. Its Customer Experience Manager, Renn Harbin, had worked with another customer service provider before and had not been impressed.
E-Commerce • Shop the Scenes
Core Metrics: TalentPop's recruitment team onboarded two skilled customer service agents ahead of the BFCM rush. TalentPop also paired the brand with a dedicated Customer Success Manager and Onboarding Specialist. Together, they built out processes that such a lean team had not yet had the time or opportunity to create.
"You guys are doing an outstanding job, and you've added a personal touch to the Customer Experience management side."
Renn Harbin, Customer Experience Manager
Renn was pleasantly surprised by the quality of service, and she has since referred other brands. The takeaway for your own team is simple: build the process first, then build the templates that support it. TalentPop does this for E-Commerce brands every day, pairing trained customer service agents with a dedicated team that builds out your processes, so your replies stay fast, accurate, and on brand.
Scale your support
Want trained agents who already know your helpdesk? Skip the work of building and maintaining every template yourself.
➔Agents trained on your tools, tone, and policies
➔Documented processes and reply libraries built for you
➔Faster replies without growing your in-house team
FAQ
What are canned responses in customer service?
Canned responses are pre-written replies that support agents insert into emails, tickets, and chats to answer common questions quickly. Agents customize details like the customer's name and order number before sending. Helpdesks may call them macros, saved replies, or templates, but the purpose is the same: faster, more consistent answers.
Are canned responses bad for customer service?
No, when used well. Canned responses are helpful for repeat questions with a single correct answer. They become a problem when agents send them without editing, ignore the customer's tone, or use them for complex complaints. Personalize every reply and write from scratch when the situation calls for it.
What is the difference between canned responses and macros?
A canned response is reusable text. A macro usually includes text plus actions, such as adding a tag, changing ticket status, or assigning the ticket to a teammate. Gorgias and Zendesk call these macros, while Freshdesk uses canned responses. Many teams use the terms interchangeably.
How many canned responses should a support team have?
Start with 15 to 25 templates that cover your highest-volume ticket reasons, then expand carefully. A large library is only useful if agents can find the right template fast. Group templates into folders, use clear names, and delete outdated or duplicate entries each quarter.
How do you personalize canned responses?
Use variables for the customer's name, order number, and product, then add one line that references their specific situation. Match your opening to their tone, and name the exact next step with a timeline. Even a single personal sentence makes a template feel written for that customer.
What should a good canned response include?
A good canned response includes a friendly greeting, an acknowledgment of the customer's issue, a clear answer or action, and the next step with a timeline. Keep the language plain, the paragraphs short, and the tone aligned with your brand. Add personalization fields so agents can tailor each message.
Can AI replace canned responses?
AI can answer many simple questions without an agent, but it does not fully replace canned responses. Templates still help agents handle returns, billing fixes, and follow-ups quickly and consistently. Most teams combine automation for repetitive questions with templates and human judgment for everything else.
How often should you update your canned responses?
Review your library at least once a quarter, and update templates immediately when policies, prices, or shipping times change. Check CSAT and reopen rates by template to find replies that confuse customers. Assign an owner to each folder so reviews actually happen.
Conclusion
Canned responses for customer service work best as a system, not a shortcut. The right templates answer common questions fast, protect your tone, and give agents more time for the conversations that need real attention. Build your library around your top ticket reasons, personalize every reply, and review it each quarter. Teams that treat their templates as living documents deliver quicker answers and a more human experience.
.png)
.png)
