5 Ways to Submit Better IT Tickets
Submitting an IT ticket is only the first step. A well-written ticket can reduce follow-up questions and help DSA IT focus on solving the problem.
A few weeks ago, we published What Happens After You Submit a Ticket?, which explored what occurs behind the scenes once a support request is submitted. From initial review and assignment to troubleshooting and resolution, a lot happens before a ticket reaches the finish line.
While that process is important, there is another part of the equation that often gets overlooked: the quality of the information included in the ticket itself.
Every ticket starts with information provided by the person experiencing the issue. The more complete and accurate that information is, the faster DSA IT can begin troubleshooting and the fewer follow-up questions are needed before investigation can begin. While our team is always happy to gather additional details, providing a little extra context upfront can help us get to a solution more quickly.
Whether you’re reporting a technical issue, requesting access, or asking for assistance with a system or application, these five tips can help you submit better IT tickets and improve the support experience for everyone involved.
1. Include the Full Error Message
When something goes wrong, an error message is often the most valuable piece of information available. Even when the message appears confusing or overly technical, it frequently contains clues that help technicians identify the source of the problem.
Here is a common statement made in a ticket: “The application isn’t working.”
Here is a more effective way of making that same statement: “The application displays: ‘Access denied. Unable to connect to the server.'”
The second example immediately provides useful information about what happened and allows support staff to begin investigating potential causes and opposed to reaching back out to get additional information.
Whenever possible, include the complete error message exactly as it appears. Avoid paraphrasing or summarizing the message. Even details that seem unimportant can be useful during troubleshooting.
2. Tell Us What You Were Trying to Do
Understanding the problem is important. Understanding what you were trying to accomplish is often even more important.
Here is a common statement made in a ticket: “Excel crashed and I need help getting it working again.”
Here is a more effective way of making that same statement: “Excel crashed while I was opening a shared budget spreadsheet from a network drive.”
The second example provides context that may help identify whether the issue involves a specific file, a shared location, a permissions problem, or something else entirely.
When submitting a ticket, try to describe:
- The application or website you were using
- The task you were attempting to complete
- The steps that led to the issue
- What you expected to happen
- What actually happened
Think of your ticket as telling the story of how the issue occurred. The more complete the story, the easier it is for support staff to follow the trail.
3. Include Screenshots When Possible
Sometimes a screenshot can provide more information than several paragraphs of explanation.
Screenshots allow technicians to see exactly what you are seeing, including:
- Error messages
- System notifications
- Application screens
- Browser pages
- Missing buttons, menus, or options
- Unexpected behavior
A well-timed screenshot often eliminates several rounds of follow-up questions and helps technicians begin troubleshooting immediately.
Before attaching screenshots, take a moment to review the image and ensure it does not contain sensitive information such as passwords, confidential records, or personal data.
When appropriate, screenshots can be one of the fastest ways to communicate a problem.
Inside of a service.tamu.edu ticket:

- You can add images or files as attachment.

- You can copy and paste the image directly into the description window. If you have an error message up, you can press (Win + Shift + S), drag and select the error, then come to this window, click in the box, and press (CTRL + V) to paste that image here. (The image may look small, but we can see the original size of the screenshot.)
- Along with the image, please continue to describe the issue you are having as detailed as possible. A screenshot by itself might not be enough to fully investigate your issue.
4. Provide Device and Location Information
Not every issue is caused by software. Many problems are tied to a specific computer, device, building, room, network connection, or workstation.
Providing device and location information can help identify patterns and narrow troubleshooting efforts before additional investigation even begins.
Useful details might include:
- Computer name (if known)
- Building and room number
- On-campus or remote location
- Desktop, laptop, tablet, or mobile device
- Wired or wireless network connection
Here is a common statement made in a ticket: “My computer is not working.”
Here is a more effective way of making that same statement: “I have a laptop that was issued to me and when I try to access my account from home, it will not let me log in.”
Even simple location and device details can save valuable troubleshooting time.
5. Submit One Issue Per Ticket
When several things go wrong at once, it can be tempting to include everything in a single support request.
For example: “My printer won’t print, my monitor is flickering, and I need software installed.”
While this may seem efficient, combining multiple unrelated issues into a single ticket can make tracking and resolution more difficult.
Separate tickets allow support teams to:
- Route requests to the appropriate personnel
- Track progress more effectively
- Prioritize issues independently
- Communicate updates more clearly
- Resolve problems without delaying unrelated requests
As a general rule:
One issue or request should equal one ticket.
If multiple problems are related to the same underlying issue, they can often remain together. However, unrelated issues are usually better handled through separate requests.
Better Information Leads to Faster Support
Submitting a great ticket doesn’t require technical expertise. In most cases, it simply requires a little additional information.
Before submitting your next request, take a moment to ask yourself:
- Did I include the full error message?
- Did I explain what I was trying to do?
- Did I provide a screenshot if one was available?
- Did I include device and location information?
- Am I reporting a single issue or request?
Those extra details can help DSA IT begin troubleshooting sooner, reduce the need for follow-up communication, and improve the overall support experience.
At the end of the day, the goal isn’t simply to submit a ticket. The goal is to solve the issue and get you back to work as quickly as possible. A well-written ticket is often the first step toward making that happen.