What the official NOC page establishes
The NOC page describes MSP white-label monitoring, triage, remediation, patch and backup checks, with daily reporting. Its FAQ states a 50-device minimum, month-to-month contracting and a 20-minute action claim for critical alerts. Reviewed 2026-10-06. Obtain the actual order and severity definitions before relying on these terms.
The same page names NinjaRMM, Kaseya, ConnectWise Automate, Datto RMM, Auvik, IT Glue and Halo. The directory groups NinjaRMM with NinjaOne for discovery, while keeping an unspecified Halo label separate from HaloPSA. That normalization does not certify product version compatibility or integration depth.
Is your estate eligible?
The device minimum is an immediate qualification question for a smaller MSP. Ask what a device means in the proposed service, whether several clients can share the minimum, and whether monitoring-only assets count. Do not calculate an apparent price per endpoint before confirming the billable inventory.
| Estate or workload | Question to ask first | Evidence to retain |
|---|---|---|
| Fewer than the published device minimum | Is an exception available for this service? | Written eligibility and minimum charge |
| Several client environments | How are tenant access and escalation separated? | Role map and tenant-level test |
| Backup alerts dominate the queue | Does a check include restore testing or only status review? | Explicit scope and test artifact |
| Patch work carries business risk | Who approves changes and owns rollback? | Change authority and rollback record |
Do not treat this table as an eligibility decision. It identifies the first missing answer. Device count alone says little about alert noise or time needed for safe remediation. Send a recent workload sample with confidential client details removed, together with the exclusions your clients expect.
What remains unknown in a quote
The reviewed page does not provide a universal rate or a complete fee schedule. Request the billing unit, minimum charge, onboarding work, overage, retained management effort, notice period and exit work as separate lines. Month-to-month wording does not settle when notice is due or how prepaid charges and data return work.
Use the NOC quote worksheet to compare the same inventory and action scope. If you also need end-user ticket handling, request a separate help desk scope instead of assuming NOC remediation includes user contact. The white-label help desk guide explains that distinction.
Evaluate the action target and escalation seam
The critical-alert statement needs a precise start event and a definition of action. Is the provider beginning investigation, performing an approved fix or handing off to your engineer? Ask what stops the clock when credentials fail or the fix requires an authorization. A fast first action does not itself prove a fast restore.
An illustrative pilot can contain a routine alert with a documented runbook, a critical alert requiring your approval, and an alert that belongs to an external application vendor. For each, retain the ticket timestamps, actual action, identity, client mapping and next owner. Choose pass thresholds before the pilot starts. These are suggested tests, not Worksent performance results.
Security and your tools
The NOC FAQ claims ISO/IEC 27001:2022 certification and access inside the MSP's RMM/PSA environment. This site has not independently validated the certificate or the proposed service's data flow. Ask for certificate scope and validity, access controls, subprocessors and incident-notification terms.
Working in your tools does not by itself show that no information reaches email, reporting, backups or another system. Obtain a flow diagram for the actual service. Test independent account revocation and review an audit record. The integration worksheet can capture those answers.
Public partner testimony
Worksent's professional-services page carries named partner testimonials, reviewed 2026-10-06. It attributes a dedicated-to-shared help desk experience to Andrew Miller, IT Service Desk Manager at Circle MSP, and NOC/SOC monitoring comments to Paul Casey, COO of Paradyn. These are testimonials selected and published by Worksent; their original publication dates are not displayed, and we have not independently interviewed the speakers.
The Worksent Clutch profile showed no client reviews when checked. That is a finding about this source, not evidence that no customers have reviewed Worksent anywhere. Employee reviews do not establish buyer experience. Request a current reference for your proposed service, hours and workflow, and distinguish help desk testimony from NOC performance.
Next step
Compare Infrassist's NOC evidence if you are considering similar external remediation models. Keep proposals aligned to one RFP and compare public fields in the provider directory. Missing answers are evidence gaps rather than negative capability verdicts. See our methodology or send a sourced correction.