Six published NOC purchase choices
These six purchases from four suppliers in our reviewed directory name Automate at service level. Their source dates describe the material checked. Use the published scope to prepare an exact request, then settle the current version, access and deliverables in the proposal.
Benchmark365 / NOC Launch
The NOC page lists ConnectWise Automate alongside its three work-allowance plans. NOC plans / 2026-10-17 (external website)
Published plan or charging basis: USD 990/month starting price. Includes 3 customer environments and 10 investigations per month, with email intake. Endpoint, user and ticket intake is advertised as unlimited; completed work is capped by the plan allowances. NOC plans / 2026-10-17 (external website)
Ask in the proposal: Which alert-to-ticket route and script actions are in this plan? Specify what counts as an investigation or remediation, any included allowance, approval holds and excess-work charges.
Read provider details / RFP for this service / Download service brief
Benchmark365 / NOC Connect
The NOC page lists ConnectWise Automate alongside its three work-allowance plans. NOC plans / 2026-10-17 (external website)
Published plan or charging basis: USD 2,990/month starting price. Includes 10 customer environments, 25 investigations and 10 remediations per month, plus live two-way PSA integration. Major Incident Response is an add-on; unlimited tickets do not mean unlimited completed work. NOC plans / 2026-10-17 (external website)
Ask in the proposal: Which alert-to-ticket route and script actions are in this plan? Specify what counts as an investigation or remediation, any included allowance, approval holds and excess-work charges.
Read provider details / RFP for this service / Download service brief
Benchmark365 / NOC Enterprise
The NOC page lists ConnectWise Automate alongside its three work-allowance plans. NOC plans / 2026-10-17 (external website)
Published plan or charging basis: USD 9,990/month starting price for customized scope, with unlimited approved customer environments. The page lists contractual SLA alignment, compliance agreements and a named-resources option; investigation and remediation quantities need a written scope. NOC plans / 2026-10-17 (external website)
Ask in the proposal: Which alert-to-ticket route and script actions are in this plan? Specify what counts as an investigation or remediation, any included allowance, approval holds and excess-work charges.
Read provider details / RFP for this service / Download service brief
Infrassist / Managed MSP NOC
The NOC page shows the ConnectWise Automate logo. The proposed tasks and connector need confirmation. Source / 2026-11-06 (external website)
Published plan or charging basis: Fixed monthly pricing tied to devices; no numeric rate is shown on the reviewed NOC page. Source / 2026-11-06 (external website)
Ask in the proposal: Which Automate monitoring, scripts, patching and PSA handbacks are included in the managed NOC quote? Price extra projects or named POD staffing separately.
Read provider details / RFP for this service / Download service brief
NOC 24/7 / Managed MSP NOC
The NOC service page names ConnectWise Automate in its supported-tool sections. Detailed RMM / PSA sections / 2026-10-15 (external website)
Approved-script scope: The RMM integration page says operators execute existing scripts on the MSP-approved allow-list, do not write, alter or upload scripts, and escalate an unlisted action for approval. Agree who owns the approved revision, required parameters, devices, maintenance window, recorded result and handback before enabling the workflow. Script execution and approval rules / 2026-10-15 (external website)
Ask in the proposal: Which existing script references and versions are approved for which clients? Define the on-call decision and accepting owner for an unlisted action, failed run or missing history.
Read provider details / RFP for this service / Download service brief
Worksent / MSP NOC
The NOC service information lists ConnectWise Automate alongside Standard and Premium work plans. NOC service page / 2026-10-15 (external website)
Choose the NOC work plan: Both Worksent NOC plans list continuous monitoring, alert triage/remediation, patching, AV/EDR administration and daily summaries. The Standard plan marks RMM consulting, backup checks and vendor coordination as excluded; Premium marks them included. Select the plan in the order, separately from shared or exclusively assigned POD staffing. Define the permitted changes, backup-check result and vendor handoff; plan ticks alone do not establish restore validation or security incident response. NOC Standard/Premium plan table / 2026-10-20 (external website)
Ask in the proposal: Which Standard/Premium tasks and POD assignment are quoted? Map allowed Automate work and the accepting PSA owner separately; name any consulting or vendor tasks excluded.
Read provider details / RFP for this service / Download service brief
Benchmark365's three NOC plans have separate allowances and prices. Obtain the alert-to-ticket route and counting rules alongside the chosen plan. For Worksent, name Standard or Premium work as well as the shared or exclusively assigned POD model. Infrassist's managed NOC and named POD staffing require separate purchase decisions. Keep each purchase attached to its own service brief.
Name the actual product and service
ConnectWise's Automate product FAQ (external website) identifies Automate and ConnectWise RMM as separate tools. Its current Automate description covers script drafting, libraries and scheduling, patch approval, pilot groups and maintenance windows. Keep the software capabilities and the supplier's accepted duties together in the order.
Specify Automate, the deployed version and hosting arrangement, then name the actual ticket system and any remote-support product. Ask whether analysts work in your queue, exchange updates with a supplier queue, or use both. Define which client, device and ticket identifiers connect each step.
The integration worksheet captures the working queue, mapping, permissions and failure owner. The ConnectWise PSA section covers help desk ticket handling; this guide concerns infrastructure NOC work in Automate.
Approve a script revision and its target
The Automate product page (external website) describes AI-assisted PowerShell drafting with human review and approval, plus a custom library and scheduling. Ask who may prepare a draft, review it, change the library, schedule a run and execute it. Document those decisions separately, including any work your MSP retains.
NOC 24/7's RMM operating description (external website) describes an MSP-approved list of existing scripts and escalation for an unlisted action. Its stated scope excludes writing, modifying or uploading scripts. Ask how an approved reference, revision and parameter set are accepted for your order, and who handles a change to that script after approval.
| Put in the action schedule | Define before the operator acts |
|---|---|
| Approved script | Library reference, reviewed revision, required parameters and approval owner |
| Target inventory | Enrolled clients, sites and devices; how an added or moved device becomes eligible |
| Execution conditions | Permitted trigger, maintenance window, preconditions and required notification |
| Exception | Who accepts a request for a new revision, different target or unlisted action |
| Result | Device, responsible identity, script reference, start/end, output and resulting ticket |
| Failed or interrupted work | Who may stop, retry or approve recovery, and who accepts the unfinished item |
Ask the MSP administrator to demonstrate the effective access of the proposed role on your deployed release. Include its assigned classes, client/device reach, group memberships, available commands and library permissions in that review. The allowed-action schedule should still identify the person who can approve an exception.
Keep patch approval and restart authority separate
The maker's Automate description names approval workflows, pilot groups and maintenance windows. Assign the people who choose the update, accept the first device results, expand deployment and manage the end of the window. Define the permitted device group before a broadly targeted change is scheduled.
Write a separate restart decision for service-hosting devices. Specify the latest allowed start, notification, application owner and next action if approval is unavailable or the job runs beyond its window. Reconcile offline devices and failed updates with a named owner. Use the patching and restart guide for the wider action schedule.
Return the result to an accepting PSA owner
Agree where the alert is acknowledged, where the script or patch result is recorded and which ticket receives the work. Define the company and board, note audience, status, time entry and escalation destination in the actual PSA or receiving queue.
NOC 24/7 describes Automate operations alongside ConnectWise Manage ticket updates. Ask each candidate to show its own promised route. Decide what happens if the endpoint action finishes but the ticket update fails: preserve the action reference and keep the failed exchange assigned until the receiving ticket is reconciled.
Request the history your MSP can retrieve during service and at handover. Identify device history, ticket notes, script output and any separate recordings as distinct items, with their access and retention rules. The exit access plan covers accounts, integrations and other retained access.
Try six bounded cases
Example pilot cases. Agree the devices, permissions and expected results with the responsible owners.
| Proposed case | Outcome to agree and preserve |
|---|---|
| The approved script changes before its scheduled run | The new revision reaches its review owner before execution is accepted |
| A request names a device outside the purchased client scope | The action stays within the authorized inventory and the exception reaches its owner |
| A proposed patch group reaches more devices than the approved pilot | The operator identifies the actual target set and obtains the required expansion decision |
| A restart lacks approval near the end of the maintenance window | The case follows the agreed hold or handback, with the next accepting owner and time |
| Automate work completes while its PSA update is unavailable | The action result and failed exchange remain traceable until the receiving ticket is reconciled |
| Operator access is revoked while a scheduled action remains | The MSP accounts for the schedule, retained service identities and the safe next owner |
Keep the first attempt and any correction in the existing NOC pilot log. Reuse the integration worksheet for the agreed mapping and action boundaries. Price the selected service, software fees, included work, excess charges and retained MSP effort in the quote worksheet.