Your Junior Techs Are Already Using AI. That's Why Your Senior Techs Are Drowning.

Last week the most upvoted post on r/msp wasn't about a vendor outage or a pricing change. It was a tech asking if it's just their MSP, or if everything is going downhill.

Seven years at the same shop. The company won't hire anyone with experience. The new techs "just ask ChatGPT about any issues and blindly trust it." The experienced people are absorbing three people's workloads. The one week of vacation they took was filled with emergency calls and followed by two weeks of cleaning up everyone else's mess.

The replies were full of people who recognized every line of it.

We want to talk about one specific part of that story, because it's the part that's getting worse industry-wide: the AI part.

It's not the AI. It's the browser tab.

Nobody in that thread is really complaining that AI exists. The problem is how it's being used. A junior tech with a ticket and a ChatGPT tab has three things working against them:

No context. The model has never seen this client's tenant. It doesn't know their conditional access policies, their licensing, what's documented about their setup, or that this exact issue came up last month and was fixed a specific way. So it gives a generic answer i.e. confidently.

No accountability. Whatever the tech does next happens in a portal, by hand, with no record of why. When it goes wrong, there's no trail back to "the AI said to do this." There's just a broken thing and a senior tech trying to work out what changed.

No process. Your MSP has a right way to handle a mailbox access request, an offboarding, a license change. It lives in a senior tech's head, or a doc nobody reads. The chatbot doesn't know it exists, so every junior improvises their own version.

Put those three together and AI doesn't reduce the load on your experienced people. It moves the load onto them as cleanup, after the fact, usually on their day off.

The senior tech becomes the undo button

Here's the uncomfortable math. A junior using AI in a tab might close a ticket faster. But if one in ten of those closures needs a senior tech to unpick it later, you haven't saved time. You've taken predictable, scheduled work and turned it into unpredictable, urgent work for the one person you can least afford to interrupt.

That's the pattern in the thread. Not "the juniors are bad." The juniors are doing exactly what the tooling lets them do. The system just has no place for the senior tech's judgment except after something breaks.

What it looks like when AI works inside your stack instead

The alternative isn't banning AI. Your techs will use it anyway and the thread proves that. The alternative is AI that works where the work actually is, with the guardrails your senior techs would insist on.

That's what we built Uniportal to be. Three differences matter:

It reads the real environment. Instead of guessing, Uniportal pulls live context from the client's tenant and your stack, the ticket in HaloPSA, ConnectWise, or Autotask; the user, groups, and licenses in Entra ID or Google Workspace; the devices in NinjaOne or Datto RMM; what's documented in IT Glue or Hudu. The answer is about this client, not a generic one.

It proposes, a human approves. Anything that changes a client environment is laid out as a plan first. Every action, which system it touches, what it will change. Nothing executes until a technician approves it. That gate is enforced by the platform, not a suggestion in a prompt.

It leaves a trail. Every action that runs is logged. When a senior tech needs to know what happened to an account on Tuesday, they read one audit trail, they don't reconstruct it from four vendor portals and a junior's memory.

Turn your senior tech's judgment into the default

The biggest lever, though, is process. In Uniportal, your processes live as Skills, workflows written in plain English, the way a senior tech would explain them to a new hire.

Take a request every service desk sees weekly: "Give Sarah access to the finance shared mailbox." Your senior tech's version of that probably looks something like:

When someone requests access to a shared mailbox:Confirm the requester is authorized to approve access for that mailboxCheck what access the user already hasGrant Full Access — and Send As only if it was explicitly requestedAdd a note to the ticket with exactly what was grantedIf the mailbox isn't documented, flag it for the docs

A junior with a chatbot skips steps 1, 2, and 5 not out of carelessness, but because nobody told them those steps exist. A junior running the Skill gets them every time. The AI plans the run from the Skill, the junior reviews the plan, and the senior tech's judgment is baked in before anything happens instead of applied as damage control afterward.

That's the shift. Your most experienced tech stops being the undo button and becomes the author of the playbook everyone else runs.

What this won't fix

We'd be doing the same thing that thread is complaining about if we pretended software fixes everything in it.

A lot of the replies weren't about AI at all. They were about private equity buyouts, merged companies missing their numbers, and an unwritten expectation of being reachable at all hours. If your MSP won't hire experienced people and expects your best tech to answer calls on vacation, no tool changes that. That's a leadership problem, and it deserves a leadership answer.

What the right tooling can do is stop AI from making it worse and give the people carrying the load a way to put their knowledge somewhere other than their own heads.

Start with the ticket your senior tech keeps getting pulled into

You don't need an AI strategy. You need to know which request your most experienced person keeps getting dragged back into.

Ask them. They'll know instantly. Have them describe how it should be done, in plain English, the way they'd explain it to a new hire. That's your first Skill. Let the next junior who gets that ticket run it with a plan to review, an approval before anything changes, and a record of what happened.

Then ask them for the next one.

Uniportal gives MSPs an AI teammate that works across Microsoft 365, Google Workspace, your PSA, your RMM, and your documentation with your technician approving every change. Learn more.