back to Jitbit Blog home About this blog

10+ Best Canned Responses for your Help Desk

by Alex Yumashev · Updated Apr 18 2026

"Canned responses" are pre-saved help desk messages that can can speed up your customer support preventing you from typing the same thing over and over. And it is a very common feature in many help desk systems.

After more than 10 years of running a SaaS help desk company (and also providing support to our customers) here's the list of our most frequent and most used canned responses:

Downtime acknowledgement

Shit happens. And when it does - you'll get dozens of support tickets: "Help, it's not working!" "I get an error!", "Are you guys there!?" - have a canned response that confirms the issue and lets your clients know you're working on it.

Thanks for reporting, yes, we are fully aware of the issue and we're working to resolve this ASAP, sorry folks!"

Critical times like this is when you need the most resources, don't waste it on writing the same thing again and again.

Calming an angry customer

Sometimes customers can be angry and even rude. Don't let this get to you, have a calming canned response ready:

I realize how frustrating this can be and we're incredibly sorry about this experience. We are currently reviewing our processes to make sure this won't happen again.

This also a psychological hack that helps keep your head clear, not take it personally and make this negative energy simply fly by and go into sand.

Bug report response

When someone reports a bug, respond with a nice confirmation:

Thanks for reporting and sorry about this, this wasn't supposed to happen. There seems to be a glitch in the application. We've logged this in our bug tracker, please expect a new version with the fix shortly.

Feature request - a "yes"

Great suggestion, we've added this to our road map.

Feature request - a "no"

I'm afraid we can't do that but here's another option.

Common issues, FAQ and KB items

A good help desk app has a built-in FAQ and "Knowledge base" modules that are tightly coupled with the canned responses (shameless plug: Jitbit does!), so whenever you see a common question - send a link to a KB-article with a click of a mouse. This includes:

The "break up" letter

Whenever someone wants to cancel their subscription or a trial, or asks for a refund - have a canned response ready:

It's really sad to see you go. But we surely appreciate your comments, which will help us make the app better. Please come by in a little while; perhaps, after time of our hard work you will find our app looking the way you've been expecting to see it. Your refund details are: xxxxxxx

Responses to your marketing campaigns

You are probably running a drip campaign - a sequence of short emails customers get after signing up or something like that. Every email probably generates some common inquiries so make sure you have an answer at hand.

The "We haven't forgotten about you" reminder

Sometimes when you spot a ticket that hasn't been updated for a long time (say, your engineering team is still working on it, or your financial department is still figuring the payment out), it's a good idea to update the customer, letting them know you haven't forgot about the ticket. Also, a good helpdesk app ;-) usually has a way to do that automatically - via workflow engines and "automation rules".

It's been a while since our last update, just wanted to reassure you that we haven't lost your case and still working on this.

Admitting a mistake

It's OK if a support agent has made a mistake. Admit your fault, do it quickly and empathetically, then apologize and move on.

Please disregard my previous message, I have to admit that what I said earlier was incorrect. Sorry about the error and hope this clears things up.

Bonus tip #1: keep tuning your canned responses as you go

Even once you set your canned responses up, the work is not over yet. Keep an eye on the incoming support tickets and adjust when needed.

Bonus tip #2: customize your responses

Make sure your canned responses address a customer by name - "Hello %CUSTOMER_NAME%" and insert more customer specific fields if needed.

Bonus tip #3: frequently used canned response? Consider a knowledge base article

If you find yourself using a canned response multiple times a day, consider writing a more detailed knowledge base article. Articles are great for many reasons:

Finally: don't use a canned response when personal treatment is required

There's a right and a wrong time for a canned response. Sometimes you just have to sit down and actually write a personalized message that's unique and specific to the situation. The first rule of automation is - not to rely on automation too much.

More canned response templates you'll actually use

The ones above cover the obvious cases. Here are the ones most teams add within their first few weeks of using a help desk — the "I wish I'd saved that reply" moments.

First acknowledgement (auto-reply alternative)

Use this when a ticket first arrives and you know the specific agent is about to pick it up (so an auto-reply feels too robotic):

Hi %FIRST_NAME%, thanks for reaching out. I've got your ticket in front of me and I'll be back to you within the next few hours with a real answer. If anything changes or you remember extra details, just reply to this email and it'll land in the same thread.

"Can you send more information?"

For tickets that arrived with half the information you need:

Thanks for the report. To help me look into this properly, could you send a few things? 1) A screenshot of the error message. 2) The approximate time (with timezone) when this last happened. 3) The account email you're signed in with. Once I've got those, I can check our logs and come back with a definite answer.

