Connect your documentation. Connect your helpdesk.

Knowledge sources flow in. Source-cited resolutions flow out, inside the ticketing tools your team already uses.

Platform shape

Knowledge in. Resolutions out.

Inbound: knowledge sources

Resolution engine

rc> resolve --ticket [n]

read context

match across sources

cite every step

deliver structured

HIGH CONFIDENCE

Outbound: ticket surfaces

Find your stack

Five common shapes. Pick the closest one.

If your stack matches one of these, jump straight to the right setup guide.

MSP, multi-tenant IT: IT Glue or Hudu for client documentation. ConnectWise, HaloPSA, or Autotask for ticketing. Per-client resolution scoping; junior-tech onboarding from day one.; For MSPs →
Internal IT, M365 shop: SharePoint sites and Drive for runbooks. Zendesk for helpdesk; Microsoft Teams for shadow-helpdesk capture (Q2 2026). Microsoft Graph permission boundaries respected.; For IT Teams →
Internal IT, Atlassian shop: Confluence spaces, no Jira Service Management required. Zendesk or the web app for delivery. Space-scoped sync; page-level citations in every ticket.; For IT Teams →
B2B SaaS support: Confluence and Drive for engineering and support SOPs. Zendesk for tickets. Agent-side resolutions; the customer never sees the AI.; For Support →
Mixed, multi-source: Any combination of sources, any surface. Acquired teams on different doc systems? PE rollups stitching IT Glue and Hudu together? ResolvCmd reads all connected sources at once and cites the most relevant. See the multi-source matching section below.; View pricing →

Other verticals on the roadmap: DevOps and SRE, Legal Ops.

Inbound

Knowledge Sources

Connect the documentation your team already maintains. Sync runs every 15 minutes; new and updated docs are indexed automatically.

IT Glue

Flexible Articles, Documents, Configurations. Org-level metadata preserved on every cited source.

Hudu

Articles, procedures, asset and configuration data. Company tags carried into resolutions.

Confluence

Cloud spaces and pages via OAuth. Connect specific spaces or your entire instance. No Jira required.

SharePoint

Modern pages, classic wikis, and document libraries via Microsoft Graph plus OAuth.

Google Drive

Google Docs, PDFs, DOCX, Markdown, plain text. Folder structure used for client tagging.

Upload

Document Upload

Drag-and-drop PDF, DOCX, MD, TXT, or ZIP. No integration required.

Outbound

Ticket Surfaces

Resolutions appear inside the tools your team already works in. No context switching, no separate window.

Zendesk

Sidebar app via Zendesk Marketplace. Reads ticket context automatically; resolution appears inline.

ConnectWise

Pod inside the PSA ticket pane. Multi-source matching across IT Glue, Hudu, Confluence, Drive.

HaloPSA

REST API integration. Customer-scoped resolutions across your external doc sources.

Autotask

Beyond Workflow Rules. AI-driven resolution from IT Glue, Hudu, Confluence, Drive.

rc>

Web App

Always available at my.resolvcmd.com. Direct query interface for any team member, any time.

Microsoft Teams

Capture the IT questions that never reach a ticket. Answer from your docs. Surface coverage gaps.

Coming Q2 2026 →

Multi-source

One ticket. Multiple sources, cited inline.

ResolvCmd reads from every connected source at once. A single resolution can pull from an IT Glue Flexible Article, a Hudu procedure, a Confluence runbook, and a Drive PDF. Each step is cited; ranking is per-step, not per-source. Most AI helpdesk tools index one knowledge base and stop. Multi-source matching is how you get accurate resolutions when your knowledge is spread across the systems your team actually uses.

No re-platforming

Keep IT Glue, Hudu, Confluence, Drive, and SharePoint where they live. Connect, do not migrate.

Per-step citation

Each step in a resolution links back to the specific Flexible Article, procedure, page, or file it came from.

Conflict surfacing

When sources disagree, Knowledge Studio flags the conflict so your team can pick a canonical answer.

First resolution in under 10 minutes

Connect your docs. Connect your ticketing system. Start resolving.

View Pricing