Somewhere in your office right now, someone is typing a ticket that says “the internet is broken.” We know exactly why. They are frustrated, they are behind, and describing the problem in detail feels like it takes longer than the problem deserves. That instinct is reasonable. It is also one of the most expensive habits in small business IT, and it costs your team more than it costs ours.
This is not a complaint about your staff. Your people were hired to do accounting, sales, dispatch, or design. Writing a clear technical report is not their job, and almost nobody has ever been trained to do it. So we want to do that training here, in about five minutes of reading, and we want to be honest that the obligation runs both directions. If your team gives us better information, we owe you faster fixes and better communication.
Why “The Internet Is Broken” Costs Everybody an Hour
That one sentence can mean a dozen different things. The Wi-Fi dropped on one laptop. The whole building lost service from the internet provider. One website is down while everything else works. A password expired and the sign-in screen is refusing to cooperate. A cloud service is having a bad day, which happens more often than people expect and is worth planning for ahead of time. Each has a different fix, and some are not fixable by us at all.
So we ask a question. The person is in a meeting and answers ninety minutes later. We ask a follow up. They have gone to lunch. By the time we know enough to act, half a day is gone on a four minute fix. Nobody did anything wrong. The information arrived in slow motion.
There is a second cost that is less obvious. Vague tickets break prioritization. If we cannot tell whether one person is inconvenienced or the whole front office has stopped, somebody genuinely stuck ends up waiting behind somebody mildly annoyed. Detail is not bureaucracy. It is how urgent work gets to the front.
What a Genuinely Useful Report Contains
You do not need technical vocabulary. Describe what happened the way you would describe it to a coworker. Six pieces of information do almost all the work.
- What you were doing. “I was attaching a PDF to an email in Outlook.” Not “I was working.” The specific app and action narrow the search enormously.
- What you expected to happen. This sounds obvious, and it is the line that most often reveals a settings issue rather than a broken system.
- What actually happened instead. Did it freeze, close, show a message, or quietly do nothing? “Nothing happened” is real information, so say it.
- The exact error text. This is the big one. “It gave me an error” tells us nothing. The literal wording, including any code number, often takes us straight to the answer.
- When it started, and what changed. This morning? After a restart? After you moved desks or joined a different network? Timing is the closest thing troubleshooting has to a shortcut.
- Whether anyone else has it. Ask the person next to you first. One person with a problem and five people with the same problem are entirely different investigations.
Put together, a great ticket reads like this: “Since about 9:15 this morning, when I open the shared pricing spreadsheet in the finance folder, I get a message that the file is locked for editing by another user. Sarah gets the same message, Mike does not. Screenshot attached.” Forty seconds to write, three hours of back and forth avoided.
Why a Full Screenshot Beats a Cropped One
People are polite about screenshots. They crop down to just the error box so we are not bothered by the rest. We appreciate the thought, and we would rather have the whole screen. The parts you cropped out are often where the answer is hiding: which account is signed in, which window was in focus, whether the network icon shows a connection, what the clock says, whether a second copy of the program is open behind the first.
On Windows, Microsoft Support documents that the Windows logo key plus Shift plus S opens the Snipping Tool overlay, with modes for a rectangle, a single window, the full screen, or a freeform shape, and that captures save to your Screenshots folder. Microsoft Support also documents Windows logo key plus Shift plus R to capture a video clip, which is the fastest way to show a problem that only appears when you click things in a certain order.
On a Mac, Apple Support documents Shift plus Command plus 3 to capture the entire screen and Shift plus Command plus 5 for more capture options, with screenshots saving to the desktop by default. Shift plus Command plus 3 is the one to remember.
If the machine is too stuck to take a screenshot at all, a phone photo is genuinely useful. Get the whole screen in frame and hold still enough for the text to be readable.
When to Call, When to Email, and How Urgent Is Actually Urgent
Written tickets are better for most things. They create a record, they carry screenshots, and they do not depend on anyone being at their desk. But some situations deserve a phone call, and we would rather you called too often than not enough.
- Call when work has stopped for a group. A department offline, phones down, or the system that takes customer payments failing.
- Call when you suspect a security problem. You clicked something you should not have, an unexpected approval prompt appeared on your phone, or files suddenly will not open. CISA’s Cyber Guidance for Small Businesses recommends a written incident response plan with defined roles, and a fast phone call is what starts that plan.
- Call when you cannot reach the ticket system. If email is the broken thing, do not email us about it.
- Write a ticket for everything else. One person, one machine, one annoyance, plus requests, new hires, and questions.
Then there is urgency, where good intentions go sideways. When every ticket is marked urgent, the label stops carrying information and the queue reverts to first come, first served. That hurts people with real emergencies. The honest test is three questions: is anyone unable to work right now, is there a hard deadline today, and is there a workaround.
The Promise That Goes the Other Way
None of this is fair unless we hold up our end. We will confirm we received your ticket rather than leaving you wondering. We will tell you who owns it. We will give you a next update time, and we will keep it even when the update is “still working, nothing new yet,” because silence is what makes people call twice and open duplicate tickets.
We will tell you when we are stuck, when the problem sits with a vendor we do not control, and how long that usually takes. When it is done, we will explain what happened in plain language, not acronyms. And nobody on our team will ever make one of your people feel foolish for asking. The time your team gets back is the real product, and it depends on both sides communicating well.
The Bottom Line
Good ticket hygiene is not paperwork and it is not a test. It is six sentences and a screenshot that turn a half day of guessing into a fast fix. Share this with your team, keep the six questions somewhere visible, and give people permission to send an imperfect ticket rather than no ticket. Half the detail beats a shrug.
If your support process feels like a black hole where requests go in and updates never come out, that is worth fixing, and it usually is not your team’s fault. We are happy to review how tickets flow in your business and give your staff a one page reference they will actually use. Contact us today.
Sources:
Comments are closed