ConnectWise Launches RMM Agent to Investigate IT Tickets With Technician-Approved Fixes

ConnectWise has launched RMM Agent, bringing AI-led endpoint investigation into the service ticket where technicians already work. Announced on October 29, the product examines a linked device, tests possible causes, and stages a remedy from a vetted catalog. Every device change requires a technician’s explicit approval.

The launch announcement also introduces Voice, Teams, and Email Agents for gathering customer information before technical work begins. All four are generally available. Together, they target two sources of service-desk delay: incomplete requests and repetitive troubleshooting.

Endpoint Investigation Moves Into the Ticket

RMM stands for remote monitoring and management, while PSA refers to professional services automation. Connecting the two brings the service request and the managed device into the same working context.

ConnectWise’s AI Agents product page presents a coordinated sequence. Intake agents capture the user, device, impact, and urgency. Service Desk Agents classify and prioritize the request, consult its history, and route the work. RMM Agent then inspects the endpoint, supports an approved fix, and records the result.

That sequence matters because a ticket’s description and the device’s actual condition can differ. An agent with access to both can help connect the reported symptom to evidence from the environment. For technicians, a useful handoff includes what was investigated and the reasoning behind the proposed next step.

The product page describes a shared service record linking intake context, service workflow, and device evidence. Keeping those together gives the technician a more complete basis for reviewing the proposed action.

Human Approval Separates Diagnosis From Device Changes

According to the launch announcement, the new agent uses read-only diagnostics during investigation and requires authorization before changing an endpoint. That places the approval decision at a consequential point in the workflow: after evidence has been gathered, before a remedy affects a customer’s system.

Early results remain partner-reported. RealBytes reported useful diagnoses on 91% of more than 500 live tickets, typically in about a minute. Its broader ConnectWise Agentic deployment reduced first-touch time from an hour to five minutes. Those measures describe different stages of service delivery and should be assessed separately.

The Existing RMM Stack Supplies the Operational Tools

The company’s RMM platform already combines monitoring, patching, scripting, and remote access. Its documented capabilities include operating-system and third-party application patch management, monitoring conditions tuned by its network operations center, and remote troubleshooting through ScreenConnect.

It also lists AI-assisted script generation, network discovery and analysis, and centralized reporting. These capabilities provide context for the new agent’s role: investigation sits alongside established tools that technicians use to maintain and repair endpoints.

The practical value depends on how well the investigation selects an appropriate action for the specific device and service situation. A generated explanation is useful, but an operational workflow also needs a clear proposed change and a record that another technician can review later.

A Broader Agentic Platform Strategy

ConnectWise’s platform architecture describes a unified data foundation surrounded by an agentic layer. Shared workflows and services connect applications, while open APIs support work across systems. The design aims to give agents relevant operational context rather than make each application operate in isolation.

That direction follows the company’s January acquisition announcement for zofiQ, which focused on automating high-volume service-desk work. ConnectWise described connecting telemetry, tickets, and monitoring information through APIs, connectors, and event-based integrations, then applying AI to classification, prioritization, anomaly detection, and suggested root causes.

The latest release extends that trajectory toward endpoint investigation. Its central proposition is a shorter path from a customer’s request to an evidence-backed remediation decision, with the technician retaining control over changes. For managed service providers, the test will be how consistently that process reduces investigation effort across the varied environments they support.