What To Include In A Support Request So It Gets Fixed Faster
The difference between a ticket resolved in ten minutes and one that takes two days is almost always the first message. Here is what an engineer needs from you.
In short: the most useful thing in a support request is what changed today, not just what broke. Include the exact error word for word, who is affected and how many, when it started and whether it is constant, and how to reach you. That is the difference between a ten minute fix and a two day one.
What To Include In A Support Request: Say What Changed, Not Just What Broke
The single most useful sentence in any support request is a description of what is different today. Software rarely breaks on its own. Something changed: an update installed overnight, a cable was moved during cleaning, a password was reset, a new person started, a laptop went home for the weekend and came back.
Compare these two tickets. “Outlook is broken” gives an engineer nothing, and the first reply will be a question, which costs you an hour. “Outlook stopped receiving mail this morning after Windows restarted overnight, it still sends fine, and it works on my phone” gives an engineer almost the whole answer before they have touched anything.
You do not need to diagnose it. You just need to describe the shape of it.
Name The Exact Error, Word For Word
Screenshots are better than descriptions, and the full error message is better than a summary of it. “It says something about a certificate” and “Your connection is not private, NET::ERR_CERT_DATE_INVALID” send an engineer down completely different paths.
On Windows, the Snipping Tool captures a region in two keystrokes. On a Mac, Command Shift 4. Paste it straight into the ticket. If the error appears and vanishes, a phone photo of the screen is perfectly acceptable and far better than nothing.
Say Who Is Affected And How Many
Scope changes priority, and it changes the diagnosis. One person cannot print is a workstation problem. The whole floor cannot print is a print server or a network problem. One person cannot reach a website is usually their machine. Everyone cannot reach it is usually the site.
Tell us whether it is just you, your team, or the building. If you are not sure, say so, and say who else you have asked.
Say When It Started, And Whether It Is Constant
Intermittent faults and constant faults are different problems with different causes. “It happens about twice a day, usually in the afternoon” is a genuinely useful clue that points at load, or a scheduled task, or a device that is overheating. “It has not worked since Tuesday” points somewhere else entirely.
If it started at a specific moment, say what you were doing at that moment, even if it seems unrelated.
Tell Us How To Reach You And How Urgent It Is
Give us the best number and the times you are actually at your desk. Nothing wastes a morning like an engineer calling while you are in a meeting, then you calling back while they are on another job.
Be honest about urgency. If you can work around it until this afternoon, saying so genuinely helps us put the person who cannot work at all first. If you are dead in the water, say that plainly and we will treat it that way.
What Not To Bother With
You do not need to restart before logging the ticket, though it does no harm. You do not need to run any diagnostic tools. You do not need to work out whose fault it is. And you never need to apologize for logging a ticket, including the ones that turn out to be a cable.
If something is actively spreading, a suspicious email that several people received, files renaming themselves, or a machine behaving strangely after someone clicked a link, do not log a normal ticket. Call 678-374-4352 and choose option 1, the security line answered 24/7, then tell the engineer it is a security issue.
Support Request Questions We Get Asked
What people ask the first time they log a support ticket with us.
A standard request gets a response within four business hours and a critical issue within one business hour, during help desk hours of 8 AM to 5 PM Eastern, Monday to Friday. That is written into the agreement rather than implied. Security emergencies on option 1 of 678-374-4352 get a response within 30 minutes, around the clock.
Submit a ticket for anything that is not stopping you working right now, because it gets logged, tracked and picked up in order. Call when you cannot work, or when something looks like a security problem.
You can, but a ticket is better. Direct email depends on that one person being available. A ticket is visible to the whole team, so it gets picked up even if the engineer you know is on another job or on leave.
Send a screenshot and say what you were trying to do. That is enough. Working out what is actually wrong is our job, not yours.
What A Good Support Ticket Looks Like
Here is a support request that usually gets fixed on the first reply: “Since about 9am the second floor printer shows Paper Jam in Tray 2, but there is no paper in the tray. Everyone on the floor is affected. I am at my desk until noon, and we can print downstairs until then.”
That one support ticket covers everything on this page: what changed, the exact words on screen, who is affected, when it started, how to reach the person and how urgent it really is. It took under a minute to write.
If you only remember what to include in a support request in one line, make it this: say what you see, who it affects and how to reach you.
Support Request Mistakes That Slow The Fix Down
Putting several problems in one support ticket. Two unrelated faults in one message usually means the second waits until the first is closed. Open one support request per problem, even if they started at the same time.
Replying to an old ticket about a new problem. The history in it describes a different fault and sends the engineer down the wrong path. Start a fresh support request instead.
Describing the fix you want rather than the fault you have. “Please reinstall Excel” may not be what is wrong. Say what happens, and let the engineer decide what to do about it.
Leaving out the workaround. If you have found a way to keep working, put it in the support ticket. It tells us how urgent the fix really is, and it often points straight at the cause.
When To Call Instead Of Writing A Support Ticket
A written support request suits most faults. Pick up the phone instead when nobody in the office can work, when a client is waiting on the outcome, or when anything about the problem feels like a security issue.
Files renaming themselves, a message demanding payment to unlock data, or an account sending emails nobody wrote are not tickets. Call 678-374-4352, press option 1 for the 24/7 security line, and say it may be a security issue.
When you do call, the same details still help. Have the exact error, who is affected and when it started in front of you before you dial, and the call will be shorter.
Not Sure What To Include In A Support Request?
Send what you have and we will ask for the rest. A short support ticket today beats a perfect one tomorrow. If it cannot wait, call 678-374-4352.
If you are documenting an incident rather than a fault, CISA has guidance on reporting security problems as well.