AI 模型和平台
连接Wise 发布 RMM Agent 使用技术员认可的固定设备来调查 IT 车票
在 Google 上的首选来源中添加 Unite.AI
ConnectWise拥有发布 RMM Agent，对技术人员已经工作的服务票带来了AI主导的端点调查。 宣布于10月29日，产品检查一个连接的装置，测试可能的原因，从一个经过审查的目录中分期进行补救。 每个设备的改变都需要技术员的明确批准。
发布的公告中也包含推出语音，Teams，以及电子邮件Agents，用于在技术工作开始前收集客户信息。 所有四种皆可通达。 它们共同针对服务台延迟的两个来源：不完整的请求和重复的故障排除。
结束点调查移入车票
RMM代表远程监测和管理，而PSA则指专业服务自动化。 将两个带来服务请求和管理的设备连接到同一个工作上下文。
ConnectWise的AI Agents产品页面呈现一个协调的序列。 摄入agents捕获用户，设备，撞击，和紧急。 服务台Agents对请求进行分类和优先排序，查阅其历史，并引导工作。 RMM Agent然后检查终点，支持经批准的固定，并记录结果。
这种顺序很重要，因为票的描述和装置的实际状况可能有所不同。 agent既能接触，又能帮助将报告的症状与来自环境的证据联系起来。 对于技术人员来说，有益的交接包括调查的内容和拟议下一步的推理。
产品页描述一个共享服务记录，将接收内容，服务工作流程，设备证据联系起来。 将这些行动合并起来，使技术员有更完整的基础审查提议的行动。
人类批准从设备变化中分离诊断
根据发布公告，新的agent在调查期间使用只读诊断，在改变终点前需要授权。 这使批准决定处于工作流程的必然阶段：在收集证据之后，在补救办法影响客户系统之前。
早期结果仍由伙伴报告。 RealBytes报告对超过500张活门票的91%进行了有用的诊断，一般在一分钟左右。 其更广泛的ConnectWise Agentic部署将第一触点时间从1小时减少到5分钟。 这些措施描述了服务提供的不同阶段，应单独评估。
现有的 RMM 堆栈用品操作工具
公司RMM平台已经结合了监控，补丁，脚本和远程访问。 其文献记载的能力包括操作系统及第三方应用补丁管理，由其网络操作中心调节的监测条件，以及通过ScreenConnect进行远程故障排除。
它还列出了AI辅助脚本生成，网络发现和分析，以及集中报告。 这些能力为新的agent的作用提供了背景：调查与技术人员用来维护和修理终点的既定工具同时进行。
实际价值取决于调查如何为具体装置和服务情况选择适当的行动。 生成的解释是有用的，但业务工作流程也需要明确的拟议修改和另一名技术员稍后可以审查的记录。
更广泛的代理平台战略
ConnectWise的平台架构描述了一个被代理层包围的统一数据基础。 共享的工作流程和服务连接应用程序，而开放API则支持跨系统的工作。 该设计旨在给agents提供相关的操作环境，而不是使每个应用程序单独运行。
这个方向遵循了该公司1月关于ZofiQ的收购公告，该公告的重点是使大量服务台工作自动化。 ConnectWise描述了通过API，连接器和事件集成来连接遥测，门票，以及监测信息，然后将AI应用于分类，优先排序，异常检测以及建议的根源。
最新发布将轨迹延伸至终点调查。 其中心建议是缩短从客户要求到证据支持的补救决定的路径，由技术员保留对变化的控制。 对管理下的服务提供者来说，检验标准是，这一进程如何持续减少他们所支持的各种环境中的调查工作。
本文由 AI图鉴自动抓取并翻译，版权归原作者所有；如需查看原文请点下方链接。
AI Models & Platforms
ConnectWise Launches RMM Agent to Investigate IT Tickets With Technician-Approved Fixes
Add Unite.AI to your preferred sources on Google
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.
Auto-fetched and translated by AI Atlas. All rights belong to the original author.