These support ticket response examples are copy-ready replies for an IT helpdesk: acknowledgment, asking for details, password resets, outages, escalation, follow-ups, and closing. Before you send one, adapt it so the user knows the next step, when it happens, and who owns it.
We build SherpaDesk, a helpdesk and PSA (professional services automation) a small IT team can run alone. The 36 templates below are tool-neutral and written for IT queues, in nine groups, with one ticket worked from first reply to close.
Template Index
Find the situation, jump to the group, and copy the template. Every template is also in one plain-text file.
| Situation | Templates | Send when |
|---|---|---|
| New ticket | 1–4 | You can't solve it in the first reply |
| Missing details | 5–7 | You need information or an approval first |
| Passwords, accounts, access | 8–13 | Resets, lockouts, MFA, new hires, leavers |
| Outages and security | 14–18 | Several users are affected, or a phishing report arrives |
| Delays and escalation | 19–22 | You'll miss a time, or the ticket changes hands |
| No response | 23–26 | The user stops replying |
| Solved | 27–30 | The work is done, merged, or declined |
| MSP scope and billing | 31–34 | The request touches the contract or the invoice |
| School IT | 35–36 | Student devices and classroom requests |
How To Fill In These Templates
Square brackets mark the parts you replace. Your helpdesk may fill some automatically; the check below catches the rest. If your helpdesk adds its own ticket reference to the subject, keep that one and drop ours.
Field By Field
| Placeholder | What goes in | Example | Common mistake |
|---|---|---|---|
| [First name] | The requester's first name | Maria | "Hi ," when the field is empty; use "Hi there" as the fallback |
| [Ticket #] | The ticket number, in the subject and the body | 4821 | Deleting the reference your helpdesk uses to thread replies, often in the subject |
| [Problem] | The issue, in the user's words | Outlook keeps asking for your password | Pasting the ticket title written by a technician |
| [Time] | A clock time or a business-day count | by 2:00 p.m. today | "Soon," "shortly," "ASAP" |
| [Next step] | The action you'll take next | connect to your PC remotely | Describing what you already did instead |
| [Ask] | The one thing you need from the user | a photo of the error message | Asking for more than you need |
| [Phone] | The number for urgent issues | 555-0142 | A personal mobile number that ends up on every ticket |
| [Your name] | The technician's first name and team | Dana, Harbor IT support | "The IT team," which gives the user no one to answer |
Check The Reply Before You Send
Users skim, so the problem and the next step come before any instructions. Run this check on every reply; a short outage notice or merge note can skip what doesn't apply.
Where To Keep Them
The best place is your helpdesk, so replies stay on the ticket. Email clients can hold them too.
Gmail has a Templates setting under Settings, Advanced, and you can only turn it on and use it from a computer. You insert a template from the compose window through More options, Templates.
The new Outlook and Outlook on the web use My Templates, saved to your primary mailbox. Shared mailboxes depend on setup. In new Outlook, templates you create in a shared mailbox that hasn't been promoted to a full account are available only to you. In a promoted one, anyone with access who also promotes it can view and edit them. In Outlook on the web, the same split depends on whether you open the shared mailbox in the same tab as your own or with Open another mailbox.
Whatever tool you use, keep one master copy in a knowledge base article or shared document, and change it first.
Acknowledgment Templates
Send an acknowledgment when you can't solve the ticket in the first reply. If you can fix it in five minutes, skip it and send the fix.
1. Ticket Received, During Business Hours
Use this as the first human reply on a normal-priority ticket. Use your real target for [Time], not the contract maximum.
Subject: #[Ticket #] We're on it: [Problem]
Hi [First name],
Thanks for letting us know that [Problem].
I've logged it as ticket [Ticket #] and I'm handling it.
Next step: I'll [Next step] by [Time].
You don't need to do anything until then.
If this gets worse or stops you working, call [Phone].
[Your name]2. Ticket Received After Hours
Give the after-hours route only if your agreement covers one.
Subject: #[Ticket #] Received: [Problem]
Hi [First name],
We've received your request about [Problem] as ticket
[Ticket #]. Our support hours are [Hours], so a
technician will pick it up at [Time] on [Day].
If this is stopping your business from working, call
[Phone] for urgent support. After-hours work is billed
at [After-hours rate] under your agreement.
[Your name]For internal IT and schools, drop the billing sentence.
3. Urgent Ticket Acknowledged
Use this for a high-priority ticket, such as a server down or a whole office offline. Pair it with a phone call; the email confirms the call.
Subject: #[Ticket #] Urgent: working on [Problem] now
Hi [First name],
I've just called you about [Problem]. Confirming here:
- I'm working on it now as top priority.
- Next update: [Time], even if nothing has changed.
- Fastest way to reach me: [Phone].
If you notice anything new, such as more people
affected, reply here or call.
[Your name]4. Request Sent Outside The Queue
Use this for requests by direct email, text, or hallway. A one-person school IT department described the problem on r/k12sysadmin: "I usually reply back 'Please submit a ticket,' but they rarely do." This reply creates the ticket, then teaches the route.
Hi [First name],
Happy to help with [Problem]. I've added it to the
helpdesk for you as ticket [Ticket #], so it won't get
lost in my inbox.
Next time, send requests to [Helpdesk email] and they'll
reach whoever is on duty, even when I'm out.
I'll [Next step] by [Time].
[Your name]Asking For More Information
Diagnosing problems and documenting what users describe are both core duties of support specialists. These templates ask for the description in a form a non-technical user can answer.
5. Need More Details
Use this when the ticket says "it's broken" and nothing else. It's the one case where a short numbered list beats a single ask, because you can't start without any of it.
Subject: #[Ticket #] Quick questions about [Problem]
Hi [First name],
I want to fix [Problem] on the first try, so I need a
little more detail:
1. What were you doing when it happened?
2. What does the screen say? A photo is perfect.
3. Which computer or device? The name is on the
sticker, for example [Device name example].
Reply with whatever you have. I'll start as soon as I
hear back.
[Your name]6. Remote Session Needed
Name the tool, the time, and what the user will see. An unexpected remote-access prompt looks like a scam.
Subject: #[Ticket #] Can I connect to your computer at [Time]?
Hi [First name],
To fix [Problem], I need to see your screen. Could I
connect remotely at [Time]? It takes about [Minutes]
minutes.
What you'll see: a prompt from [Remote tool name] asking
you to allow the connection. Click Allow only if the
prompt names [Your name] or [Company name].
If that time doesn't work, reply with one that does.
[Your name]7. Approval Needed
Use this when a request needs a manager's sign-off. Copy the approver so the user doesn't have to chase them.
Subject: #[Ticket #] Approval needed: [Request]
Hi [Approver name],
[First name] has asked for [Request]. Before I set it
up, I need your approval as [Approver role].
Reply "Approved" to this email and I'll complete it by
[Time]. If you'd rather not approve it, reply "No" and
I'll let [First name] know.
[First name], I'll hold the ticket until [Approver name]
replies.
[Your name]Password, Account, And Access Templates
NIST's digital identity guidelines say account recovery "SHALL cause a notification to be sent to the subscriber or their designee." The notice exists "to help detect the fraudulent use of account recovery." Your identity system may send its own notice. A short reply after every reset is a good team habit on top of it, not a replacement.
Watch out
Never type a password into a ticket reply. Tickets are stored, forwarded, printed, and searched. Give a temporary password by phone or in person, and require a change at first sign-in.
8. Password Reset Done
Use this after any password reset, even when the user asked by phone. The last paragraph tells them what to do if they didn't ask.
Subject: #[Ticket #] Your password was reset
Hi [First name],
I reset the password for [Account] at [Time] today, as
you asked by [Channel]. I gave you the temporary
password by phone; you'll be asked to choose a new one
when you sign in.
Didn't ask for this? Call us at [Phone] right away.
Don't reply to this email with any password.
[Your name]9. Account Locked Out
Use this after a lockout from failed sign-ins. If you can't explain the failed attempts, treat the ticket as a possible security issue.
Subject: #[Ticket #] Your account is unlocked
Hi [First name],
Your [Account] account locked after several wrong
passwords. I've unlocked it, and your password hasn't
changed.
A common cause is an old password saved on a phone or
second computer. If it locks again today, tell me which
devices use this account and I'll check them.
If you didn't try to sign in around [Time], call
[Phone] so we can check the account.
[Your name]10. MFA Device Change
Use this when a user replaces the phone with their authenticator app. NIST says that when a new authenticator is added, the provider "SHALL notify the subscriber via a mechanism independent of the transaction binding the new authenticator." Send this to the user's email and confirm by phone.
Subject: #[Ticket #] Sign-in method changed on your account
Hi [First name],
Today at [Time] we registered a new sign-in device for
[Account]: [Device description]. Your old device no
longer works for sign-in.
You asked for this by [Channel] on [Date]. If you
didn't, call [Phone] now and we'll lock the account.
[Your name]11. Identity Check Before A Reset
Use this when a reset request comes from an address or number you can't tie to the user. CISA's advice for suspicious messages is to look up another way to contact the person, not to use the details in the message.
Subject: #[Ticket #] Let's confirm it's you
Hi,
We received a request to reset the password for
[Account]. Before we change anything, we need to confirm
it's you.
I'll call the number we have on file for [First name]
at [Time]. If that number has changed, ask your manager
to email us from their work account.
We won't reset the password from this email thread.
[Your name]12. New Hire Accounts Ready
Send this to the hiring manager, not the new hire's new mailbox, which they can't open yet. Sign-in details go in person or by phone on day one.
Subject: #[Ticket #] [New hire name] is set up for [Start date]
Hi [Manager name],
[New hire name]'s accounts and equipment are ready for
[Start date]:
- Email: [Email address]
- Access: [Systems and shared folders]
- Device: [Device and asset tag], at [Location]
I'll meet [New hire name] at [Time] on day one to set
the password and sign-in method. Anything missing from
the list? Reply by [Deadline].
[Your name]13. Leaver Access Removed
Send this to the manager or HR contact who asked.
Subject: #[Ticket #] Access removed for [Leaver name]
Hi [Manager name],
As requested, [Leaver name]'s access was turned off at
[Time] on [Date]:
- Sign-in disabled for: [Systems]
- Email: [Forwarded to / shared with] [Person]
- Files: moved to [Location]
- Equipment to collect: [Device and asset tag]
Tell me by [Date] if anyone else needs access to their
email or files.
[Your name]One more NIST line belongs in your password policy, not a template: verifiers "SHALL NOT require subscribers to change passwords periodically." They must force a change if there is evidence the password has been compromised.
Outage And Incident Templates
An outage changes who you're writing to: one user becomes everyone. Incident management guidance calls for proactive updates to end users and stakeholders on the incident status, resolution progress, and any actions required from them. Google's SRE book gives a communications role the job of periodic updates to stakeholders, "usually via email." In a three-person MSP, that's whoever isn't fixing the problem.
14. Outage: First Notice
Send this as soon as you've confirmed the outage, before you know the cause.
Subject: [Service] is down. Next update at [Time]
Hi all,
[Service] stopped working at [Start time]. We know, and
we're working on it now.
Affected: [Who or what is affected]
Not affected: [What still works]
Workaround: [Workaround, or "none yet"]
You don't need to open a ticket for this. If you already
did, we've linked it to this outage.
Next update: [Time], even if nothing has changed.
[Your name], [Team name]15. Outage: Update
Send this at the time you promised, every time. Number the updates so people can tell whether they missed one.
Subject: Update [N]: [Service] still down. Next update at [Time]
Hi all,
[Service] is still down.
What we know: [Cause, or "we haven't found the cause
yet"]
What we're doing: [Current action]
What you can do: [Workaround]
Next update: [Time].
[Your name], [Team name]16. Outage Resolved
Send this when the service is back and at least one user has confirmed it.
Subject: Resolved: [Service] is working again
Hi all,
[Service] is working again as of [End time].
What happened: [One-sentence cause]
What we changed: [One-sentence fix]
What you may need to do: [Action, for example "restart
Outlook," or "nothing"]
If something still doesn't work for you, reply to this
email and we'll open a ticket for you.
[Your name], [Team name]17. Planned Maintenance Notice
Send it a few working days ahead and again the day before.
Subject: Planned maintenance: [Service] unavailable
[Day], [Start]–[End]
Hi all,
We'll be updating [Service] on [Day] from [Start] to
[End]. During that time you won't be able to [Effect].
Before you leave on [Day before]: [Action, for example
"save your files and close the accounting program"].
If this time is a problem for your team, reply by
[Deadline] and we'll look at another window.
[Your name], [Team name]18. Phishing Report Received
Thank the user, because reporting is the behavior you want, and keep only the block that matches your verdict.
Subject: #[Ticket #] Thanks for reporting that email
Hi [First name],
Thanks for sending this to us. Reporting it was the
right call.
[Keep one of the two blocks below and delete the other.]
[Block A, phishing:]
It's a phishing email. Please delete the original.
Don't reply to it or click any link or attachment in
it, including "unsubscribe."
Did you click a link or enter a password before you
reported it? Call [Phone] now, and we'll check your
account and device with you.
[Block B, safe:]
It's safe. It came from [Sender], and you can [Action].
[Your name]The delete line follows CISA's advice: delete the message without replying or clicking any attachment or link, "including any 'unsubscribe' link." CISA also notes that some phishing emails now have perfect grammar and spelling.
Delay, Escalation, And Hand-Off Templates
Escalation paths should be defined for incidents that front-line support can't resolve. The user doesn't care about your tiers. They care that someone still owns the ticket, and that they hear about a slip before the deadline passes.
19. We'll Miss The Time We Promised
Send this before the promised time, not after. Give the reason in one line and a new time you can keep.
Subject: #[Ticket #] New time for [Problem]: [New time]
Hi [First name],
I told you I'd [Promised step] by [Old time], and I
won't make it. [One-line reason, for example "the
replacement license hasn't arrived yet"].
New time: [New time]. If that's a problem for your
work, call [Phone] and we'll look for a workaround.
[Your name]20. Escalated Or Handed Off
Use this when the ticket moves to another technician or team. Name the new owner.
Subject: #[Ticket #] [New owner] is taking over [Problem]
Hi [First name],
[Reason, for example "This needs access to the
firewall" or "I'm out from [Date] to [Date]"], so
[New owner] is taking over your ticket.
[New owner] has everything we've tried so far. You
won't need to explain it again.
Expect to hear from [New owner] by [Time].
[Your name]21. Waiting On A Vendor
Include the vendor's case number and your own check-in date.
Subject: #[Ticket #] Waiting on [Vendor] for [Problem]
Hi [First name],
The cause of [Problem] is on [Vendor]'s side. I've
opened a case with them: reference [Vendor case #].
They've told us to expect [Vendor estimate]. I'll check
with them on [Day] and update you then, whether or not
they've finished.
In the meantime: [Workaround, or "there's no
workaround yet"].
[Your name]22. Parts Ordered
Give the order date, the expected delivery, and what to use meanwhile.
Subject: #[Ticket #] Replacement [Part] ordered
Hi [First name],
The [Part] in your [Device] has failed, and I ordered a
replacement on [Date]. Expected delivery: [Date].
Until then: [Loaner or workaround].
I'll book the install with you once it arrives. The
ticket stays open until the new part is working.
[Your name]Subscribe to the SherpaDesk Blog.
Get Tips for Running IT With a Small Team.
Loading form…
The form couldn’t load. Please try again.
Or start your free trial →SHERPADESK · FREE TRIAL
Resolve tickets.
Turn time into revenue.
Bring support tickets, billable time, and invoicing into one place. Built for small IT teams and MSPs.
- 14 days free
- No credit card required
After your trial, keep your first agent free forever.
SHERPADESK · LIVE DEMO
See tickets, time,
and billing work together.
Walk through ticketing, time tracking, and billing with a product specialist. See how SherpaDesk fits the way your team works.
- 15 minutes
- Your workflow, your questions
A live walkthrough tailored to your team.
Closing Ticket Due To No Response: Template And Follow-Ups
When a user stops replying, use a short, written sequence that ends in a close the user can come back from. Below, the first question counts as attempt 1, so the sequence is three attempts, then the close.
Memorial University of Newfoundland's IT office publishes one: if it doesn't hear back, it makes three attempts to reach the user by email, Teams chat, phone, or voicemail. "If we do not receive a response after the third attempt, your ticket will be closed." Tickets won't close within the first week unless the issue is resolved or rescheduled repeatedly, and security issues such as virus or malware concerns are exceptions.
-
Day 1, attempt 1: Ask once, clearly
Send the question with one ask and a time. Set the ticket to a waiting status so the team can see it's with the user. Whether that also pauses your response clock depends on your helpdesk and its settings.
Common mistake: asking three questions, so the user answers one and the ticket stalls anyway.
-
Day 3, attempt 2: Follow up, and change the channel
Send template 23, or template 24 if the problem may have gone away on its own, and try a call or chat message too. A different channel reaches people who filter helpdesk email.
-
Day 5, attempt 3: Final notice with a date
Send template 25 and name the closing date, here day 8.
-
Day 8: Close
If there's still no answer, close with template 26, listing the dates of the three attempts.
Example: the user replies on day 10. If your helpdesk reopens tickets on reply, the work continues on the same ticket; if not, link the new ticket to the old one.
23. Follow-Up (Attempt 2)
Subject: #[Ticket #] Checking in: [Problem]
Hi [First name],
I'm following up on [Problem]. To keep going, I need
[Ask].
If it's easier to talk, call me at [Phone] or reply
with a time that suits you.
[Your name]24. Follow-Up When It May Have Fixed Itself (Attempt 2)
Subject: #[Ticket #] Still need help with [Problem]?
Hi [First name],
I haven't heard back about [Problem], and I don't want
it to fall through the cracks.
- Still a problem? Reply with [Ask] and I'll pick it up.
- Fixed itself? Reply "fixed" and I'll close the ticket.
[Your name]Before you use templates 25 and 26, check what your helpdesk does with a reply to a closed ticket. Both templates promise only that you'll pick the work up again, which holds whether the reply reopens the ticket or starts a new one.
25. Final Notice Before Closing (Attempt 3)
Subject: #[Ticket #] Closing on [Date] unless we hear back
Hi [First name],
This is our third try to reach you about [Problem]. If
we don't hear from you by [Closing date], we'll close
the ticket.
Closing it doesn't mean the problem is gone. If you
still need help after that, reply to this email and
we'll pick it up from there.
[Your name]26. Closing Ticket Due To No Response Template
This is the closing note itself. It states the facts without blame, and the last line tells the user how to come back.
Subject: #[Ticket #] Closed: [Problem]
Hi [First name],
We tried to reach you about [Problem] on [Attempt 1
date], [Attempt 2 date], and [Attempt 3 date] and
didn't hear back, so we've
closed ticket [Ticket #].
If you still need help, reply to this email and we'll
pick it up from there with everything we've done so
far.
[Your name]Closing Templates For Solved Tickets
When an incident is resolved, it's formally closed, with the actions taken documented and the knowledge base updated. The closing reply is the user's half of that record: what you did, what to watch for, and how to come back.
27. Fixed, Closing Unless You Tell Us Otherwise
Subject: #[Ticket #] Fixed: [Problem]
Hi [First name],
[Problem] should be fixed. Here's what I did:
[One or two plain sentences].
Please check it the next time you [Action]. If it's
working, you don't need to reply. If anything's still
off, reply to this email and I'll pick it up again.
I'll close the ticket on [Date] if I don't hear back.
[Your name]28. Duplicate Ticket Merged
Subject: #[Ticket #] Merged with ticket [Original #]
Hi [First name],
This looks like the same issue as ticket [Original #],
which we're already working on. I've merged the two so
all the details are in one place.
Updates will come from ticket [Original #]. Nothing is
lost, and you don't need to do anything.
[Your name]29. Request Declined Or Not Supported
Say no once, give the reason in its own sentence, and offer the nearest yes. Keep the exception paragraph only for internal rules someone can waive; a license limit can't be waived, so offer the right license or an approved alternative.
Subject: #[Ticket #] About your request for [Request]
Hi [First name],
We can't [Request] because [Reason, for example "the
software isn't licensed for business use"].
What we can do instead: [Alternative, for example "buy
the business license, about [Cost]" or "use [Approved
app], which does the same job"].
[Optional. Keep only if the rule allows exceptions:]
If you think this needs an exception, [Approver role]
can approve one. Reply and I'll send them the details.
[Your name]30. Closing With A Satisfaction Survey
Subject: #[Ticket #] Closed: [Problem]
Hi [First name],
We've closed ticket [Ticket #] for [Problem].
How did we do? Rate this ticket in one click:
[Survey link text, for example "Rate ticket 4821"]
If the problem comes back, reply to this email.
[Your name]Use link text such as "Rate ticket 4821," not "click here." W3C accessibility guidance asks for link text that identifies the purpose of the link.
Support Ticket Response Examples For MSP Contracts And Billing
These four replies protect an MSP's margin. They turn a scope argument into a yes/no question the client answers in writing, before the work starts.
One r/msp member described the move in a thread about clients who expect instant answers. They tell the client: "If you want immediate response this is not covered under our agreement, we charge high emergency hourly rate. Do you want us to proceed?" Templates 31 and 32 put that question in writing.
31. Out Of Scope: Approval Needed
Use this when a request falls outside the client's agreement, such as an office move or a project. Keep one pricing line and delete the other.
Subject: #[Ticket #] Approval needed: [Request] is billable
Hi [Client contact],
[Requester] has asked us to [Request]. This isn't covered
by your [Agreement name], so it would be billed
separately:
[Keep one line:]
Estimate: [Hours] hours at [Rate] per hour.
Fixed price: [Amount].
Reply "Approved" and we'll schedule it for [Date]. If
you'd rather not go ahead, reply "No" and I'll let
[Requester] know.
[Your name]Send it to the person who signs the invoices.
32. Emergency Or After-Hours Rate
Subject: #[Ticket #] Urgent work on [Problem]: please confirm
Hi [First name],
Under your agreement, [Problem] is a [Priority] ticket,
which we answer within [Response target] during
business hours.
If you need us on it right now, we can start
immediately at our emergency rate of [Emergency rate]
per hour.
Reply "Go ahead" and we'll start now. Otherwise we'll
handle it at [Time].
[Your name]33. Prepaid Hours Running Low
Send this before the last prepaid hour is used, not after.
Subject: Your prepaid support hours: [Hours left] left
Hi [Client contact],
A quick heads-up: your prepaid block has [Hours left]
hours left of [Hours total] as of [Date].
When the block runs out, new work is billed at
[Overage rate] per hour until you renew. To add another
block of [Block size] hours for [Block price], reply
"Renew" and we'll send the invoice.
[Your name]For how prepaid blocks fit into pricing, see our guide to managed services pricing.
34. Response-Time Reminder
Use this when one user sends every ticket as urgent. Send it to the client contact, and keep it factual.
Subject: Response times under your agreement
Hi [Client contact],
A few recent tickets from your team were sent as urgent.
So everyone has the same picture, here's what your
agreement covers:
- Urgent (business stopped): response within [Time]
- Normal: response within [Time]
- After hours: [After-hours terms]
This month we answered [N] of [N] tickets within these
times. If your team needs faster response, we can talk
about a different plan.
[Your name]Fill in "[N] of [N]" only with numbers from your helpdesk's reports, or delete the line.
Templates For School IT Teams
School IT replies are shorter, and they name a loaner or a workaround near the top.
35. Student Device Repair Received
Subject: #[Ticket #] Repair for [Student name]'s [Device]
Hi [Teacher or parent name],
We have [Student name]'s [Device] (asset tag [Asset tag])
for [Problem].
Loaner: [Student name] has loaner [Loaner tag] today.
Please return it when the repair is done.
Expected repair date: [Date]. We'll email you when it's
ready for pickup at [Location].
[Your name], [School] TechnologyKeep student details to the name and asset tag the repair needs.
36. Classroom Tech Before Class
Subject: #[Ticket #] [Room]: [Problem]
Hi [Teacher name],
Got it: [Problem] in [Room].
I can be there at [Time]. If class starts before then,
try this first: [Quick fix, for example "switch the
projector input to HDMI 2"].
If that doesn't work, text "[Room]" to [Phone] and I'll
come straight over.
[Your name]Why Templates Help, And How To Keep Them Human
Templates make the best technician's wording everyone's, and they set expectations before a conflict starts. One r/msp member's contract promises four hours, and every new ticket gets an automated email that reminds the client of that time. Another warned that pointing to the contract later means "you've already lost because things have degraded into a conflict."
They have limits. One r/msp member, discussing a client who wanted five-minute responses, said simple yes/no tickets "are stuff you can templateize, maybe." Another drew the line between replying and fixing: "We responded, not solve the problem, which are two different things…"
A template carries the structure. The technician still supplies the diagnosis.
Never type a password into a ticket reply.
Write It So It Reads In One Pass
Digital.gov warns that "long, complex sentences containing multiple phrases and clauses can confuse the reader," and notes that pronouns, active voice, and base verbs help cut excess words. In a ticket, that means "I reset your password," not "Your password has been reset by the support team." It also means one name for one thing: different terms for the same object confuse readers. If the user says "the shared drive," don't switch to "the file server."
- Keep a [Problem] bracket in each template so every reply restates the issue
- Name a clock time or a day for every next step
- Edit one sentence by hand so it fits this ticket
- Delete templates nobody has used in six months
- Send a template before checking it still fits the ticket's history
- Promise to reply "soon" or "as soon as possible"
- Paste a template into an angry thread without reading the last message
- Keep three versions of the same reply
How Much Time They Save
Count the templated replies your team sends in a day, and estimate the minutes a template saves on each.
Estimate the minutes templates save per day
replies per day × minutes saved per reply. Your numbers stay in the browser.
What To Look For In Your Helpdesk's Reply Tools
For a wider comparison, see our guide to ticketing system software for small IT teams.
| Capability | Why it matters | Templates |
|---|---|---|
| Email to ticket | Replies from the user's inbox land on the same ticket | All |
| Saved replies shared by the team | One master copy instead of a private copy per technician | All |
| Placeholders that fill themselves | Name and ticket number go in without typing | All |
| A waiting status | Shows the ticket is with the user; some tools also pause the response clock | 23–26 |
| Reply to linked tickets at once | One outage update reaches every linked ticket | 14–16, 28 |
| Knowledge base links in replies | A how-to link replaces a page of pasted steps | 5, 27, 36 |
| Time logged on the ticket | The time a reply took reaches the invoice or the contract | 31–33 |
| Editable closing email | Closing notes and survey links go out without manual work | 26, 27, 30 |
| SLA clocks per priority | The [Time] you promise matches the target you track | 1–3, 32, 34 |
Our guide to PSA software shows where tickets, time, and contracts meet.
A Filled-In Example: One Ticket From Start To Finish
Example: Harbor Dental is a client of a three-technician MSP. At 9:12 a.m., Maria Lopez at the front desk emails: "Outlook keeps asking for my password and won't take it." Here's the ticket in three emails and a follow-up.
Subject: #4821 We're on it: Outlook password prompt
Hi Maria,
Thanks for letting us know that Outlook keeps asking for
your password and won't take it. I've logged it as
ticket 4821 and I'm handling it.
Next step: I'll check your account from our side by
10:00 a.m. You don't need to do anything until then.
If email stops working completely, call 555-0142.
Dana, Harbor IT supportDana finds the account locked after failed sign-ins. Maria changed her password last week, and the old one is still saved on the front desk tablet.
Subject: #4821 Your account is unlocked
Hi Maria,
Your Microsoft 365 account locked after several wrong
passwords. I've unlocked it, and your password hasn't
changed.
The cause is the front desk tablet: it still has your
old password saved. Could you leave the tablet on the
desk at 12:30 so I can update it remotely?
Dana, Harbor IT supportThe security line from template 9 is gone: Dana knows where the failed sign-ins came from. The tablet stays off at 12:30, and Maria doesn't answer. Two days later, Dana sends template 23, asking for the tablet to be switched on for 10 minutes. Maria replies with a time, Dana updates the tablet, confirms Outlook signs in on both devices, and logs 25 minutes on the ticket.
Subject: #4821 Fixed: Outlook password prompt
Hi Maria,
The Outlook password prompt should be fixed. I updated
the saved password on the front desk tablet, which was
locking your account.
Please check it the next time you open Outlook on the
tablet. If it's working, you don't need to reply. If
anything's still off, reply to this email.
I'll close the ticket on Friday if I don't hear back.
Dana, Harbor IT supportThe 25 minutes Dana logged are on the ticket, ready for Harbor Dental's invoice or contract.
Download All Templates
All 36 templates, numbered and in the same order, in one plain-text file. Paste it into your helpdesk, a Gmail template, or a knowledge base article as your master copy.
How this works in SherpaDesk
Answer, Log Time, And Update The Ticket From One Email
A helpdesk and PSA a small IT team can run alone. You forward your support inbox to a dropbox address, and incoming emails become tickets. When you reply from your inbox, you can act on the ticket in the same message with commands such as cmd onhold, cmd escalate, or cmd close. Add cmd time 0.25 and the reply logs 15 minutes on the ticket. Several commands fit in one reply.
A Wait (Tech) clock shows how long the user has waited for you, and it resets when any technician responds. For how-to answers, you attach a public knowledge base article to the response instead of pasting steps.
Base Camp is $45 per agent per month ($40 billed annually), and your first agent is free, forever. 14 days free, no card, and setup takes less than 2 minutes.
Where Templates Fall Short
Templates handle the routine. They can't diagnose a ticket you haven't read, and they shouldn't carry a legal notice, such as a data breach notice, which should come from the owner with legal advice. With an angry user, answer the complaint in your own words first and paste only the facts: the timeline and the next step.
Who this isn't for
Teams that need sales, refund, or shipping replies: this library covers IT support queues only. If you run SherpaDesk, note that it has no built-in survey tool. For template 30, you edit the closed-ticket email message and add your own survey link.
If your queue keeps producing the same ticket, the template is a symptom. Turn the fix into a written procedure; our guide to helpdesk SOPs covers how.
FAQ
What is a canned response?
A canned response is a saved reply a technician reuses for a situation that comes up often, then fills in for the ticket at hand. The good ones keep a bracket for the user's problem, so each reply still reads as written for that person. The 36 templates in the template index are canned responses for IT queues.
How do you close a ticket when the user doesn't respond?
Write the sequence down and use it for everyone. Make three contact attempts on more than one channel, and use the third as the final notice that names the closing date. Then close with a note that says how to come back. Some tickets, such as security issues, are exempt from closing for no response. The follow-up sequence has a template for each step.
Does an automatic reply count as a response?
That depends on how your agreement defines a response, so check the wording. For the user, an automatic reply confirms the ticket exists, and some MSPs use it to restate their response time. Follow it with a human reply that names a person and a time, such as template 1.
Should you ever send a password in a ticket reply?
No. A password in a ticket stays readable in the history, in forwards, and in printouts long after it's needed. Give a temporary password by phone or in person, require a change at first sign-in, and send the user a notice that the reset happened. Template 8 is that notice.
How many response templates does a small helpdesk need?
Start with the situations you answer every week, such as acknowledgment, more details, a password reset, an outage notice, the follow-ups, and a closing note. Add others when a situation repeats. A library people can remember gets used; a sprawling one sends technicians back to typing.
Can I use these templates in Gmail or Outlook?
Yes. Gmail and Outlook both store reusable templates, with limits on computers and shared mailboxes covered in where to keep them. For a team, keep the master copy in a shared knowledge base article or document so every technician sends the same version.
Patrick co-founded SherpaDesk and has led it as CEO since 2013. He has worked with IT service providers since 1998, first on network projects for schools and government offices, then on the helpdesk software their technicians use every day.