What the service evidence establishes
NOCDOC describes a white-label NOC with 24/7 monitoring and operational maintenance. Its About page positions the company as a US-based MSP operations partner. That wording is a provider claim, not a verified service-specific staffing or data-location guarantee. See the official service source.
Commercial boundary to resolve
The referral page uses a $1,000 monthly engagement threshold to qualify a referral. A referral qualification threshold is not a published NOC price, universal service minimum or complete fee schedule. Request the actual service order.
Qualification by scenario
| Your scenario | First question | Evidence to retain |
|---|---|---|
| US staffing requirement | Which shifts and escalation functions are staffed in the required country? | Service-specific roster commitment without personal staff details |
| Mixed NOC and SOC | Who owns an alert that becomes a suspected security incident? | A joint escalation map and separation of incident authority |
| Referral threshold | Does the proposed service have its own minimum? | Signed service quote independent of referral qualification |
Bring a defined inventory and anonymized workload to the first discussion. Device counts, user counts and ticket volumes describe different obligations. Record a missing answer as unresolved; do not substitute a zero cost, an assumed capability or a negative quality judgment. Ask the supplier to identify the applicable plan and legal entity in its reply.
Public customer evidence and its limits
The pages reviewed here establish provider positioning and a referral program. They do not establish an independently interviewed customer outcome for the proposed NOC service. Ask for a reference operating a similar estate and verify the dates, coverage and action scope directly before relying on that experience.
For a reference conversation, ask when the service was used, which plan and shifts were involved, what the customer retained internally and whether a material incident or exit was experienced. A named comment can help identify a question to investigate, but it does not establish the full SLA, staffing model or suitability for your clients.
A bounded pilot before enrollment
Pilot a network alert that needs an application owner's approval. Record how NOCDOC identifies the affected tenant, finds the permitted runbook and hands off when it cannot act. Add a backup failure and require the ticket to distinguish checking a job from proving recoverability. A successful status check should not close a restore-test requirement.
Define pass and fail criteria before testing: correct tenant, permitted action, an intelligible audit trail, accepted escalation and a reversible access path. Preserve both successful and unsuccessful cases. Use these criteria when agreeing your own pilot.
Compare the same obligation
Use the provider directory to select candidates, then send one RFP with identical scope. Normalize the quote in the cost calculator and record the five SLA clocks separately. Confirm staff and data locations, notice and exit work in writing before granting production access. Read our methodology or send a sourced correction.