ConnectWise has been building AI into its platform under the Sidekick brand. If you’re a ConnectWise PSA shop, you’ve probably seen the features rolling out — ticket categorization, priority assignment, response drafting, and triage automation. These features are useful. They solve real problems with ticket intake and routing.

But there’s a question that comes up once you start using Sidekick: where are my SOPs? The documentation your team has spent years building in IT Glue, Hudu, or Confluence doesn’t factor into Sidekick’s suggestions. It drafts responses and categorizes tickets based on its AI model and your ticket history. It doesn’t pull your documented procedures into the resolution.

This post compares ConnectWise Sidekick’s approach with documentation-driven resolution tools, and helps you figure out which problem you’re actually trying to solve. For a quick side-by-side, see our structured ConnectWise Sidekick comparison.

What ConnectWise Sidekick does well

ConnectWise Sidekick handles ticket intake and triage tasks that eat up dispatcher and technician time. Here’s what it does and where it genuinely adds value.

Ticket categorization and priority assignment. Sidekick reads incoming tickets and automatically assigns category, subcategory, priority, and other fields based on the content. For MSPs processing hundreds of tickets per day, this eliminates manual triage work that dispatchers currently handle. The categorization improves over time as it learns from your ticket history.

Response drafting. Sidekick generates draft responses for tickets based on the ticket content and your historical responses to similar tickets. Technicians can review, edit, and send rather than writing from scratch. This speeds up the communication side of ticket handling.

Ticket summarization. For tickets with long email threads or multiple updates, Sidekick produces a summary so technicians picking up a ticket mid-conversation can get up to speed quickly. This is particularly helpful for escalated tickets where the L2 tech needs context on what L1 already tried.

ConnectWise-native. Sidekick works inside the ConnectWise interface. No separate tab, no additional login, no middleware to configure. If you’re already living in ConnectWise, the AI features appear where you already work.

These are real productivity gains. Ticket triage alone can save a full-time dispatcher 2-3 hours per day on a busy helpdesk. Response drafting reduces the per-ticket writing burden. Summarization cuts onboarding time when tickets change hands.

Where Sidekick falls short

Sidekick’s limitations become clear when you look at what happens after triage — when a technician actually needs to resolve the issue.

No external documentation connection. Sidekick doesn’t connect to IT Glue, Hudu, Confluence, or any external documentation platform. It can’t pull your SOPs, runbooks, or client-specific procedures into the ticket. If your team has spent years building documentation in IT Glue, Sidekick can’t access any of it.

Response drafting isn’t resolution. Drafting a response to a customer is a different task than resolving a technical issue. Sidekick can help write “We’re looking into the backup failure and will update you within the hour.” It can’t produce “Here are the 6 steps to remediate a Veeam error 4096 on Acme Corp’s DC01 server using their specific backup configuration.” The first is communication. The second is resolution.

Historical patterns, not documented procedures. Sidekick learns from your ticket history. This means its suggestions reflect how your team has resolved tickets in the past — including the times they took shortcuts, skipped steps, or resolved things differently than the documented procedure specifies. If three technicians resolved the same issue three different ways, Sidekick has three conflicting patterns to draw from.

No source citations. When Sidekick suggests a response or action, there’s no link to a source document. The technician can’t verify where the suggestion came from or check it against an authoritative procedure. For routine tickets, this might not matter. For complex changes or client-specific procedures where getting it wrong has consequences, verifiability is important.

The documentation gap: your SOPs live in IT Glue, not ConnectWise

This is the core architectural issue. Most ConnectWise MSPs store their documentation in a separate platform — usually IT Glue (which, like ConnectWise, is owned by Kaseya) or Hudu. The detailed, client-specific procedures that technicians need to resolve tickets live in these documentation platforms, not in ConnectWise’s ticket history.

IT Glue and ConnectWise do have an integration. IT Glue embeds inside ConnectWise tickets, showing related configurations and documentation links for the relevant client. This is useful, but it’s a sidebar reference — it shows what’s available, not what to do. The technician still needs to click through, find the right article, read it, and mentally translate it into resolution steps.

Sidekick doesn’t use the IT Glue sidebar data. It operates on the ticket content and ConnectWise’s internal data. So you end up with two parallel AI-adjacent systems in the same interface: Sidekick suggesting actions based on ticket history, and IT Glue showing documentation that may or may not relate to those suggestions. Neither one produces a structured, step-by-step resolution drawn from your actual SOPs.

For Hudu and Confluence users, the situation is worse. There’s no sidebar integration at all. Documentation lives in a completely separate system, and Sidekick has zero visibility into it.

Resolution engines: a different approach to the same problem

Resolution engines like ResolvCmd start from a different premise. Instead of helping with triage and communication, they focus on the resolution step — connecting your documentation to your tickets and delivering actionable procedures.

A resolution engine connects to your documentation platform (IT Glue, Hudu, Confluence, Google Drive) through its API. It indexes your SOPs, runbooks, configurations, and procedures. When a ticket arrives in ConnectWise, it reads the ticket, identifies the issue and client, searches your documentation for matching procedures, and delivers structured resolution steps inside the ticket.

For a monitoring alert about a backup failure, the resolution engine doesn’t draft a response to the customer. It produces: “Here’s how to fix this, based on your documented procedures for this client’s backup environment, with links to each source document.”

The difference is the knowledge source. Sidekick draws from your ticket history and a general AI model. A resolution engine draws from your documentation — the procedures your team wrote, verified, and maintains.

Feature comparison

Who should use which tool

These tools aren’t direct competitors. They solve different parts of the ticket lifecycle.

Use Sidekick when your main bottleneck is triage and communication. If your dispatchers spend hours categorizing and routing tickets, and your technicians spend significant time writing responses, Sidekick addresses those problems directly. It’s also the path of least resistance if you’re already on ConnectWise and want AI features without adding another vendor.

Use a resolution engine when your main bottleneck is finding and applying documented procedures. If your team has good documentation in IT Glue or Hudu but technicians aren’t using it consistently — because searching takes too long, because they forget it exists, because they’d rather ask a colleague — a resolution engine delivers that documentation into the ticket automatically.

Use both when triage and resolution are both bottlenecks. Sidekick handles the front end of the ticket lifecycle (categorize, prioritize, route, draft initial response). A resolution engine handles the middle (find the right procedure, deliver it to the technician). These tools can coexist because they operate on different parts of the workflow.

The mistake to avoid is expecting Sidekick to solve the documentation delivery problem. It wasn’t built for that. It’s a triage and communication tool, and it’s decent at those jobs. But if your technicians are spending 10-15 minutes per ticket searching IT Glue for the right SOP, Sidekick’s ticket categorization won’t help.

The bottom line

ConnectWise Sidekick is a solid triage and communication tool that works well inside the ConnectWise ecosystem. It reduces the manual work around ticket intake, categorization, and response writing. For MSPs with heavy ticket volume and dispatcher bottlenecks, it delivers real value.

It does not connect to your documentation platforms. It does not deliver your SOPs as structured resolutions. It does not cite sources. These aren’t flaws — they’re scope boundaries. Sidekick was built to help with triage, not resolution.

If your documentation investment in IT Glue, Hudu, or Confluence is supposed to be the backbone of your service delivery, you need a tool that actually uses it. Sidekick and resolution engines can work side by side — one handles the front of the ticket lifecycle, the other handles the middle. The key is knowing which problem each tool solves and not expecting one to do both.