How to Submit an Effective Trouble Ticket

Cite This Article

Siron, E. (2023, January 4). How to Submit an Effective Trouble Ticket. Project Runspace, https://projectrunspace.org/how-to-submit-an-effective-trouble-ticket/

Siron. Eric. "How to Submit an Effective Trouble Ticket." Project Runspace, 4 Jan. 2023, https://projectrunspace.org/how-to-submit-an-effective-trouble-ticket/. Accessed unknown.

Siron. Eric. "How to Submit an Effective Trouble Ticket." Project Runspace. January 4, 2023. https://projectrunspace.org/how-to-submit-an-effective-trouble-ticket/.

Siron, E. (2023), 'How to Submit an Effective Trouble Ticket', Project Runspace, 4 January, https://projectrunspace.org/how-to-submit-an-effective-trouble-ticket/ (Accessed: unknown).

This site focuses on systems administrators, but everyone at every level, technical or not, needs to report problems. As the first point of contact, your trouble ticket (or e-mail, or problem report, or service ticket, or helpdesk request, or whatever your organization calls it) sets the tone for all future interactions necessary to get that problem solved. When you submit an effective trouble ticket, you increase your chances of skipping unnecessary intermediary steps and reaching resolution faster.

An example of a good trouble report:

Screenshot of an e-mail containing a report of a problem along with a screenshot of what happened.A sample trouble report

As you read through the article, you might decide that this example lacks one major piece: What did the user expect to happen? We can expect a reasonable person to look at the contents of this message and understand that the user thought that they would have access to the site. Right away, understand that you need to provide enough information for your recipient to help you without overwhelming them. Everything that follows shows you ways that you can accomplish that. If you can achieve that aim without hitting every bullet point, that’s OK.

The Ground Rules

First, a few things to do or not do to make certain that you don’t turn in an objectively poor ticket:

If everyone filing a trouble report would follow those few rules, support resolution times would decrease for everyone.

Making it Better

We set the baseline for making a ticket not awful. We can do a little more to make a ticket good (if we can ever call a trouble report that). A few pointers:

Any writing skills learned in school will help. Organization and clarity make the biggest difference. You might also need a bit of persuasiveness.

Behave Professionally

Remember that support staff are people, too. This probably seems obvious to you. It also seems obvious to me that many people forget this simple fact. We all have an ethical responsibility to act politely toward each other in any environment. For some, it doesn’t seem like that matters. So, a few supporting points:

Few things can ruin your day quite like a bad support experience. Do your part to keep the interactions civil and upbeat. You will almost always get a superior outcome this way.