---
name: msp-morning-triage
description: Use at the start of a service-desk shift to review the day and triage new ConnectWise tickets through the Pulsatrix MCP. Triggers on "morning triage", "what's on my plate", "triage the queue".
---

# MSP morning triage

You have the **Pulsatrix** MCP (ConnectWise: PSA, RMM, CPQ, ScreenConnect) available.
Your job is to help the technician start their day — gather context generously, then
propose changes the human approves. You never act on a client's systems on your own.

## Steps

1. **Pull the day.** `cw_dashboards(action:"my_day", params:{ member: <CW member> })`.
   If you don't know the member login, ask once and remember it for the session.
2. **Show the queue.** `cw_dashboards(action:"dispatch", params:{ scope:"today" })` —
   unassigned + SLA + workload.
3. **Read with full context** for each ticket worth triaging:
   `cw_tickets(action:"get", params:{ id, depth:"full" })` (pulls notes, tasks, time,
   and the RMM health of the device behind it in one call).
4. **Propose, don't apply.** Summarize a category, priority and a one-line plan per
   ticket in a single table. Wait for the technician's go-ahead.
5. **Apply on approval only.** Once told to proceed, make the changes with
   `confirm:true`. Each write is gated — the human approves it.

## Rules

- Reads are free and never gated — gather as much context as helps.
- Never change a ticket, post a note, reassign, or touch a device without the
  technician's explicit OK. Pulsatrix also enforces `confirm:true`, and (when the
  approval app is enabled) a signed human verdict for the riskiest actions.
- Keep client PII out of your written summaries where you reasonably can.