How To Report An IT Outage So It Gets Fixed First
What an outage is, how to say so clearly, and why the first sentence you use decides how fast it moves.
In short: an IT outage means a shared service is down for more than one person. Confirm it is an IT outage by asking a colleague, then call 678-374-4352 with what is down, how many people, when it started and what changed.
Not every fault is an outage, and the difference matters more than most people realize. A slow laptop is a fault. A shared drive nobody can reach is an outage. When you report an IT outage, you are telling the help desk that work has stopped, and that changes where your ticket sits in the queue.
This guide covers what counts, how to describe it in one sentence, and what happens on our side the moment it lands.
What Actually Counts As An Outage
The test is simple: can people still do their job? If a system that more than one person needs is unavailable, that is an outage. A single printer misbehaving is not, even though it is annoying. The distinction changes the response: for an outage we drop other work and look at the shared infrastructure, and for a single device we book time with you.
Examples that count: nobody can reach the shared drive, email is not sending for the whole office, the phone system is silent, the line-of-business application will not load for anyone, the internet is down at a site.
Examples that do not: one person cannot print, one laptop is slow, one mailbox is full. Those are ordinary tickets and they are answered within four business hours, but they do not jump the queue.
If you are not sure which you have, report it as an outage and say you are not sure. Being wrong costs nothing and being slow costs a morning.
How To Describe It In One Sentence
The most useful thing you can tell us is what changed and who it affects. “Nobody in the Marietta office can open the shared drive since about 8:40” is a better report than three paragraphs.
Include the number of people affected, when it started, and whether anything happened just before it. A power cut, a storm, a software update, somebody moving a cable: all of that shortens the search.
Say what you have already tried. If three people have rebooted and it is still down, that rules out a whole category of causes before an engineer picks it up.
Do not troubleshoot in the message. Describe the symptom, not your theory. Theories are welcome on the call but they can send a fix down the wrong path if they arrive first.
Who To Tell, And How
Call. Do not email an outage. Email is a queue, and a queue is the wrong tool for something that has already stopped work. Ring 678-374-4352 and say the word outage in the first sentence.
Outside office hours, use the same number and follow the prompt for the security and emergency line. It is monitored around the clock.
Tell one person on your side to own the conversation. When five people report the same outage from five directions, the engineer spends the first ten minutes working out that it is one problem, not five.
Then tell your own team what is happening. Half the cost of an outage is people repeatedly trying something that is not going to work.
What Happens Once You Report An IT Outage
It gets triaged straight away. Somebody confirms the scope, checks monitoring for what it already knows, and checks the shared pieces from widest impact down: the connection, then the server or cloud platform, then the application. Most outages turn out to be one of the first two.
You get told what we know, in plain language, and roughly when we will update you again. An honest “we do not know yet, next update in twenty minutes” is more useful than silence.
When it is fixed, you get told what happened and what stops it happening again. If the answer is that nothing stops it happening again, you get told that too. If the cause sits with a carrier or cloud provider, we say so plainly and pass on what they have told us.
Afterwards it goes in the notes, so the next person who sees the same symptom starts from the answer instead of the beginning.
A Quick Self-Check Before The Next Outage
Picture the front desk at 8:15 on a Monday with no dial tone and no internet. Whoever notices first needs to know which phone to use, which number to dial, and who tells waiting clients about the delay.
If nobody in your office could answer those three questions today, write the answers down now. An IT outage is the worst moment to learn that the support number only lived in an email signature.
Outage Reporting Mistakes That Slow The Fix
Assuming a colleague has already called it in. Everyone sees the same frozen screen and everyone waits for someone else, so an IT outage can sit unreported for an hour. If you are unsure, ask out loud.
Restarting the router, firewall or server over and over. Each restart can wipe clues an engineer needs and make a short drop look like failed hardware. Leave shared equipment alone unless we ask you to touch it.
Declaring it over the moment one screen comes back. Services often return one at a time, so email may work while the shared drive or the phones are still dead. Check the few things your team relies on before telling everyone the IT outage has ended.
Moving work onto personal email or personal cloud storage to get around the problem. Client files end up in places nobody can track or recover later.
Signs An Outage Could Be Something Worse
Systems going dark while files get strange names or a message demands payment may point to an attack rather than a fault. Call security at 678-374-4352, option 1; the line is always open.
A hot server cupboard, a burning smell, or equipment beeping after a power cut also needs an immediate call. Do not power things on and off to test them.
Ring again if a fixed IT outage returns, even for a few minutes. Note the exact time of each drop, since a repeating pattern often reveals what the first repair missed.
The Thirty Second Check That Saves Everyone Time
Before you report an IT outage, do one thing. Ask the nearest colleague to try exactly what you just tried.
If it fails for them too, you have an outage and you should say so in the first sentence. If it works for them, you have a local problem, and knowing that changes what we look at first.
Two extras are worth doing if they take no time. Try the same thing from your phone on mobile data rather than the office network, which separates an internet problem from a service problem. And note whether anything else stopped at the same moment, because simultaneous failures usually share one cause.
Thirty seconds of checking removes the single biggest delay in outage handling, which is not knowing the scope.
Keeping The Business Moving While It Is Fixed
Not every IT outage has a workaround, but many do, and thinking about it in advance is worth more than improvising on the day.
If the internet is down, mobile data on phones usually still works for email and for the 3CX app, so calls and messages can continue. If a server is unavailable, cloud based files may not be. If phones are down, a diverted number can keep sales calls answered.
The time to decide which of those matters is not during the outage, and the industry notes further down show what usually tops the list.
Related Guides And What To Have Ready
If you are not sure whether something is urgent, read when to call out of hours. If it turns out to be a security problem rather than an IT outage, go straight to reporting a security incident. More in Getting help.
Have four things ready when you report an IT outage: what is down in plain words, how many people it affects, the time it started, and anything that changed just before.
Call 678-374-4352. For anything affecting the whole office, call rather than email, every time.
For general guidance on preparing a business for disruption, the federal resources at CISA are a reasonable starting point.
An IT Outage Checklist You Can Print And Pin Up
Print this and put it somewhere visible. When an IT outage happens, nobody wants to be reading a web page to find out what to do, and the page may be on the thing that is down.
- Confirm it is an IT outage by asking one colleague to try the same thing.
- Check whether it fails on mobile data as well as the office network.
- Agree who is reporting the IT outage so we do not get ten tickets for one fault.
- Call 678-374-4352 rather than emailing. An IT outage needs a phone call.
- Say what is down, how many people, when it started, and what changed just before.
- Note the exact time the IT outage began. It is the most useful single fact you can give.
- Tell colleagues internally so they stop raising duplicate tickets.
- Switch to the agreed fallback if you have one, mobile data or a diverted number.
- Keep working on anything unaffected rather than waiting for the all clear.
- Reply to the existing ticket with anything new rather than opening another.
Ten lines. Most of the delay in resolving an IT outage comes from the first three of them being skipped.
What An IT Outage Costs In Your Industry
The impact of an IT outage is not the same everywhere, and knowing your own version of it is what makes a fallback plan worth building.
Law firms. A morning offline is a morning of missed client calls and a filing deadline that does not move. For a firm, email and phones are the two things that cannot stop, and an IT outage that takes both is the one to plan for specifically.
Distribution and logistics. An IT outage that stops order entry stops shipping, and shipping does not catch up. A day of orders taken on paper is a week of reconciliation afterwards, so the fallback needs to be agreed before it is needed rather than improvised at the counter.
Manufacturing. On a plant floor an IT outage can idle people rather than just inconvenience them, and the cost per hour is measurable in a way office downtime is not. Anything touching production scheduling belongs at the top of the recovery order.
Tell us which two or three functions genuinely cannot stop for your business and we will make sure a fallback exists and somebody knows how to use it. Call 678-374-4352.
Questions About How To Report An IT Outage
Call. 678-374-4352. Email is fine for ordinary faults but an outage should reach a person, not a queue.
Nothing bad happens. It becomes a normal ticket with a four-business-hour response. Reporting it costs you nothing.
One person. Nominate somebody to own the conversation so the engineer is not reconciling five reports of the same fault.
Same number, follow the prompt for the emergency line. It is monitored around the clock.