ConnectWise AI: What It Does Today, and the Record It Can't Read
Open a ConnectWise ticket where the fix happened on the phone. The initial description says "Outlook not syncing." There is one note from the dispatcher and a time entry that says "worked with user, resolved, 0.25." The actual work, the twelve minutes where the tech walked the user through rebuilding a profile and found the real cause was an expired mailbox license, lives in a call recording nobody will ever play back.
Now run any AI summary on that ticket. It can only tell you what the ticket already says. That is the most useful thing to understand about ConnectWise AI in 2026: the AI inside the PSA works on the PSA's record, and for most MSPs the record is thinnest exactly where the work is hardest.
What ConnectWise AI is today
"ConnectWise AI" covers two product lines from ConnectWise itself, plus the third-party tools that plug into ConnectWise PSA.
ConnectWise Sidekick is the AI assistant ConnectWise announced at IT Nation Connect in November 2023 (ConnectWise press release). Sidekick for PSA lists ticket summarization (written back to the ticket as a note), customer sentiment tracking, ticket translation, auto-triage, suggested resolutions from previous tickets, drafted customer emails, opportunity insights and a Microsoft Teams bot (Sidekick for PSA). Sidekick for Automate drafts scripts from plain-English requests, which a technician approves before they run.
ConnectWise AI Agents came after ConnectWise acquired zofiQ, an agentic AI company, in January 2026 (RCP Channel Briefing). ConnectWise describes them as agents built into PSA workflows on the ConnectWise Platform (What's new in ConnectWise PSA). Outside write-ups describe four: a service desk agent, a triage agent, a data analyst agent and an oversight agent.
Third-party AI connects to ConnectWise PSA through its REST API and usually shows up as a pod on the ticket screen. That includes tools for triage, call documentation, ticket chat and reporting, Vight among them.
ConnectWise does not publish Sidekick or AI Agents pricing on those pages. You get it from sales.
What the native AI is good at
Sidekick and the AI Agents start from data ConnectWise already holds: ticket text, notes, statuses, boards, companies, agreements and history. That makes them a good fit for jobs where the answer is already in the PSA:
- Triage on written tickets. An emailed or portal ticket has its whole request in the description. Classifying it by board, type and priority is a reading job, and the PSA has the history to learn from.
- Summaries of long ticket threads. A ticket with forty notes across three techs is hard to pick up. A summary of what is written saves real time.
- Drafting customer replies from the ticket's own notes, which a technician reviews before sending.
- Questions over PSA data, the job the data analyst agent is aimed at.
If your tickets mostly arrive by email and your techs write thorough notes, the native tools are working with good input.
What it can't see
The ticket is not where most of the work gets recorded. Three things happen outside it:
- Phone calls. A client call is often the intake, the troubleshooting and the fix in one. Unless the tech writes it up afterward, the PSA never learns what was said. Your phone system (3CX, Teams, RingCentral, Zoom Phone and the rest) has the recording; ConnectWise does not.
- Remote sessions. The RMM or remote tool knows a session happened. It does not know what the tech changed.
- The time itself. A time entry is whatever the tech typed when they got to it. On a busy day that is a round number at the end of the shift, or nothing.
So an AI that summarizes the ticket summarizes the tech's memory. An AI that suggests a resolution from "previous tickets" learns from notes like "resolved, 0.25." Triage on a ticket a dispatcher opened from a call reads two lines, not the ten minutes of detail the caller gave. We dig into that last one in ticket triage for MSPs.
This is not a knock on ConnectWise. No PSA records phone calls, and any AI that reads only the PSA has the same ceiling. The question is whether you are buying AI that reads the record, or AI that writes it.
Two kinds of ConnectWise AI: readers and writers
It helps to sort every ConnectWise AI tool, native or not, into one of two jobs.
Readers work on what is already in ConnectWise: summarize, classify, translate, route, answer questions, suggest. They are only as good as the notes, and they make no new record of the work.
Writers put new information into ConnectWise: a note from a call transcript, a time entry from the call or session length, a ticket opened from an after-hours call, a corrected title or category. They raise the quality of everything downstream, including every reader you run later.
Most MSPs buy readers first, because summaries and triage demo well. If your notes are thin, the writer is the better first purchase. A reader on a better record is worth more than a smarter reader on the same thin one.
The security role is the real spec sheet
Every tool that touches ConnectWise PSA through the API does it as an API member with a security role. That role tells you more about what the tool actually does than its feature page, so ask for it before the demo, not after.
Here is what the common capabilities need. ConnectWise calls the levels Add, Edit, Delete and Inquire.
| If the tool claims to... | It needs, at minimum |
|---|---|
| Read tickets and match calls to them | Service Desk > Service Tickets: Inquire |
| Post notes on a ticket | Service Tickets: Edit (ConnectWise checks Edit, not Add, for notes) |
| Create tickets | Service Tickets: Add |
| Change title, type or status | Service Tickets: Edit |
| Log time entries | Time & Expense > Time Entry: Add |
| Log time on a ticket that is already closed | Close Service Tickets: Edit, to reopen and re-close it |
| Know which member a call or entry belongs to | System > Member Maintenance: Inquire |
| Read devices for a ticket | Companies > Configurations: Inquire |
What to look for:
- A vendor that asks for an admin role has not worked out what it needs. Ask them to list modules and levels.
- A tool that claims to write but asks for Inquire only writes nothing. It will show you a note and leave you to paste it.
- Edit on Service Tickets is broad. It covers notes, fields and status in one permission, so ask what the tool changes and whether every change is logged.
When the role is wrong, the failure is not obvious. ConnectWise answers a refused request with a generic security error that does not name the missing permission, so a tool that "posts notes" can quietly fail on one board and work on the next. Ask the vendor how they surface those failures. We keep our own per-module list in the ConnectWise integration setup so you can check it line by line.
Five failure points to test before you trust it
These are where AI writing into ConnectWise goes wrong in practice. Test each on a sandbox board or a single tech before you roll it out.
- Notes that email the customer. ConnectWise emails a note to whoever the ticket's Send Notes as Email boxes (contact, resources, Cc) say. An AI that posts a detailed call summary as a discussion note can send it to the client. Ask how the tool decides internal versus customer-facing, and post one test note to see what happens.
- Time on the wrong member. A time entry needs the exact ConnectWise member. If the tool maps your techs by name or email and one is off, their time lands on someone else or fails.
- Work types that do not fit the board. Each board has its own valid work types. An entry with a work type that is inactive or not allowed on that board is refused.
- Rounding. ConnectWise can round actual hours to the increment set in your system (six or fifteen minutes, for example), so the hours on the entry may not match the minutes on the call. Check that what the tool writes matches your billing increment policy.
- Closed tickets. A call that comes in after a ticket closes still needs its time logged. Ask what the tool does: skip it, open a new ticket, or reopen and re-close the original.
Where Vight fits
Vight is a writer first. It pulls each recorded call from your phone system, transcribes it, matches it to the client and ticket in ConnectWise, posts a summary of the issue, steps and resolution as a note, and logs a time entry for the time worked. In the ConnectWise pod, technicians see the calls linked to a ticket, play recordings, link an unlinked call in one click, and ask questions about the ticket. Ticket agents rewrite vague titles, categorize, merge duplicates, and flag negative sentiment and P1 incidents.
It works next to Sidekick and the AI Agents rather than replacing them. If you run ConnectWise's own triage or summaries, they get a better ticket to read. Vight is also listed on the ConnectWise Marketplace. More on the rest of the stack in AI for MSPs.
Common questions about ConnectWise AI
Does ConnectWise have built-in AI? Yes. ConnectWise Sidekick has been available since late 2023 and covers summaries, sentiment, translation, triage, suggested resolutions and drafted emails in PSA, plus script generation in Automate. ConnectWise AI Agents, built after the January 2026 zofiQ acquisition, add agents for the service desk, triage, data questions and oversight.
How much does ConnectWise Sidekick cost? ConnectWise does not list a price on its Sidekick or AI Agents pages. Pricing comes through ConnectWise sales.
Can ConnectWise AI document phone calls? Not from what ConnectWise lists for Sidekick for PSA, which works on ticket data and email. Calls live in your phone system. To get them into the ticket you need a tool that pulls recordings from the phone system and writes notes and time entries into ConnectWise.
Can ChatGPT or Claude connect to ConnectWise? Not natively. They reach ConnectWise through a connector, from community-built MCP servers to vendor ones. Vight's MCP connector lets Claude, ChatGPT and Microsoft Copilot search your calls and ConnectWise tickets, read only, limited to what each person can already see in Vight.
What permissions does an AI tool need in ConnectWise? At least Service Tickets: Inquire to read tickets. Posting notes and changing fields need Service Tickets: Edit, creating tickets needs Add, and logging time needs Time Entry: Add. A tool that asks for an admin role without listing modules should explain why.
Should I start with triage or documentation? Start with whichever fixes your weakest input. If most tickets arrive as phone calls, documentation comes first, because triage and summaries can only read what was written down. A week of your phone log next to your ConnectWise time entries will show you which it is. Our phone-to-PSA gap check walks through it.
See it on your own tickets
The fastest way to judge any ConnectWise AI is on your own tickets, not a demo board. If you want to see what your calls look like written into ConnectWise as notes and time entries, book a demo and bring a ticket that was worked on the phone.