Everyday office basics
How to ask IT for help so it actually gets fixed
Tickets rarely vanish because your question was too basic. They vanish because five specific things are missing. Here is what to put in, what to leave out, and how to nudge politely when something stalls.
Say what you were trying to do, what happened instead, the exact error, when it started, and what you already tried. Never put a password in a ticket.
Last reviewed 2026-08-18 by Grayson Dodson. Free, plain-English guidance for everyday work technology.
What you'll be able to do
write a support ticket that carries the five things a helpdesk actually needs, capture the exact error message on Windows or a Mac, say how urgent it really is without inflating it, and follow up politely when something stalls
the five things every workablecapturing the exact error textscreenshot shortcuts: windows key +describing impact in facts andwhy inflating urgency costs youkeeping passwords out of tickets,cropping screenshots that contain otherticket numbers, status fields, and
Your question is not too basic. Really.
Start here, because it is the thing that stops most people from asking at all: there is no such thing as a question too basic for a helpdesk. The people on the other end of that ticket spend their whole day on password resets, printers that will not print, and Teams meetings with no sound. A clear report about a small thing is the easiest part of their day. What they genuinely dread is the mystery: a message three weeks later saying nothing has worked properly for a while, with no dates, no error text, and half a memory of what happened. By then the logs may have rolled over and the evidence is gone. Early and specific is a gift to them, not an imposition. It also helps you. A ticket is a record with a timestamp, so when a problem turns out to be bigger than it looked, there is proof that you flagged it on the day rather than sat on it. And no one is born knowing what a VPN client is, or which of the four printers on the floor is the one by the kitchen.
The five things that turn a vague ticket into a fixed one
Wherever your workplace keeps its front door, a portal such as ServiceNow, Jira Service Management, Freshservice or Zendesk, an address like helpdesk@ your company domain, or an IT channel in Slack or Teams, the same five pieces turn a vague ticket into a fixed one. One: what you were trying to do. Two: what happened instead. Three: the exact error message, word for word, including any code. Four: when it started, and whether it happens every time or now and then. Five: what you have already tried. The third one is where most tickets fall down, because 'it gave an error' tells nobody anything, while 'Something went wrong (Error code: 30016-4)' can be searched. Do not retype it from memory. On Windows, press Windows key + Shift + S, drag a box around the message, then paste it into the ticket with Ctrl + V. On a Mac, press Shift + Command + 4 and drag; the picture lands on your desktop ready to attach. On many classic Windows dialog boxes you can also click the box and press Ctrl + C, which copies the whole text so it stays searchable.
The same problem, written badly and then written well
Here is the same problem written twice. First: 'Outlook is broken again, please help. Thanks.' That one cannot be worked on, or even routed, so it sits until someone writes back asking what you could have said first time. Second: 'I am trying to send an email with a 12 MB PDF attached, from Outlook on my Windows laptop, device name FIN-LT-0442. When I click Send the message drops into Outbox and about a minute later I get: Task Microsoft Exchange reported error (0x80040610). The message being sent exceeds the message size established for this user. It started this morning around 9:15 and happens every time I attach anything over roughly 10 MB. Smaller attachments send fine. I restarted Outlook and signed out and back in. Screenshot attached.' Same person, same problem, about forty seconds more effort. Your device name is under Settings > System > About on Windows 11, or the Apple menu > System Settings > General > About on a Mac. Give the ticket a title in the same spirit, such as 'Outlook: attachments over 10 MB fail, error 0x80040610', and it can be picked up, diagnosed and answered without a single follow-up question.
Saying how urgent it really is, without inflating it
Most ticket forms have a priority box: Low, Medium, High, Urgent, or P1 to P4 in ServiceNow and Jira Service Management. The honest way to fill it in is to stop guessing at a label and describe the impact in facts, then let them set the priority. Facts are things like how many people are affected, whether there is a workaround, and whether a real deadline is attached. 'This is only me, I can use the web version meanwhile, no rush' is genuinely useful. So is 'This blocks the payroll run that has to be submitted by 4pm today, and four of us cannot get in.' Both are believable, and the second gets moved without you having to shout. Marking everything Urgent feels like the safe play, but it works exactly once. Queues are visible, and a person who files five P1s a month for things that were not P1 quietly becomes the person whose next P1 gets read as probably not. Real emergencies deserve a phone call or the on-call number as well as a ticket: a lost or stolen laptop, a suspected security incident, a whole team locked out, anything where money is moving.
Two things that never belong in a ticket
Two safety points matter more in tickets than almost anywhere else. First, never put a password in a ticket, a chat message or an email, even if the form seems to invite it. Genuine IT staff never need your password; they can reset it. If someone asks for one, look them up in the staff directory and call back. If you have already typed a password into a ticket, change that password and say so in the ticket rather than quietly deleting the comment; deleting first hides the very thing your security team needs to see, and telling them takes ten seconds. Second, watch what your screenshots contain. A full-screen grab of an error often also shows an open inbox, a customer record, a colleague's salary line or a patient name. Capture only what is needed: on Windows, Windows key + Shift + S and drag a box around the error, or Alt + Print Screen for just the active window. On a Mac, Shift + Command + 4 then press the Space bar to grab one window. If something private slipped in, crop it out in the Snipping Tool or Preview before attaching. Tickets are read by more people than you think.
Following up when it goes quiet
When you submit, you get a ticket number such as INC0042318 or HELP-1421. Keep it. Reply on that same thread rather than opening a second ticket, because duplicates split the history and usually land at the back of the queue. Then check the status, because the single most common reason a ticket stalls is that it is sitting in Pending or Waiting on customer: someone asked you a question, the reply went to a folder you do not watch, and in many systems the ticket closes itself after a few days of silence. Search your mail for the ticket number, including the junk folder. If it really has gone quiet, wait one business day for an everyday problem, then send a short, factual nudge on the ticket: 'Following up on INC0042318 from Tuesday. Still happening, still blocking the Friday payroll run. Anything you need from me?' That reads as helpful, not pushy. If two nudges get nothing, it is completely normal to ask your manager to escalate, which usually means the queue owner reprioritizes it, not that anyone is in trouble. And when it is fixed, say so in one line.
Common questions
What should I include in an IT support ticket?
Five things: what you were trying to do, what happened instead, the exact error message word for word, when it started and whether it is constant or intermittent, and what you already tried. Add your device name, from Settings > System > About on Windows 11 or the Apple menu > System Settings > General > About on a Mac, and the app you were in. Attach a screenshot of the error. Leave passwords out entirely. That is usually enough for a helpdesk to diagnose the problem without a single round of follow-up questions.
How do I take a screenshot of an error message to send to IT?
On Windows, press Windows key + Shift + S, drag a box around the error, and paste it straight into the ticket with Ctrl + V. For just the active window, use Alt + Print Screen. On a Mac, press Shift + Command + 4 and drag, or press Shift + Command + 4 then the Space bar to capture a single window; the image lands on your desktop. On many classic Windows dialog boxes you can also click the box and press Ctrl + C, which copies the error text so it can be searched. Crop out anything private before you attach it.
Is my question too basic to ask the IT helpdesk?
No. Helpdesk staff spend their days on password resets, printers and missing sound in Teams, and a clear report of a small thing is the easiest part of their day. What they dread is a mystery reported weeks late, when the logs have already rolled over. Asking early protects you too, because a ticket is a timestamped record showing you flagged it on the day. If it helps, say plainly that you are not sure what the right words are, and describe what you saw. Nobody is born knowing this.
How do I follow up on an IT ticket without being annoying?
Reply on the existing ticket rather than opening a new one, and keep the ticket number in the subject. For an everyday problem, give it one business day, then send a short factual note: what is still happening, what it is blocking, and whether they need anything from you. Check the status first, because most stalled tickets are sitting in Pending or Waiting on customer, meaning someone already asked you a question. Search your mail, including junk, for the ticket number. After two nudges with no answer, asking your manager to escalate is normal.
Should I mark my IT ticket as urgent?
Only if it genuinely is. Instead of guessing at a label, describe the impact in facts: how many people are affected, whether there is a workaround, and whether a real deadline is attached, such as a payroll run at 4pm. Let the helpdesk set the priority from that. Marking everything Urgent works once; queues are visible, and someone who files repeated false emergencies gets read as unreliable when a real one arrives. Genuine emergencies, like a lost laptop or a suspected security incident, deserve a phone call as well as a ticket.