Advanced IT Support • Managed IT Services • Jacksonville, FL
Can You Use ChatGPT to Fix Your Business IT? What Works, and What Makes It Worse
AI is a very good tutor and a risky technician. Here is how to tell which job you are giving it.
Let us be clear up front: we are not against AI. We use it ourselves, and it can be a great way to understand how your technology works. The point of this post is narrower. There is a big difference between asking AI to explain something and following its instructions on a live system that your business depends on.
Why Business Owners Are Doing This
It makes sense. A chatbot is instant, free, available at 9 pm on a Sunday, and writes in confident, detailed, step-by-step instructions. A call to an IT provider costs money and takes time. If something is slow, broken, or confusing, trying the AI first feels like a smart, low-risk move.
It also lowers the barrier for the person in the office who ended up holding IT together without being hired for it. That person can now attempt fixes that would have been out of reach a few years ago. Sometimes that is a win. The risk is that being able to attempt a change is not the same as being able to judge whether it is safe.
A Real Example: The Broken SharePoint Sync
A customer of ours ran into a problem with SharePoint file sync. He asked an AI chatbot for help and followed the troubleshooting steps it gave him.
Some of those steps are things IT people really do when sync misbehaves. But they were written without knowing how his folders were set up, what was already synced, or which files existed only on his computer. When he was done, the sync was broken worse than when he started, and our team had to step in and untangle it.
Fixing it took more work than the original problem would have. Before anyone could repair the sync, someone had to work out what had changed, what state everything was in, and which copies of files could be trusted.
That pattern is the real lesson. The original problem was small. The damage came from confident-sounding changes made without a full picture.
Sync tools make a local folder and a cloud library mirror each other. That is convenient, but it also means that deleting, moving, or resetting things locally can change what is stored in the cloud, and a troubleshooting step that is harmless in one situation can be destructive in another. Deleted items usually land in a recycle bin for a limited time, but relying on that is not a plan.
Where AI-Guided Fixes Tend to Go Wrong
The sync example is one of several patterns we see. The common thread is a change that affects something the whole business depends on, made without knowing what depends on it.
- Email routing and DNS records. A wrong edit to your domain's mail or DNS settings can stop email from arriving, sometimes without any visible error.
- Microsoft 365 admin, security, and sign-in settings. Changing access rules, MFA, or admin roles can lock your own team out, including you.
- Scripts and registry edits. Copying a PowerShell command or registry change you do not understand can change far more than the one thing you intended.
- Turning off security tools to test. Disabling antivirus, the firewall, or email filtering "just to see if that is the problem" often gets forgotten and left off.
- Resetting, reinstalling, or wiping. A reset can remove data that was never backed up, and a chatbot cannot tell you whether it was.
- Backup and sync settings. As the example above shows, changing how data is synced or stored can leave you unsure which copy is current.
- Firewall and router settings. A wrong rule can cut off remote access or open a door that should stay closed.
Why this happens
AI cannot see your environment. It answers the question you typed, not the network you have. It does not know what else is connected, what was configured years ago for a reason, or what a change will affect.
It sounds equally sure whether it is right or wrong. A chatbot can give an incorrect answer in the same calm, authoritative tone as a correct one. For an unfamiliar topic, it is very hard to tell the difference.
Instructions often do not match your version. Menu names, settings, and options change between product versions and licenses. Steps written for one version can do something different, or nothing, on yours.
Fixes stack up. When the first step does not work, the natural move is to ask what to try next. After four or five attempts, nobody, including the chatbot, knows what the current state is.
What you paste may leave your control. Error logs, screenshots, and configuration details often contain usernames, server names, or credentials. Unless your company uses an AI service under a business agreement that covers data handling, treat anything you paste as leaving your control.
Where AI Genuinely Helps
None of this means you should not use it. Used for understanding rather than for making changes, AI is a real asset.
- Explaining what an error message means in plain language.
- Learning what a term or tool is, such as DNS, MFA, a VPN, or conditional access.
- Writing a clear description of a problem to send to your IT provider.
- Drafting documentation, checklists, and internal procedures for your team.
- Preparing a list of questions before a call with your IT provider or a vendor.
- Comparing options in general terms before you make a purchase decision.
Many of these actually make your IT provider's job easier. A customer who shows up with a clear description of what is happening and what they have already tried is a pleasure to work with.
Ground Rules for Using AI Around Your IT
If you or someone on your team is going to try AI-guided troubleshooting, these rules will prevent most of the damage.
- Do not run anything you do not understand. If you cannot explain what a command or setting does, ask the chatbot to explain it first, and verify the explanation against the software vendor's own documentation.
- Make one change at a time, and write each one down. If something breaks, you need to know exactly what changed and in what order.
- Only make changes you can undo. If a step cannot be reversed, or you are not sure it can, stop.
- Confirm you have a working backup first. Not that backups exist, but that you know how to restore from them.
- Stay out of DNS, email routing, admin roles, security settings, firewalls, and backups. These affect the whole company, and mistakes are the hardest to spot.
- Never paste passwords, keys, or client data into a chatbot. Remove usernames and server names from logs and screenshots where you can.
- Stop when something gets worse. If a change makes things worse, do not ask for another fix. Stop, note the current state, and call for help.
That last rule matters most. The expensive cleanups almost always involve a chain of attempts rather than a single mistake. Calling for help after the first thing breaks is far cheaper than calling after the fifth.
What It Costs When an AI Fix Goes Wrong
Fixing a problem that has been made worse costs more than fixing the original problem, for a simple reason. Before anyone can fix it, someone has to work out what changed, in what order, and what the system looked like before. That investigation takes time that the original problem never needed.
There is also the cost nobody sees: the hours a team spends unable to work, files that cannot be trusted, and the stress of not knowing what state things are in. For a small business, that cost lands on the same few people who are trying to do their actual jobs.
This is also why a good IT provider is not mainly a repair service. A big part of the value is judgment: knowing what a change will touch before making it, and having the backups and documentation that let you undo it. That is exactly the part a chatbot cannot supply.
Use AI to Get Smarter, and Let Someone Own the Risk
The best way to think about it is as a division of labor. AI is excellent for learning, preparing, and explaining. For changes that affect your email, your files, your security, or your backups, you want a person who knows your environment, has a way to undo mistakes, and is accountable if something goes wrong.
If you are not sure whether a problem is safe to tackle yourself, that uncertainty is your answer. A short call before you change anything costs very little, and it is a lot cheaper than the cleanup afterward.
Not Sure Whether to Fix It Yourself?
If something is not working and you are not certain a change is safe, call us before you try it. We will tell you straight whether it is a quick fix you can handle or something worth leaving alone. No pressure, no sales pitch.
Serving Jacksonville, St. Augustine, Green Cove Springs, and surrounding Northeast Florida.
One Response