“Remote monitoring” gets used like it answers the whole question of how support works. It doesn't. Here's what genuinely gets covered without anyone in the building — and the specific situations that still need someone on-site.
Comparing managed IT providers, it’s common to hear “remote monitoring” used almost as a selling point on its own, as if it answers the whole question of how support works. It doesn’t. Remote monitoring is one part of how a provider delivers support — a genuinely important part — but it doesn’t replace the need for someone to occasionally show up in person.
Remote monitoring and management (RMM) is software that lets an IT provider observe, maintain, and fix a business’s systems over the internet — without a technician physically present — covering things like patch deployment, performance monitoring, security alerts, and most day-to-day troubleshooting.
“Good IT shouldn’t be something you notice. If it is, that’s the signal something’s missing.”
— Jeffrey Bowles, Partner & Director of IT Services, ACT360
The useful question isn’t “remote or on-site.” It’s which category a given problem actually falls into, and whether your provider has a clear answer for that before something breaks.
What Remote Monitoring Actually Covers
The bulk of managed IT work happens through RMM tools, and for most issues that’s genuinely the faster path — no travel time, no waiting for a technician’s schedule to open up.
Remote monitoring and remote support typically cover:
- Performance monitoring — server load, disk space, memory usage, and network performance tracked continuously, with alerts before a slow system becomes a down system
- Patch management — security updates and software patches deployed on a schedule, without anyone needing physical access to each machine
- Security monitoring — endpoint protection alerts, unusual login activity, and firewall events reviewed and acted on in real time
- Software troubleshooting — application errors, login issues, printer configuration problems, and most day-to-day helpdesk tickets
- Backup verification — confirming backup jobs actually completed, not just that they were scheduled
- Remote reboot and recovery — restarting services, clearing caches, and recovering from many software-level failures without anyone leaving their desk
This list covers a large majority of what generates support tickets in a typical small or mid-sized business. It’s also the reason “remote-first” providers can usually respond faster than a purely on-site model — there’s no travel time between a ticket being opened and someone starting on it.
What Genuinely Requires an On-Site Visit
A smaller, more specific set of situations can’t be resolved without a person physically present, regardless of how good the remote tooling is:
- Hardware failures — a failed hard drive, power supply, or network switch has to be physically replaced
- New equipment setup — installing workstations, servers, or network hardware for the first time
- Structured cabling and physical network changes — running new cable, reconfiguring a server room, adjusting physical network layout
- Situations where the network itself is down — if the internet connection or core network hardware has failed, remote tools can’t reach the affected systems at all
- Hands-on training or a genuinely complex handoff — some onboarding and training scenarios go faster with someone in the room
- Physical security and access control — badge systems, camera installs, and similar physical-layer work
None of this is a knock on remote-first support. It’s simply a different category of problem. A server that won’t boot because of a failed component isn’t something any amount of remote access fixes — someone has to open the case.
The Real Difference Isn’t “Better.” It’s “Different Problems.”
A common misconception is treating “remote” and “on-site” as competing service tiers, where one is more premium than the other. That framing misses the point. The two aren’t ranked against each other — they solve different categories of problem, and a provider that’s genuinely good at remote support still needs a plan for the on-site half.
The Canadian Centre for Cyber Security’s baseline guidance for small and medium organizations treats remote access itself as something that needs to be actively managed — inventoried, patched, and monitored like any other system, not assumed to be secure by default. That’s worth knowing because the quality of a provider’s remote tooling isn’t just about speed. A remote monitoring platform that isn’t properly secured is itself a risk, since it typically has deep access into a business’s systems. A provider’s remote-access security posture is worth asking about directly, not just their response times.
How a Good Provider Decides When On-Site Is Needed
A well-run managed IT relationship has a clear default: try remote first, since it’s faster for most issues, and escalate to on-site when the problem’s nature requires it. That escalation shouldn’t be a mystery. A few signals that typically trigger it:
- Remote diagnostics point to a hardware component, not a software or configuration issue
- The affected system can’t be reached remotely at all (network down, device won’t power on)
- The situation involves physical installation, cabling, or equipment that has to be handled in person
- A genuine security incident requires physically isolating a device from the network
If a provider can’t articulate this decision process — or defaults to “we’ll figure it out when it happens” — that’s a sign the on-site half of the relationship hasn’t actually been planned.
What This Looks Like at ACT360
ACT360 offers both a remote-only plan and a full-service plan that includes site visits, because different businesses genuinely need different coverage. A business running entirely cloud-based software with straightforward hardware has different needs than a manufacturer with production floor equipment and physical network infrastructure to maintain.
What doesn’t change between the two is the standard for what remote monitoring actually includes — the difference is in the site-visit coverage layered on top, not in the depth of the remote side. That’s part of why the scope of managed IT is worth reading in full before comparing remote-only and full-service pricing; the categories above should be covered either way, and the real variable is how on-site work is handled when it’s genuinely needed.
Final Thought
The question worth asking a prospective provider isn’t “are you remote or on-site.” It’s “walk me through what happens when an issue turns out to need someone in the building.” A provider with a clear, specific answer to that has actually thought about the on-site half of the job. One without a clear answer is describing remote monitoring as if it’s the whole service, which it isn’t.
T: 705-739-2281 E: [email protected]
