How to Submit an IT Support Ticket
Your printer stopped working. Your email won't sync. You can't open that file your client just sent. Whatever the IT problem, the fastest path to resolution is a well-written support ticket.
Not a phone call. Not a hallway mention to "the IT person." Not an email with the subject line "HELP."
A ticket. Here's why, and here's how to write one that actually gets resolved quickly.
Why Tickets Beat Phone Calls and Emails
Tickets are tracked. Nobody forgets about a ticket. It sits in a queue with a status, a priority, and an owner. An email can get buried. A hallway conversation can be forgotten.
Tickets have context. When you write down the problem, you organize your thinking. You include details you'd forget to mention on the phone. And when a technician picks it up, they have everything they need to start working.
Tickets are visible. You can check the status any time. No need to wonder if someone's working on it. No need to send a "just following up" email.
Tickets create history. If the same problem happens again, there's a record of how it was fixed last time. This speeds up resolution from hours to minutes.
How to Write a Ticket That Gets Resolved Fast
The difference between a ticket that gets resolved in 30 minutes and one that takes all day often comes down to how it's written.
Bad Ticket
Subject: Computer broken
My computer isn't working. Please fix.
This tells the technician almost nothing. They'll need to ask follow-up questions, which adds hours to the resolution time.
Good Ticket
Subject: Outlook won't open - freezes on splash screen since this morning
When I try to open Outlook this morning, it shows the splash screen for about 10 seconds and then freezes. I have to use Task Manager to close it. I've restarted my computer twice and the problem persists.
- Computer: DESKTOP-LV2847
- Started: This morning (Feb 15)
- Other apps work fine
- I can access email through outlook.com in the browser
Screenshot of the frozen screen attached.
This ticket will likely be resolved on the first touch because the technician has everything they need.
The Formula
Every good ticket answers these four questions:
- What were you doing? ("I was trying to open Outlook")
- What happened? ("It freezes on the splash screen")
- What did you expect? ("I expected it to open normally")
- What have you tried? ("I restarted twice, same result")
Add any error messages (exact text, not paraphrased) and a screenshot if possible.
Using the Self-Service Portal
Most managed IT providers offer a self-service portal where you can submit tickets, track progress, and communicate with technicians.
Submitting a New Ticket
- Log in to your provider's portal
- Click "New Ticket" or "Submit a Request"
- Choose a category if available (helps route to the right team)
- Write a clear subject line - Specific is better than vague
- Describe the issue using the formula above
- Attach screenshots - They eliminate guesswork
- Submit - You'll get a confirmation with a ticket number
At Las Vegas IT Services, you can submit a ticket here. Our portal also offers templates for common requests.
Ticket Templates Save Time
For routine requests, templates pre-fill the important fields so you don't have to write everything from scratch:
- New Employee - Name, start date, license, department, access needs
- Offboard Employee - Disable accounts, transfer files, revoke access
- Website Edit - Describe the change, provide content
Templates ensure nothing gets missed and help your IT provider process the request faster.
Tracking Your Ticket
Once submitted:
- Check status any time by logging into the portal
- Read updates from your technician as they work on the issue
- Add comments if you have new information (e.g., "Actually, it started working but then froze again")
- Get email notifications when your ticket is updated
You don't need to call to check on a ticket. The portal shows real-time status.
Priority Levels: What Gets Fixed First
IT providers prioritize tickets based on impact:
| Priority | Example | Typical Response |
|---|---|---|
| Critical | Email down for everyone, security incident | Immediate |
| High | One person can't work, server issue | Within 1 hour |
| Medium | Software not working, slow computer | Within 4 hours |
| Low | Feature request, how-to question | Within 1 business day |
If your issue is truly critical (affecting multiple people or involving a security incident), say so in the ticket. But don't mark everything as critical-it slows down response for actual emergencies.
Common Mistakes That Slow Things Down
Submitting multiple tickets for the same issue. This creates confusion, not urgency. Submit one ticket and add updates to it.
Calling, emailing, AND submitting a ticket. Pick one channel. The ticket is best. Sending the same request three ways doesn't make it faster-it creates duplicate work.
"It's not working" without details. The technician's first response will be asking for the details you could have included upfront. Save that round trip.
Not mentioning what changed. "It was working yesterday" is useful information. "I installed a program yesterday and now it's broken" is even more useful. If anything changed before the problem started, mention it.
Waiting too long to report. A small issue today can become a big problem next week. If something seems off, report it. A quick ticket is faster than an emergency call.
The Bottom Line
A support ticket is the fastest way to get IT issues resolved. Write clear descriptions, include screenshots, and use the self-service portal to track progress. It's not bureaucracy-it's efficiency.
Need IT support with a self-service portal? View our plans or contact us to get started.