CW Copilot: AI-assisted ticket resolution inside ConnectWise
ConnectWise Manage is where MSP tickets live. It's also where ticket quality degrades — terse notes, inconsistent time entries, missing resolution steps. When the senior tech who closed the ticket leaves, the knowledge leaves with them.
CW Copilot is an AI layer that lives inside ConnectWise and makes tickets better without changing the workflow.
What it does
Ticket summarizer One-paragraph summary of a ticket's full history: original request, steps taken, current status, blocking issues. Useful for:
- Picking up a ticket after context switching
- Handing off to another tech
- Client update emails (the summary is pre-formatted for that)
Time entry drafter Reads the ticket notes and generates a draft time entry: work type, labor hours (derived from timestamps), notes. The tech reviews and submits — they don't write it from scratch. Time entry quality improves; billing doesn't miss billable time because a tech forgot to log it.
Resolution suggester Searches the closed ticket history for similar tickets using keyword + category matching. Returns the top 3 with: original issue description, resolution steps, time to close, which tech closed it. The pattern: tech sees that the "Outlook not syncing" category has been resolved the same way 12 times this year.
Merge candidate detector Flags tickets that are likely duplicates: same caller, same category, opened within 4 hours, similar subject. The duplicate is marked; the tech merges or links rather than solving the same problem twice.
Escalation path suggester Rule-based escalation logic: priority 1 tickets auto-escalate after 30 minutes unacknowledged, enterprise clients escalate at tier 2, certain categories (data loss, security) go straight to tier 3. Returns a list of suggested escalation steps, not a mandate — the tech still decides.
Workload forecaster Per-engineer queue analysis: open tickets, estimated hours to close (derived from category averages), slack hours in the week. At-a-glance view of who's buried and who has capacity. Useful for managers during morning standup.
Ticket health score Per-ticket score from 0-100: notes completeness, time entry presence, SLA status, escalation risk, days open. Surfaces tickets that are quietly degrading before they become a client complaint.
Sentiment analyzer POSITIVE/NEUTRAL/NEGATIVE/CRITICAL classification on ticket text and notes. Churn risk flag when sentiment is consistently negative across multiple tickets from the same client. Legal threat detection (identifies language patterns associated with escalation to management).
Knowledge gap detector Flags categories where ticket volume is high but knowledge base coverage is low. "You're closing 8 tickets/week about Outlook issues but have zero KB articles for Outlook." The output is a list of suggested KB article topics, ranked by ticket frequency.
Change risk classifier ITIL change categories (standard/normal/emergency) from ticket description keywords. LOW/MEDIUM/HIGH/CRITICAL risk classification. Useful for change advisory board triage — the classifier flags the ticket; the human approves or overrides.
How it integrates
CW Copilot connects to ConnectWise Manage via the REST API. It reads tickets, members, companies, and time entries. It never writes without explicit confirmation — a tech clicks "Apply" on a time entry draft, or "Use this resolution" on a suggestion.
The read-only default matters. ConnectWise has real billing data attached to tickets. An AI that could write time entries or close tickets autonomously is a liability. CW Copilot surfaces suggestions; humans execute.
The integration runs as a ConnectWise Manage app (iframe panel). The tech opens a ticket, the Copilot panel loads alongside it, and the relevant features are auto-triggered: summary on open, similar tickets in the resolution section, escalation path in the escalation section.
Why inside ConnectWise, not alongside it
The context switch problem is real. If using the AI assistant requires opening a separate browser tab, techs don't use it. The tooling lives inside the workflow, not adjacent to it.
ConnectWise Manage's app framework allows iframe panels at the ticket level. CW Copilot uses this — it appears as a collapsible panel in the ticket view, not a separate window.
Test suite
473+ tests across all 10 modules. Every function is tested with injectable ConnectWise API mocks — no live CW access in CI. Coverage includes: pagination (ConnectWise returns max 1000 records/page), error handling (CW returns 400 on malformed queries, 401 on expired tokens), rate limiting (CW PSA enforces 250 requests/minute).
CW Copilot is in early access. Currently targeting MSPs running 10-50 technicians on ConnectWise Manage.