Password reset / login help

Probably the single most-used template in any IT or SaaS help desk:

If you're locked out, the fastest path is our self-service reset link: [LINK]. Drop the email address on your account into the form and you'll get a reset email within a minute or two. If the reset email doesn't arrive, check your spam folder first, then reply here and I'll trigger it manually.

How-to question — link to the KB article

Paired with a help-desk's KB integration, this is the backbone of ticket deflection:

Great question — we have a walk-through for exactly this: [ARTICLE LINK]. It covers the step-by-step and includes a few screenshots. Give it a try and let me know if anything is unclear, and I'll expand the article with whatever's missing.

Out-of-scope request (polite "no")

When someone asks for something you don't support — and you want to keep goodwill:

Thanks for asking. That's outside what we officially support, so I can't promise it'll work or that we'll be able to help if it breaks. That said, here's what I'd try if I were you: [SUGGESTION]. It's what I've seen other customers do in the same spot.

Delayed response apology

For the ticket that slipped through. Own it briefly and move on:

Apologies — this one got away from us. I'm looking at it now and I'll have an answer to you within the next couple of hours. Thanks for your patience on this.

Closing a ticket — confirmation

A clean close that keeps the door open:

Glad we got that sorted. I'm going to mark this ticket as resolved now, but if the issue comes back or you run into anything else, just reply here and we'll pick it right back up.

Escalation handoff

When the ticket has to move to engineering or a more senior agent:

This one needs a closer look from our engineering team. I've passed the full context over to them, and %AGENT_NAME% will take it from here. You'll hear back from them directly within [TIMEFRAME].

Duplicate ticket merge

For when someone has already contacted you about the same issue:

Looks like we already have an open ticket from you on this — I'm going to merge this one into the other thread so nothing gets lost, and we'll continue the conversation there. Apologies for the confusion!

Upsell / upgrade trigger

When a user is hitting a plan limit or asking for a feature that's in a higher tier:

That feature is available on our %PLAN_NAME% plan. Happy to walk you through the upgrade — or if you'd rather not change plans, here's a workaround that uses what's already included: [WORKAROUND].

Frequently asked questions

What are canned responses in a help desk?

Canned responses are pre-saved reply templates that an agent can insert into a ticket with a click, usually with placeholders like %FIRST_NAME% or %TICKET_ID% that get filled in automatically. They're meant for the reply patterns that come up dozens of times a week — first acknowledgements, password resets, closing confirmations, bug reports — where typing the same thing again wastes the agent's time and risks inconsistent wording. Good help desks pair canned responses with shortcut keywords (type /pwreset and the template expands) and knowledge-base suggestions, so agents can respond faster without losing the personal tone.

How many canned responses should a help desk have?

Most teams land somewhere between 15 and 40. Fewer than 10 and you're probably retyping more than you need to. More than 50 and agents can't find the right one, so they retype anyway. Start with five or six (acknowledgement, password reset, bug report, KB link, closing confirmation, delayed apology) and let the library grow from real ticket patterns, not from brainstorming sessions. Prune the templates no one uses — a stale library is worse than a small one.

Are canned responses the same as auto-replies?

No — and it's a common source of confusion. A canned response is inserted by an agent into a reply; the agent decides when it fits and edits it as needed. An auto-reply is sent by the system automatically, with no human review, usually on ticket creation ("thanks, we got it"). Auto-replies are best kept short and generic. Canned responses can be more detailed and tailored because a human is about to adjust them.

How do you write a good canned response?

Keep it short, sound like a human, and leave room for personalization. Specific tips: start with the customer's first name via a placeholder; acknowledge the specific issue in one sentence rather than a generic "we received your message"; tell them the next step and the expected timeframe; avoid corporate-voice phrases like "please be advised" and "at your earliest convenience". A good test: read it out loud. If it sounds like a form letter, rewrite it.

Should canned responses be customer-facing or internal-only?

Most are customer-facing — they're replies the customer will read. But a subset (internal notes, escalation handoffs, context for the next agent) should be marked as internal only. Good help desks distinguish between the two and prevent accidental sends of an internal template to a customer. If your tool doesn't separate them, it's worth pushing for that feature or using naming conventions like [INTERNAL] in the template name.

Can canned responses hurt customer experience?

Only if you lean on them too hard. A customer who gets three canned replies in a row to a complex problem feels like they're talking to a bot — even if a human is behind the keyboard. The fix is to treat canned responses as a starting draft, not a finished reply. Insert the template, then spend 30 seconds personalizing: mention something specific from the ticket, answer the actual question raised, and cut anything that doesn't apply.