What the service evidence establishes
Support My MSP publicly presents outsourced help desk, NOC, SOC and project services for MSPs. The homepage is a qualification source, not a complete operational specification. Exact coverage, named product workflows, severity clocks and current rates remain questions for the proposed service. See the official service source.
Commercial boundary to resolve
Separate help desk, NOC and security quotations. A supplier offering all three categories has not automatically committed to one seamless incident workflow. Ask who invoices, accepts tickets and owns changes in each service. We have not inferred detailed contract terms from marketing descriptions.
Qualification by scenario
| Your scenario | First question | Evidence to retain |
|---|---|---|
| Help desk | What identity checks precede a password reset? | Approved authentication steps and failure escalation |
| NOC | Which actions can occur without your approval? | Runbook version, authorized change list and audit trail |
| SOC seam | Who may contain an endpoint and notify the client? | Incident authority, communications owner and handoff test |
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
A real customer reference should match the selected service and time coverage. The material reviewed for this profile does not establish an independently verified service-specific interview. Ask for a recent MSP reference and distinguish project-delivery comments from recurring desk or NOC 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
Test the boundary between service queues before broad enrollment. Use an availability alert with a possible security cause and require a documented escalation, not parallel uncoordinated actions. A useful result identifies the next owner, remaining uncertainty and permitted customer communication. Retain timestamps and evidence even if no technical fix is possible in the test.
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.