Research dated 2026-09-05. Business value remains unmeasured. Software descriptions are documented capabilities; each project must verify fit, rights and outcomes before adoption.
United States research pilot; customer contracts, data-processing terms, security obligations and named customer authority require review.
What the evidence supports
O*NET describes computer user support specialists as diagnosing user problems, documenting resolutions and communicating with users; NIST incident-response guidance emphasizes preparation, detection/analysis, response and recovery with defined roles. These sources support supervised workflow assistance, not autonomous remediation or security authority.
[onet-support-specialists] [nist-ir-800-61r3]
Processes to test
Inbound support request triage and routing
Classify and summarize the submitted request, suggest queue/SLA metadata and surface missing context; do not infer severity, customer entitlement or authorization from incomplete text, and do not close a ticket without review.
- Measure
- Human minutes per correctly routed and acknowledged request, including review, rework and exceptions; misroutes, missed SLA risks and unsupported classifications.
- Reject the idea if
- Reject if review/rework and exception effort do not reduce net effort, or a critical severity, entitlement, privacy or SLA error reaches the customer workflow.
- Human authority
- Named service-desk lead owns severity, entitlement, customer communication and escalation decisions.
[onet-support-specialists] [halopsa-features] [freshservice-itsm] [repo-chatwoot] [repo-activepieces]
Incident evidence assembly and change-request preparation
Assemble approved ticket, timeline, logs and proposed runbook fields; identify missing evidence and draft a change record, but never diagnose conclusively, select a remediation, or execute a privileged/production change.
- Measure
- Human minutes per complete, approved incident/change packet, including reconciliation, review and exceptions; evidence gaps, unauthorized actions and change defects.
- Reject the idea if
- Reject if packet review does not reduce net effort, evidence provenance is incomplete, or any unapproved privileged or production action occurs.
- Human authority
- Incident commander and authorized customer/change approver own diagnosis, risk acceptance, rollback and production execution.
[nist-ir-800-61r3] [halopsa-features] [freshservice-itsm] [repo-plane] [repo-activepieces]
Customer onboarding and offboarding checklist coordination
Track approved checklist items, dependencies, evidence and reminders across systems; do not create accounts, grant/revoke access or attest completion without an authorized operator and customer record.
- Measure
- Human minutes per reconciled, authorized lifecycle event, including review and exception handling; missed approvals, stale access and incomplete evidence.
- Reject the idea if
- Reject if net coordination effort is not reduced or a stale, overbroad or unauthorized access change is made or left unreviewed.
- Human authority
- Named customer owner and authorized MSP operator own identity, access, data-retention and completion attestations.
[onet-support-specialists] [halopsa-features] [freshservice-itsm] [repo-plane] [repo-activepieces]
Monthly service review and SLA/reporting pack
Reconcile approved ticket, SLA, incident and change data and draft a traceable service report; do not infer causality, promise remediation or conceal missing/late data.
- Measure
- Human minutes per accepted report, including reconciliation, review and rework; missing/incorrect SLA fields and unsupported causal or risk claims.
- Reject the idea if
- Reject if reconciliation and review erase time reduction, material data is missing without disclosure, or an unsupported service/security claim reaches the customer.
- Human authority
- MSP service manager and customer approver own metric definitions, interpretation, commitments and risk decisions.
[onet-support-specialists] [halopsa-features] [freshservice-itsm] [repo-plane]
Existing software
HaloPSA
Vendor advertises PSA capabilities spanning service desk/ticketing, incident and change workflows, SLA handling, asset context and reporting for IT service providers.
No verified customer plan, seat cost, migration cost or avoidable spend; price and cancellation value remain unknown.
[halopsa-features]
Freshservice
Vendor describes IT service-management workflows for incidents, service requests, changes, assets and knowledge, with automation features subject to configured permissions and review.
No verified customer plan, adoption, configuration effort or avoidable spend; price and savings remain unknown.
[freshservice-itsm]
Reusable code candidates
makeplane/plane
Open-source work-item and project operations platform with triage and delivery primitives documented by the upstream project.
- Possible reuse
- Customer-approved backlog and change-preparation work items; preserve customer/project boundaries and require approval before any operational action.
- Limits
- Repository capability does not prove tenant isolation, customer authorization, SLA correctness, integration reliability or safe production-change execution.
- Rights
- Upstream license, distribution and trademark obligations require review before reuse; source evidence does not qualify a production deployment.
[repo-plane]
Revision: 5f7d92784c403f76284f0f16718f320221dc7fec
chatwoot/chatwoot
Shared inbox and customer-support conversation platform documented by the upstream project; useful for controlled customer communications around tickets and incidents.
- Possible reuse
- Route inbound customer messages into a reviewable queue and draft acknowledgements; require named approval for external sends and preserve channel identity.
- Limits
- Conversation features do not prove identity mapping, channel credential revocation, replay handling, customer consent or incident-resolution quality.
- Rights
- Upstream repository licensing and hosted/self-hosted route require review; customer communication authority remains outside the module.
[repo-chatwoot]
Revision: b354a9550e1fb59fa537a9c384232cb076213e72
activepieces/activepieces
Visual automation runtime with reusable connectors, triggers and actions documented by the upstream repository.
- Possible reuse
- Allowlisted ticket notifications, evidence collection and report synchronization with approval transitions, idempotency and dead-letter handling required.
- Limits
- Connectors do not prove customer consent, least privilege, retry safety, idempotency, tenant isolation or permission to make a production change.
- Rights
- Community and enterprise licensing boundaries require review; connector credentials must remain governed by the owning environment.
[repo-activepieces]
Revision: af374df8ae23f973376650f9b83642e2e7985bf3
Business value and a falsifiable pilot
No customer baseline, authorization, adoption, pricing or controlled-pilot data was available; missing data is not zero.
Paired, approval-gated pilot on matched support requests, incidents/changes, lifecycle events and service reports; compare incumbent workflow with the same evidence and record review, rework, exceptions, authority checks and correctness.
- net human effort is not reduced
- critical severity, evidence, privacy or authority error survives review
- unapproved privileged or production action occurs
- material report or SLA claim lacks provenance
Read the shared value modelLimits
- No MSP customer data, incumbent configuration, credentials, endpoint telemetry or production changes were accessed.
- Vendor pages and GitHub repositories establish stated capability only; they do not establish adoption, reliability, security qualification or measured savings.
- No pricing, labor rates, baseline volumes, cancellation evidence or controlled pilot exists, so all monetary value and capacity outcomes remain unmeasured.
- Tenant isolation, least privilege, retention, backup/restore, integration retries and customer-specific contractual obligations require separate verification.
Sources
- 15-1232.00 Computer User Support Specialists · O*NET OnLine
US occupational task and work-activity context; does not estimate MSP adoption, automation or savings.
- SP 800-61 Revision 3: Incident Response Recommendations and Considerations · National Institute of Standards and Technology
Incident-response roles and lifecycle guidance; not a license to automate diagnosis, authority or production changes and not a savings estimate.
- HaloPSA Features · HaloPSA
Vendor capability claims for PSA workflows; no independent adoption, quality, pricing or outcome evidence.
- Freshservice IT Service Management · Freshworks
Vendor capability claims for ITSM workflows; no independent adoption, quality, pricing or outcome evidence.
- makeplane/plane · GitHub / Plane
Pinned upstream repository evidence; licensing, deployment, upgrade, restore and tenant-boundary review remain required.
- chatwoot/chatwoot · GitHub / Chatwoot
Pinned upstream repository evidence; repository capability does not prove communication authority, isolation or operational outcomes.
- activepieces/activepieces · GitHub / Activepieces
Pinned upstream repository evidence; community/enterprise licensing and connector safety boundaries require review.