Canned Responses for Customer Service: 30 Templates

Canned Responses for Customer Service: 30 Templates

Canned responses (also called saved replies or macros) save time and keep answers consistent. The trick is making them sound human: always use the customer’s name, reference their issue, and edit before sending.

Replace anything in [brackets].

Greetings and acknowledgements

1. First reply

Hi [Name], thanks for reaching out. I’m looking into this now and will get back to you by [time].

2. Need more information

Hi [Name], thanks for the details. To look into this, could you send me [order number / screenshot / email on the account]?

3. Escalating to a specialist

Hi [Name], I’ve passed this to our [team] specialists, who are best placed to help. You’ll hear from them within [timeframe].

Refunds and returns

4. Refund approved

Hi [Name], I’ve processed a refund of [amount] to your original payment method. It usually appears within [X] business days.

5. Refund request outside policy

Hi [Name], I understand why you’re asking. Our policy covers refunds within [X] days, and this order was placed on [date]. What I can do is [alternative: store credit / exchange / partial refund].

6. Return instructions

Hi [Name], here’s how to return your item: [steps]. Once it reaches us, we’ll process your [refund/exchange] within [X] days.

Shipping and delivery

7. Late delivery apology

Hi [Name], I’m sorry your order hasn’t arrived yet. I’ve checked, and it’s currently [status]. The new estimated delivery date is [date]. [Optional: As an apology, here’s [discount] off your next order.]

8. Lost package

Hi [Name], I’m sorry, it looks like your package was lost in transit. I’ve sent a replacement today, and you’ll get tracking details by email shortly.

9. Wrong item received

Hi [Name], sorry about the mix-up. I’ve sent the correct item and a prepaid return label for the wrong one. No need to rush returning it.

Technical issues and bugs

10. Bug acknowledged

Hi [Name], thanks for reporting this. I was able to reproduce it and have passed it to our engineering team. I’ll update you as soon as there’s a fix.

11. Bug fixed

Hi [Name], good news: the issue you reported is now fixed. Could you try again and let me know if everything works?

12. Workaround

Hi [Name], while our team works on a permanent fix, here’s a workaround: [steps].

13. Outage

Hi [Name], we’re currently experiencing an issue affecting [feature]. Our team is working on it, and you can follow updates at [status page].

Billing and accounts

14. Duplicate charge

Hi [Name], I can see the duplicate charge. I’ve refunded [amount]; it should appear within [X] business days.

15. Payment failed

Hi [Name], your last payment didn’t go through. You can update your card here: [link]. Your account stays active until [date].

16. Cancellation

Hi [Name], I’ve cancelled your subscription. You’ll keep access until [date]. If you have a moment, I’d love to know what we could have done better.

17. Password reset

Hi [Name], you can reset your password here: [link]. The link expires in [X] hours.

Feature requests and feedback

18. Feature request

Hi [Name], thanks for the suggestion. I’ve shared it with our product team. I can’t promise a timeline, but requests like yours shape what we build next.

19. Positive feedback

Hi [Name], thank you, this made our day! I’ve shared your kind words with the team.

20. Complaint

Hi [Name], I’m sorry about your experience. You’re right that [acknowledge the issue]. Here’s what I’ve done to fix it: [action].

Sales and pre-sales

21. Pricing question

Hi [Name], our plans start at [price]. Based on what you’ve described, [plan] is probably the best fit because [reason].

22. Demo request

Hi [Name], happy to show you around. You can pick a time that suits you here: [booking link].

Social media and chat

23. Move to private channel

Hi [Name], sorry to hear this. Could you send us a DM with your order number so we can sort it out?

24. Chat: one moment

Thanks, [Name]. Give me a minute while I check that for you.

25. Chat: out of hours

Thanks for your message! Our team is offline right now. We’ll reply by [time], or you can find quick answers here: [help center link].

Follow-ups and closing

26. No reply follow-up

Hi [Name], just checking in on this. Is there anything else you need from us?

27. Closing a ticket

Hi [Name], I’m closing this ticket for now. If anything comes up, just reply to this email and it will reopen.

28. Satisfaction survey

Hi [Name], glad we could help. Would you mind rating your experience? It takes 10 seconds: [link].

29. Out of office (agent)

Hi, I’m away until [date]. For urgent help, please contact [colleague/email].

30. Holiday hours

Hi [Name], our team is on holiday from [date] to [date]. We’ll reply as soon as we’re back. For urgent issues, [option].

Tips for better canned responses

  • Personalise the first and last line every time.
  • Keep them short. Customers skim.
  • Review quarterly to remove outdated policies.
  • Track the impact. Saved replies should lower your first response time without hurting CSAT.
Munaza

Munaza

Founder & Editor, SupportPricing

Munaza runs a digital marketing agency that manages social media and SEO for client brands across multiple platforms. Her work puts her inside SaaS tools every day: she sets up help centers, writes product content and compares software for clients before they buy. She started SupportPricing because customer service software pricing kept changing faster than anyone could track. Every price on this site comes from the vendor’s own pricing page and carries the date she checked it.

How we check prices · Contact · LinkedIn