Published service details
Service details from Kaseya, checked . How to read these terms.
- Who the service is for
- NOC serves MSP personnel. Separate Help Desk must form part of managed service; branding and additional fees require confirmation. Source / 2026-11-06 (external website) Source / 2026-11-06 (external website)
- Service hours
- NOC advertises 24/7 endpoint operations. Separate Help Desk offers an order-selected window, including 24/7/365. Source / 2026-11-06 (external website) Source / 2026-11-06 (external website)
- Contact channels
- NOC contacts MSP personnel by phone, email or SMS. Separate Help Desk accepts registered end-user phone/email requests in English. Source / 2026-11-06 (external website) Source / 2026-11-06 (external website)
- Onboarding fees
- Scoping and onboarding fees apply as set out in the order; no amount is given in the reviewed terms. Source / 2026-11-06 (external website)
Not published: team location, time to go live, time to receive a quote. Ask for these in the proposal.
Services and plans
| Service | Hours | Price and billing unit | Team | Request |
|---|---|---|---|---|
| Endpoint NOC for MSP personnel | 24/7 endpoint monitoring and management are advertised; scope depends on the order. Source / 2026-11-06 (external website) | Covered endpoints require NOC licenses. Fees, license pools and monthly or annual advance payment are described; amounts are order-specific. Source / 2026-11-06 (external website) | Not published. | RFP for this service Service brief |
| Help Desk Services - per-device or per-ticket | 24/7/365 is an order option; the purchased window controls support. Source / 2026-11-06 (external website) | Per-device licences or monthly ticket batches; rates, onboarding and overages are order-specific. Source / 2026-11-06 (external website) | Not published. | RFP for this service Service brief |
| Dedicated Resource (NOC add-on) | Not published. | Not published. | The separately purchased Dedicated Resource add-on names specific Kaseya personnel. This does not define the standard NOC team model, exclusive full-time assignment or a covered shift. Confirm assignment, replacement and management duties. Source / 2026-11-06 (external website) | RFP for this service Service brief |
Terms and working arrangements
- Contract length - Endpoint NOC for MSP personnel
- An order defines the committed term. Removing covered endpoints does not automatically reduce the committed licenses. Source / 2026-11-06 (external website)
- Contact channels - Endpoint NOC for MSP personnel
- Telephone, email or SMS to the MSP customer as detailed in the Onboarding Summary; not end-user contact. Source / 2026-11-06 (external website)
- Contact channels - Help Desk Services - per-device or per-ticket
- English phone/email for registered users; international-call options cost extra. Source / 2026-11-06 (external website)
- Tools - Help Desk Services - per-device or per-ticket
- Help Desk RMM examples are Datto RMM/Kaseya VSA. RMM, IT Glue and supported PSA subscriptions cost extra; obtain the current supported-product list. Source / 2026-11-06 (external website)
- Minimum order - Help Desk Services - per-device or per-ticket
- Help Desk per-ticket requires 400 registered devices. Per-device covers all supported employee devices and RMM-managed contractor devices. Source / 2026-11-06 (external website)
- Contract length - Help Desk Services - per-device or per-ticket
- Order-defined committed term; advance monthly payment does not confer monthly cancellation or unit reductions. Source / 2026-11-06 (external website)
- Audience and resale - Help Desk Services - per-device or per-ticket
- MSPs must bundle Help Desk with managed service. Low-touch resale is excluded; a custom phone greeting costs extra. Source / 2026-11-06 (external website)
Service conditions
- Endpoint NOC for MSP personnel; Help Desk Services - per-device or per-ticket; Dedicated Resource (NOC add-on): Where the linked Master Agreement applies, committed subscriptions need cancellation or renewal opt-out notice at least 30 days before term end. This is not mid-term release from committed payments. Confirm the signed order, applicable master and required notice channel. Source / 2026-11-06 (external website) Source / 2026-11-06 (external website)
- Help Desk Services - per-device or per-ticket: Monthly tickets expire; each started 30 minutes uses one. After 60 minutes Kaseya may return the issue or charge more tickets; overages come in fives. Source / 2026-11-06 (external website)
- Help Desk Services - per-device or per-ticket: Help Desk SLOs begin after 60 days; request targets and the ramp-period escalation plan. Source / 2026-11-06 (external website)
- Dedicated Resource (NOC add-on): Dedicated Resource is a separate NOC-related capacity add-on with its own agreed service description. It supplements NOC operations; end-user Help Desk is separate. Specify exclusive allocation, shift hours and named tools in the resource order. Source / 2026-11-06 (external website)
- Dedicated Resource (NOC add-on): Remote Hands is typically purchased as monthly hours that expire unused; the terms call Dedicated Resource similar. Have the resource order state its hours, expiry, excess use, staff replacement and approval rules. Source / 2026-11-06 (external website)
Not published for the selected service
- Endpoint NOC for MSP personnel: Tools, Minimum order.
- Dedicated Resource (NOC add-on): Tools, Minimum order, Contract length, Contact channels.
Ask for these in the proposal. Terms published for another service do not fill these gaps.
Points to settle before signing
NOC history and export limits
NOC terms retain ticket information for six months after creation during a subscription and make it unavailable for customer export. Agree your own decision history and handover path before service starts. Source / 2026-11-06 (external website)
Help Desk history and handover
Help Desk retains ticket information for one year during a subscription and exposes incident details through PSA. Confirm permitted exports and attachments. Call recordings are not normally released; the terms reserve court-order or discretionary exceptional release. Source / 2026-11-06 (external website)
- NOC does not support your clients' end users. The separate Help Desk order covers eligible user devices and peripherals; standard scope excludes shared servers and networks.
- Reducing endpoint inventory does not automatically end payment for licenses committed through the subscription term.
- Remote Hands and Dedicated Resource services are add-ons, rather than proof that the standard NOC assigns an exclusive technician.
- Help Desk's 400-device threshold applies to the per-ticket model. Its per-device model instead requires all eligible employee devices and RMM-managed contractor devices.
How Help Desk ticket units add up
Under Kaseya's per-ticket Help Desk model, a support request can consume more than one paid ticket. Its Help Desk Services terms (external website), checked 6 November 2026, use full 30-minute units. A short request still uses one unit; a request requiring more than 30 minutes uses a second. These are billing units, not a 30-minute response or resolution commitment.
Four requests can use six units
Invented durations illustrate the counting rule below. They are not observed resolution times, a provider performance test or a quoted package.
| Illustrative request | Help Desk service time | Billable ticket units |
|---|---|---|
| A | 20 minutes | 1 |
| B | 30 minutes | 1 |
| C | 31 minutes | 2 |
| D | 55 minutes | 2 |
| Total | 136 minutes across four requests | 6 |
The 136 minutes cannot be pooled into five units: each request uses full units separately. After 60 minutes on one request, Kaseya may transfer it back to the MSP or continue with additional billable units. Agree the return path and owner of the remaining work; the example does not assume that every longer request stays with the desk.
Apply the monthly batch separately
For arithmetic only, suppose an order includes 50 monthly units and recorded usage reaches 57 units. The seven-unit excess requires two five-ticket overage batches, or 10 overage units to purchase. The order sets the overage rate, so these counts do not establish a monetary charge. Fifty units is an invented allowance, not a published Kaseya package.
Unused monthly units are forfeited at month end. Confirm how the supplier reports service time, reopened requests, overage purchases and any unused overage units; do not assume that purchased capacity carries into another month. This per-ticket model requires at least 400 registered devices. The separate per-device model has different enrollment rules.
Use the Help Desk service brief for the service boundary, then put the monthly allowance, overage rate, required subscriptions and retained MSP work into the quote worksheet. Compare the complete workload cost rather than treating one logged request as one paid unit.
Fits when
- The MSP wants endpoint operational work with escalation to its own staff.
- You can maintain the supported RMM, covered-endpoint inventory and customer-side contacts required by the NOC arrangement.
- You need registered end-user support as part of an MSP managed service and can meet its separate subscription and licence requirements.
Questions for Kaseya
- Which NOC endpoints and RMM versions are approved, and which Help Desk RMM, IT Glue and PSA subscriptions must we supply separately?
- How do license pools, added devices and removed devices change the payable commitment?
- What scoping and onboarding charges are in this order, and which service events require another charge?
- For Help Desk, how many billable 30-minute ticket units, expired units and five-ticket overage batches should we budget for our workload?
- Which Help Desk targets apply during the first 60 days, and how will we preserve operational history given the different NOC export and desk recording limits?
Supplier-published customer account
Kaseya publishes a Crystal Mountain case study naming Shawn Edie, its IT director. It describes the resort using VSA and adding server and patch management to its NOC agreement. This is a supplier-published account of a corporate IT engagement, not an MSP plan or an independently measured result. Source / 2026-11-06 (external website)