Blog

How do I stop my techs switching between the PSA and the RMM?

5 min read

By Arunava Nag, Co-Founder of Toolqit

Watch a tech work one ticket and count the tabs. The ticket is in the PSA. The machine is in the RMM. The client’s setup is in the documentation tool, the user is in the Microsoft 365 admin center, and the time entry goes back into the PSA at the end. None of those trips is long. Added up, they are a big part of the day.

It’s tough to fix this by asking people to be more disciplined. What works is moving what the tech needs onto the ticket. Below is where the trips happen, a calculator to put a number on them for your own team, the fixes you can make with the tools you already have, and how Toolqit closes the rest of the gap.

Where do techs actually switch?

If you’ve run a service desk, you know the loop. A ticket comes in, and before the tech can do anything useful they need answers the PSA doesn’t hold:

  • Which machine is this about, and is it online?
  • Does it already have open alerts?
  • What’s installed on it, and is it patched?
  • Who is the user, and is their Microsoft 365 account locked, out of licenses or failing MFA?
  • Is there a doc for how this client does this?

Every answer lives in a different tool. So the tech copies a name out of the ticket, searches for it in the RMM, picks the right device out of three with nearly the same name, reads, comes back, writes a note, and does it again for the next question. Then they log time in the PSA from memory.

What does the switching cost?

It isn’t the clicking. It’s the search every time, the wrong device picked from a list, the note that never gets written because the answer was in another window, and the minute it takes to get your head back into the ticket. Put your own numbers in. The defaults are deliberately modest.

What PSA–RMM switching costs your team

Lost per tech, per week2.5 hoursLost across the team, per month53 hoursBillable time that represents, per month$6,300

If the per-tech number looks small, time a few real trips. Once you count finding the device and getting back into the ticket, most come in well over a minute, and that is before the trips to documentation and Microsoft 365.

Can your techs work a ticket without leaving it?

Tick what’s true for your team today. Each box you can’t tick is a trip your techs make on every ticket of that kind.

Can a tech work a typical ticket without leaving it?

0 of 9.

Fix it with the tools you already have

You can cut a lot of the switching without buying anything. In order of payoff:

  1. Match devices to companies and contacts. Most PSA and RMM pairs sync assets or configurations. Turn it on and fix the matching once, so the ticket at least names the right machine.
  2. Make the RMM write context into the tickets it opens. The device, the condition and the reading belong in the ticket body, not behind a link.
  3. Put the runbook on the ticket type. If a low-disk ticket always needs the same three checks, write them into the ticket template so nobody goes looking.
  4. Pick one home for client documentation and link it from the company in the PSA.
  5. Agree when time gets logged. At the moment the work is done, in one place. Time rebuilt at five o’clock is time you don’t bill.

That helps, but a PSA is built around the ticket and an RMM around the device, so your techs still end up with five screens open.

Why not one all-in-one PSA and RMM?

Some PSAs come with an RMM built in, and some RMMs come with ticketing. It’s a fair question whether that settles it. Usually it doesn’t. The bundled versions tend to be basic on both sides: a light PSA and a light RMM, each missing things a serious MSP leans on every day.

What you want is choice. Your team should run the strongest PSA and the strongest RMM for the way you work, and the best tool for everything else, without paying for it in tabs. Locking everyone into one platform that isn’t great at either job swaps one problem for a worse one.

Go further than the PSA and the RMM

This is the problem Toolqit solves, and it doesn’t stop at sitting on top of your PSA and RMM. We realized early that the real advantage comes from going much further: building the best experience a technician has ever had, not only with the PSA and the RMM but with every other tool an MSP runs. Toolqit is one screen where your techs can do all their work: tickets, device context, documentation, Microsoft 365, client chat, scripts, time and billing. Your PSA stays the system of record, and you keep the tools you chose.

If all it does is join the PSA and the RMM, you’ve taken your tool count from 18 to 16 and your techs still spend the day switching.

When every tool they touch comes together in one place, the time comes back.

That’s what a single platform needs to be able to do.

It also has to get the small things right: knowing that the user on the ticket and the account in Microsoft 365 are the same person, and working out what’s wrong whether it’s a workstation, a server, a printer or a virtual machine. That takes a level of robustness a dashboard over two tools doesn’t have.

Techs on Toolqit typically get 10 to 15 hours back per week. It’s a new kind of product, so it’s easier to show than to describe. Put your own numbers in the calculator above, then book a demo and see what that time looks like for your team.

← All posts

Book a demo

See Toolqit on tickets like yours.