50 Canned Responses for Customer Support (Ready to Copy)

Typing the same support reply for the twentieth time today isn’t just tedious. It’s slow. Canned responses fix this: pre-written replies you can send in seconds instead of typing from scratch each time.

Here are 50 you can copy right now, organized by situation.

Greetings and openers

1. Standard greeting

Hi [Name], thanks for reaching out. Let me look into this for you.

2. Returning customer

Hi [Name], welcome back. I see you’ve contacted us before, so let me pull up your history.

3. Acknowledging frustration

Hi [Name], I can see this has been a frustrating experience. Let me help you sort it out.

4. Quick response promise

Hi [Name], thanks for writing in. I’m looking into this now and will have an answer for you shortly.

5. After-hours acknowledgment

Hi [Name], thanks for your message. Our team is currently offline, but I’ll make sure someone gets back to you first thing tomorrow morning.

Troubleshooting

6. Asking for more details

Could you send me a screenshot of what you’re seeing? That will help me pinpoint the issue.

7. Steps to reproduce

Can you walk me through the exact steps you took before the error appeared? Knowing the sequence helps us reproduce it on our end.

8. Version check

What version of the app are you running? You can find this in [App Name] > About. Also, which macOS version are you on?

9. Basic restart suggestion

As a first step, try quitting the app completely (Command+Q) and reopening it. Sometimes a restart clears temporary glitches.

10. Clear cache suggestion

Try clearing the app’s cache: go to [specific path]. This often resolves display issues without affecting your data.

Status updates

11. Looking into it

I’ve escalated this to our engineering team. They’re investigating now. I’ll update you as soon as I hear back.

12. Found the issue

Good news: I found the problem. Here’s what happened and how to fix it: [explanation].

13. Bug confirmed

You’re right, this is a bug on our end. We’ve logged it and our team is working on a fix. I’ll let you know when the update is available.

14. Feature request logged

That’s a great suggestion. I’ve added it to our feature request tracker. I can’t promise a timeline, but it’s on our radar.

15. Waiting on third party

This issue involves [third party service], so we’re waiting on their team to respond. I’ll follow up with them today and keep you posted.

Apologies and acknowledgments

16. General apology

I’m sorry for the inconvenience. That’s not the experience we want you to have.

17. Service disruption

We experienced a service disruption earlier today. Everything is back to normal now. I apologize for any disruption to your work.

18. Delayed response apology

I apologize for the delayed response. Your message got caught in a backlog, but I’m on it now.

19. Acknowledging a mistake

You’re right, we made an error here. I’ve corrected it on our end. Here’s what changed: [details].

20. Billing error

I see the billing error on your account. I’ve issued a correction. You should see the adjustment within [timeframe].

Refunds and billing

21. Refund approved

I’ve processed your refund. You should see it back on your [payment method] within 5 to 10 business days.

22. Refund with explanation

Your refund of [amount] has been processed. For reference, our refund policy covers [policy detail]. Let me know if you have questions.

23. Subscription canceled

I’ve canceled your subscription. You’ll have access until [end of billing period]. No further charges will be made.

24. Partial refund

Based on your usage and our refund policy, I’ve issued a partial refund of [amount]. Here’s how we calculated that: [explanation].

25. Payment failed

It looks like your latest payment didn’t go through. This is usually a card expiration or insufficient funds issue. You can update your payment method at [link].

How-to and instructions

26. Getting started

Here’s a quick guide to get you set up: [link to docs]. If you get stuck at any step, let me know and I’ll walk you through it.

27. Specific feature

To use [feature], go to [path]. From there, you can [specific action]. Here’s a screenshot showing where to find it: [screenshot].

28. Workaround

There isn’t a built-in way to do that yet, but here’s a workaround that gets the same result: [steps].

29. Documentation pointer

We have a detailed guide for that here: [link]. The section on [topic] covers exactly what you’re trying to do.

30. Video walkthrough

I’ve recorded a quick walkthrough showing how to do this: [link]. Let me know if anything is unclear.

Escalation and transfers

31. Transferring to specialist

I’m going to bring in [Name/Team] who specializes in this area. They’ll have more context on [specific issue].

32. Manager escalation

I understand your frustration. I’m escalating this to my manager who can review the situation and follow up with you directly.

33. Engineering escalation

This needs our engineering team’s attention. I’ve created a ticket for them with all the details you’ve provided. You’ll hear from us within [timeframe].

34. Security concern

I’m passing this to our security team right away. They’ll review the situation and contact you within [timeframe].

Follow-ups

35. Checking in

Hi [Name], I wanted to check in. Were you able to resolve the issue with the steps I sent? Let me know if you need anything else.

36. After a fix

Hi [Name], just checking that everything is working on your end after the fix we applied. Any issues?

37. After no response

Hi [Name], I haven’t heard back, so I’ll assume this is resolved. I’m going to close this ticket, but feel free to reopen it anytime if the issue comes back.

38. Scheduled follow-up

I’m going to check back with you on [date] to make sure everything is still working. Talk to you then.

Closings

39. Standard close

Is there anything else I can help you with?

40. Positive close

Glad I could help. Don’t hesitate to reach out if anything else comes up.

41. Close with resource

That should do it. For future reference, our help docs are at [link]. They cover most common questions.

42. Close after complex issue

I know this was a longer process than expected. Thanks for your patience. If anything related comes up, reference ticket #[number] and we can pick up where we left off.

Edge cases

43. Feature not available on their plan

That feature is available on our [Plan Name] plan. You can upgrade at [link], or I can walk you through what’s included.

44. Can’t reproduce the issue

I wasn’t able to reproduce this on my end. Could you try again and let me know the exact steps? If it happens again, a screen recording would be really helpful.

45. Duplicate ticket

I see you also wrote in about this on [date]. I’m merging these tickets so everything is in one place. Here’s the latest update: [details].

46. Unsupported use case

Unfortunately, we don’t support [use case] at this time. The closest alternative would be [suggestion]. I’ve also logged this as a feature request.

47. Account recovery

For security, I need to verify your identity before making changes to your account. Could you confirm [verification detail]?

48. Known issue

This is a known issue that affects [description]. Our team is actively working on a fix. I’ll notify you when it’s resolved.

49. End of life product

That feature was part of [old product/version], which we’ve since retired. The equivalent in our current version is [new feature]. Here’s how to access it: [steps].

50. Positive feedback response

Thanks so much for the kind words. I’ll pass your feedback along to the team. It genuinely makes our day to hear this.

How to use these faster

Copying and pasting from a document works, but it’s slow. You have to find the right response, copy it, switch windows, paste it, and then customize the bracketed fields.

A text expander turns each of these into a trigger you can type anywhere. In TypeSnap, you’d set up snippets like:

• ;greet expands to response #1
• ;sorry expands to response #16
• ;refund expands to response #21
• ;close expands to response #40

With TypeSnap’s fill-in fields, you can make the bracketed parts interactive. When you type ;greet, a prompt asks for the customer’s name, then inserts the personalized response. No manual find-and-replace.

If you use 10 or more canned responses regularly, text expansion cuts your response time significantly. You still write the personal parts yourself, but the scaffolding is instant.