Clear and credible information on a ticket is what makes an efficient customer response a reality. When the message is vague, the chain of communication is disrupted. Agents are forced to chase details that should have been the initial sections. This dysregulated workflow slows down the resolution and creates frustration. This narrows down to one issue: the format of the ticket.
This article addresses this gap. Below, you’ll find 10 realistic help desk ticket examples. These are based on common IT and support scenarios. Each one presents a structure for a ticket that gets resolved faster. These are either to-the-point messages or a consistent timestamp format. You should use these examples as a model for your own tickets. If your team receives most of these requests in chat, a Slack ticketing system can turn them into tracked tickets without pulling anyone out of the conversation.
What Makes a Good Help Desk Ticket?
An ideal help desk ticket has all the information that the support agent needs to immediately start the task at hand without the need for a follow-up question. Although it takes the sender an additional two minutes to compose, the support agent saves the time that they would have spent asking follow-up questions. Simply put, regardless of the requester, there is a consistent set of attributes that the best tickets have.
- A to-the-point, summarized issue statement
- A body describing the gap between user goals and system response
- Error messages (copied or pasted)
- Descriptions of the issue with the time and the system on which the issue occurred
- Help desk software analysis
- Actions or steps taken before ticket submission
10 Help Desk Ticket Real-World Scenarios
The 10 help desk ticket scenarios below cover the requests IT and support teams see most often, from password resets and VPN failures to phishing reports. Each one includes what usually causes the issue, how it's typically resolved, a real ticket example with subject line and body, and what makes that ticket easy to work.
Password Reset Request
What it is: A user cannot log into a company account after a forgotten password, expired credentials, or an account lockout from failed attempts. Password resets are the single highest-volume ticket type most IT desks handle.
Common causes: Forgotten password, account lockout after failed attempts, expired credential policy, self-service portal outage, Active Directory sync lag.
How it's resolved: Verify identity through a security question, MFA fallback, or manager confirmation. Trigger a password reset from the identity provider or Active Directory. Send a temporary password or one-time reset link. Confirm the user can log in and close the ticket.
Example Ticket
Subject: Password reset required: Active Directory account locked out
Body:
Hi, I logged in this morning and was unable to log into my Active Directory account. I failed to reset the portal at self-service. It shows the account is not present in the system. My Windows 11 is connected to the office network. I need access for a client call at 10:00 am.
Tier: Identification | Preference: High
What makes this a good ticket: Specified time. Specific error message from the portal. Required deadline.
Microsoft Teams Messages not Delivering
What it is: Messages sent through Teams show as delivered on the sender's side but never arrive with the recipient. Often isolated to one user or one channel type.
Common causes: Corrupted local cache, outdated app version, Microsoft 365 service disruption, tenant-level policy change, network firewall blocking a Teams endpoint.
How it's resolved: Confirm scope (one user or many). Check the Microsoft 365 admin service health dashboard. Clear the Teams cache, sign out and back in, and confirm behavior on both desktop and web. If the issue is tenant-wide, escalate to the Microsoft 365 admin.
Example Ticket
Subject: Teams messages sent showing but not received (all chats); error began at 8:30 am
Body:
Ever since I clocked in at 8:30 am, the messages I attempt to send via Microsoft Teams are showing as absent on the recipient's end. The delivery tick on my end shows they have been delivered. I signed out of Teams and cleared the cache, but to no avail. Reinstalling the Teams app did not work for me either. The Teams desktop app (v 23306.3314) and the web app available at teams.microsoft.com were both attempted and yielded the same results. Other employees are able to message each other via Teams without issues.
Tier: Software | Preference: Medium
What makes this a good ticket: Scope confirmed. Teams app version (desktop) included. Solution attempts mentioned.
Malfunctioning Printer
What it is: A shared or personal printer stops accepting print jobs, prints blank pages, or shows offline in the print queue. High-impact when the printer is shared across a floor or team.
Common causes: Network drop, print spooler crash, driver conflict after an OS update, low toner or paper jam, IP address change on the printer.
How it's resolved: Confirm the printer is powered on, connected, and shows a ready state. Restart the print spooler service on the client. Clear the print queue. Reinstall or update the driver. If the issue is floor-wide, check the print server and the printer's static IP.
Example Ticket
Subject: Floor 2 shared printer PRT-FL2-HP01 offline
Body:
The shared floor 2 printer PRT-FL2-HP01 is offline, and print jobs are not being processed. This has been an issue for multiple employees since 10 AM. This printer is in a ready state, has power, and an active Ethernet connection. I attempted to clear the print queue on my computer. I also restarted the print spooler and power-cycled the printer to no avail. This is an issue for the entire floor.
Tier: Hardware | Priority: High
What makes this a good ticket: Scope specified. Details of the printer are available.
Network / VPN Connectivity Issue
What it is: A user cannot connect to the corporate VPN, or the tunnel drops during use. Blocks access to internal systems and shared drives.
Common causes: Recent OS or VPN client update, expired certificate, ISP routing issue, MFA push failure, split-tunnel policy change.
How it's resolved: Capture the exact error code and client version. Restart the VPN client and reboot the machine. Confirm the user's certificate is valid. Test from a different network to isolate ISP issues. If the issue is widespread, escalate to network engineering.
Example Ticket
Subject: VPN connection failing with error 789 — Windows 11, started after today's update
Body:
Not able to connect to VPN since 7:30 AM. The VPN worked without problems before the most recent update of Windows 11.
Error code "789": L2TP connection error - security layer processing error
Version: Windows 11 Pro 22H2
As of this morning, after a Windows update, I can no longer access this VPN. My internet is working fine, I can browse and video call. I can see that some of my team members in the same city are having the same issue.
Tier: Network | Preference: High
What makes this a good ticket: Full error code and message. Version numbers. Context about scope.
Email Cannot be Sent or Received
What it is: Outlook or the corporate mail client stops syncing. New mail does not arrive, sent items sit in the outbox, or the client shows a specific sync error. For teams that also route inbound mail to chat, a Slack email integration can keep these tickets moving even when the client is unstable.
Common causes: Mailbox at storage limit, corrupted OST file, Exchange service issue, incorrect server settings after a client update, oversized attachment blocking the outbox.
How it's resolved: Check mailbox size and Exchange service health. Rebuild the OST file. Verify server settings match the current tenant configuration. Send a test message from Outlook Web to isolate whether the issue is client-side.
Example Ticket
Subject: Outlook not sending/receiving since 2:00 PM — error 0x80010108 on Windows 11
Body:
My Outlook has been sending and receiving 0 emails since 11:30 am. I have been alerted to this by a meeting notification that has been flashing and lingering. The notification is displaying the meeting details. I am unable to send an update to the meeting. My Outlook hasn't synced new notifications.
Category: Email & Messaging | Priority: High
What makes this a good ticket: employees being unable to email during critical meetings. Clear timeframe.
2-Factor Authentication App Malfunction
What it is: The MFA app on the user's phone generates codes that fail, usually after a phone restore, new device, or app reset. Locks the user out of every protected system until MFA is reissued.
Common causes: Phone restored from backup (breaks the shared secret), new device without MFA re-enrollment, time drift on the phone, backup codes already used.
How it's resolved: Verify identity through an out-of-band channel such as manager confirmation or a video call. Reset MFA enrollment from the identity provider. Walk the user through re-registering the authenticator app. Issue new backup codes.
Example ticket
Subject: Microsoft Authenticator Code Issues Post Phone Restore
Body:
The Microsoft Authenticator has locked me out of my account. This has occurred after I restored my phone on June 14. It showed me the error message “invalid code, please try again”. I tried to regenerate the code three times, but to no avail. The backup codes are also of no advantage to me (all prompted ‘code already used’). My iPhone 15 runs on iOS 17.4.
Tier: Identification & Access | Priority: High
The standout points: Restoration date. Device and OS details. Backup code and other alternative solutions were tried out.
Permissions/access denied error
What it is: A user cannot open a folder, file share, or application they should have access to. Usually appears as a 403 or "access denied" error.
Common causes: Group membership not synced, permission inherited from a parent folder was changed, role change not yet reflected in Active Directory, expired temporary access.
How it's resolved: Confirm the user's group membership. Compare to a peer with working access. Verify the folder's ACL. If access was recently changed, force a group policy update on the user's machine or re-add them to the correct security group.
Example Ticket
Subject: Access denied to /Finance/Q2-Reports shared drive folder — error 403
Body:
I'm getting "Error 403: Access Denied" when trying to open the /Finance/Q2-Reports folder on the shared drive (\fileserver01\Finance\Q2-Reports). My manager, Priya Raj, has confirmed I should have access and has emailed IT. I'm on Windows 11. Checked that I'm logged into the domain.
Category: Access & Permissions | Priority: Medium
What makes this a good ticket: Exact file path, specific error, named approver, comparison to working state last quarter.
Video conferencing camera not detected
What it is: A webcam works in one application but not another. Often reported minutes before a meeting.
Common causes: App-level camera permission disabled, another application holding the camera, outdated driver, camera privacy setting toggled off in the OS.
How it's resolved: Confirm the camera works in Device Manager and another app. Close every application that could hold the camera. Check camera permissions inside the affected app and in Windows privacy settings. Reinstall the affected app if the issue persists.
Example ticket
Subject: Logitech C920 not detected in Zoom — shows in Device Manager and works in Teams, Windows 11
Body:
This morning, right before my presentation, My Logitech C920 wasn't detected by Zoom. Zoom’s settings showed “No Camera Detected”. The same camera is working in Microsoft Teams and the Windows Camera App. The drives also appear fine. I reinstalled Zoom (v. 5.17.10), but to no avail. The issue is still present only in Zoom. I use Windows 11 Pro 22H2.
Category: Software | Priority: Medium
What makes this a good ticket: Admin error message quoted. The two-part request is clearly stated.
Shared calendar not visible after permission change
What it is: A user cannot see or add a shared calendar after a permission update. Common in teams that manage recurring events through a central calendar.
Common causes: Sharing invitation was sent but not accepted, permission change has not synced, incorrect access level applied, Outlook cache holding old permission state.
How it's resolved: Confirm the sharing invitation was accepted. Verify the permission level (Editor, Reviewer, etc.). Clear the Outlook cache and re-add the calendar manually using the owner's email.
Example Ticket
Subject: Unable to Access Operations Team - 2025 Shared Calendar
Body:
The Operations Team - 2025 shared calendar on Outlook is acting up. My manager, Rachael Voss, updated sharing permissions on June 13. The calendar is not showing on 'Other People's Calendars'. It cannot be found in the 'Add Calendar' search. Rachael confirmed I have 'Editor' access. I tried restarting Outlook. I am using Outlook 365, version 2404, and Windows 11.
Category: Email & Messaging | Priority: Medium
What makes this a good ticket: Specific shared calendar name. Specific permission updater. Request date.
Security incident report
What it is: A user flags suspicious activity, usually a phishing email, unexpected login alert, or a message asking for credentials. High priority regardless of whether the user acted on it. If your team commonly misses alerts, first check that Slack notifications are turned on so security pings do not sit unread.
Common causes: Targeted phishing, spoofed sender domain, credential stuffing attempt against the user's account, malicious link forwarded from a compromised colleague.
How it's resolved: Preserve the original message with headers. Confirm the user did not click links or enter credentials. If they did, reset the account password, revoke active sessions, and check sign-in logs. Report the domain to the mail security gateway and add it to the block list.
Example ticket
Subject: Suspected phishing email received — links to external site, did not click
Body:
I received an email at 11:23 AM today from "support@microsofft-security.com". Subject line: "Urgent: Your account will be suspended in 24 hours." The email contained a link to http://microsofft-security.com/verify. I did not click it. I've forwarded the email as an attachment to security@company.com.
Category: Security | Priority: High
What makes this a good ticket: Exact timestamp. Sender address.
Help desk ticket template (copy-paste ready)
Subject: [app/system failure/s, name of app/system, name]
When did this start: [day, date, time]
Full description: What were you doing? What happened? What were you expecting to happen?
Error message or code:
Environment:
Device type:
Operating system:
Browser (if web-based):
App version (if known):
Is anyone else on your team affected?
What have you already tried:
- Restarted the app
- Cleared cache
- Reinstalled app
How pressing is this (urgency)?
IT help desk ticket template
Subject: [Issue summary, Device name/asset tag]
Requester:
Department:
Date/time issue started:
Device: [Make, model, serial/asset tag]
OS:
Affected application: [App name + version]
What I was trying to do:
What happened instead:
Exact error message:
Steps already tried:
Priority:
Attachments:
Internal request template (HR / Ops)
Subject: [Request summary, Requester name/team]
Requester:
Manager: [include email]
Date needed by:
Cost center/budget code: [Code]
Manager approval:
Request description:
Business justification:
Attachments:
Help desk response examples (for agents)
Acknowledgement, ‘we've received your ticket’
Hi [Name],
Thanks for reaching out. We've received your ticket (#[ID]). It has been assigned to our team.
Expected response time: [X hours].
[Agent name]
Asking for more information
Hi [Name],
Could you share: the exact error message (screenshot works),
the version of [app/OS], and whether this is affecting anyone else on your team?
[Agent name]
Sharing a workaround while we investigate
Hi [Name],
While we work on a permanent fix for [system/app], here are a few workarounds:
[Steps — numbered list]
Only temporary relief steps. We'll update this ticket once the resolution is complete.
[Agent name]
Escalating to a specialist
Hi [Name],
This is outside our scope, so I've passed it on to our [specialist team].
They'll follow up. Your ticket number stays the same: #[ID]. ETA: [timeframe].
[Agent name]
Apologizing for the delay
Hi [Name],
Apologies for the delayed response on #[ID]. Here's where we are: [current status].
Next step: [action]. I'll update you by [specific time] with progress or on progress.
[Agent name]
Internal team ticket examples (IT, HR, Ops)
- Subject: Conference room AV not working — Room 49X, client presentation at 2:00 PM today
Room 49X AV (HDMI, display) has stopped working since 12:30 PM. TV shows "No signal". Client presentation at 2:00 PM. Need a fix or room swap ASAP. Slack me @k.osei.
Category: Facilities/AV
Priority: High
- Subject: New starter equipment — xyz, Finance, starting July 1
Standard Finance setup for xyz, starting July 1.
Needs: standard-spec laptop, Finance shared drive access
Manager: Alex Cossacks.
Budget code: FIN-OPS-22.
Category: New Hire
Priority: Medium
Slack-format ticket examples
Many teams capture requests from Slack threads instead of a portal. Here's what a Slack-format ticket looks like in practice:
@helpdesk: My laptop keyboard is glitching with keystrokes. Started after the morning meeting. MacBook Pro M1, macOS Sonoma 14.3. Restarting to no avail. Still unresolved. Is there a fix, or can I swap devices?
And a follow-up structured submission using a Slack ticket bot:
Issue: Keyboard input glitch
Device: MacBook Pro M1
OS: macOS Sonoma 14.3
Started: This morning
Tried: Full restart
Priority: High
Common Mistakes to Avoid in Help Desk Tickets
To improve response times and resolve issues faster, avoid the mistakes below you can learn from the help desk ticket best practices.
- Vague subject lines ("not working"): A clear subject line helps route your ticket faster and avoids unnecessary back-and-forth with the support team.
- Missing error messages: Always copy the exact error text. Paraphrasing loses critical details that agents need to diagnose the issue.
- No timestamps: Mentioning when the issue occurred helps teams trace logs and identify whether it's an isolated or ongoing problem.
- Multiple unrelated issues in one ticket: Bundling issues slows resolution. Each problem needs its own ticket so it can be assigned and tracked separately.
- Wrong category / wrong team: Check the category guide before submitting to prevent full reassignment rounds that delay your resolution time.
- Setting every ticket to "high priority": Overusing priority flags causes alert fatigue, reserve high priority for issues that are genuinely time-sensitive.
- Updates buried in comments instead of in the main thread: Always reply to the original ticket thread so agents see your updates immediately without hunting through comment chains.
Final Thoughts
A well-written ticket isn't about following a form; it's about giving the agent what they need to help you fast. Rather, you are providing information to the agent that helps them get you what you need as quickly as possible. This includes exact error messages, real timestamps, and what you have tried. Help desk ticket examples and templates in this blog are meant to be easily copied, adapted, and used in your team’s ticketing system.
If your team is outgrowing its current setup, compare the best project management ticketing systems to see how modern teams handle requests that come from chat instead of a web portal.
FAQs
What should be included in help desk tickets?
Help desk tickets should include a detailed and specific subject line. Tickets should also state the requester's intended action and what occurred instead, including the exact error message, the affected system and OS version, and timestamps. Include the steps attempted to resolve the issue.
What makes a good help desk ticket?
Good tickets are written with the understanding that the requester is not available for follow-up. Good tickets also include exact error messages, the system and version, the time of the incident, and the attempted steps.
What is an example of a trouble ticket?
A good example of a help desk trouble ticket is the above VPN connectivity example. It includes detailed information such as the full error code (789), application and version (Cisco AnyConnect 4.10), OS, trigger event (Windows Update), and scope (people it affected as well). With detail at that level, we won’t need to send follow-up questions, and we will be able to resolve the ticket that much quicker.
What are the metrics of help desk tickets?
Common metrics are the first response time, time to resolve, first contact resolution rate (tickets resolved without the need for escalation), and rate of tickets reopened. These metrics only have value if ticketing is done consistently and reliably. That is one reason a standardized help desk ticket template is important.
How do I respond to a support ticket?
A response should acknowledge the problem, state what the next step is, who is responsible, and the timeframe. Help desk response examples above acknowledge the problem, provide additional information, work around the issue, and escalate/close the ticket.
