Skip to main content
Getting started

What is QuantumOps?

QuantumOps reads every HaloPSA ticket, analyzes it with AI and returns the results as dashboards, notes, alerts and a resolution plan; this page explains the loop and where you meet it.

Last updated 26 days ago

QuantumOps adds an AI analysis layer, a dispatch board and service-desk tools to your PSA: HaloPSA, Autotask or ConnectWise PSA. You keep working in your PSA. QuantumOps reads each ticket, scores it, suggests what to do next and shows the results where you already work.

How a ticket moves through QuantumOps

  1. Your PSA sends QuantumOps a notification when a ticket is created or changed. On HaloPSA these are signed notifications for a new ticket, an update, a closure and an end user's e-mail reply; on Autotask they are two webhooks, for tickets and for ticket notes; on ConnectWise PSA it is one callback. QuantumOps creates them in your PSA when the setup wizard finishes.
  2. QuantumOps analyzes the ticket with AI. The analysis produces a summary, sentiment and tonality, a category, research on likely causes and similar tickets, and suggested resolution paths. QuantumOps also gives each ticket a health score from its SLA state, age and activity; see How the health score is calculated.
  3. The results come back as dashboards, as notes you choose to write into your PSA, as alerts in the app, Slack and Teams, and as a resolution plan that you review before it runs.

How ticket analysis works lists what the analysis produces and why a ticket is sometimes skipped. What QuantumOps writes into HaloPSA lists every note and field it can add to a ticket. For Autotask and ConnectWise PSA, What works on each PSA says how that differs.

Where you meet QuantumOps

PlaceWhat you do there
The web appSign in to land on Home, the live list of analyzed tickets. The sidebar opens the hubs, reports and settings your role can use. See Finding your way around.
HaloPSA tabsOn HaloPSA only: dashboards embedded as tabs on HaloPSA tickets and clients, such as the Ticket Dashboard and Agent Assist. See Adding QuantumOps tabs to HaloPSA.
The browser extensionA side panel that follows the HaloPSA, Autotask or ConnectWise page you are on, and the dispatch board in its own tab. See The QuantumOps browser extension and, for Autotask and ConnectWise PSA, the extension on Autotask and ConnectWise.
Slack and TeamsQubit, the AI assistant, answers questions and posts alerts in chat. See Qubit in Slack and Teams.

What QuantumOps covers

AreaWhat it doesStart with
Ticket analysis and the resolution planScores each ticket, researches it, drafts replies and builds a resolution plan that you review and run.The Ticket Dashboard in HaloPSA
Dispatch and call handlingRanks the queue, raises pings for tickets that need attention and records calls as tickets.Opening the dispatch board
Call recordingsTranscribes and summarizes recordings and matches them to tickets.Call recordings
Identity verificationProves a caller is who they say before you act on a request.Identity verification
Q-NoticesAttaches notices to tickets, clients, users and agents and delivers them to chat.Q-Notices
Customer success and CSATRaises sentiment and stale-ticket alerts and collects satisfaction surveys.Customer Success Center
Q-MissionsGives agents missions, quests and bounties that pay in points or Zinc rewards, and tells them with cards on screen.Q-Missions overview
QBR StudioBuilds quarterly business reviews from real metrics with AI-written commentary.QBR Studio
ReportingShows agent performance and where AI spend goes.Agent Performance Hub
Timeclock and payrollTracks time, time off and pay runs.Clocking in and out
Chat with QubitAnswers questions about tickets, clients and your documentation.Chat with Qubit

Modules and roles

Two things decide what you can open. A module is a part of QuantumOps that your organization has turned on: an Administrator manages them in Module Management. A role says who may open each screen. Your Administrator assigns roles in Team Management. The Modules reference lists every module, and Roles and access lists every role and what it opens. Quick start by role lists the first screens to learn for each role.

What the AI is used for

The AI reads tickets and writes summaries, scores and categories. It researches likely causes, drafts replies, builds a resolution plan for you to review, and it answers questions in chat. By default Qubit looks things up without asking and asks before it runs anything that changes data. Your Administrator sets those rules in Tool Governance.

Your organization chooses which AI models do which jobs, and can use its own provider keys. See AI providers and models. AI work costs tokens, and AI Usage Analytics shows what was used and the estimated cost. AI processing can be paused and resumed from the Processing / Paused button in the header; see Pausing and resuming AI processing.

White-label partners

MSPs that serve white-label partners can link QuantumOps instances through white-label federation. The partner documentation is not public: it opens inside the app for the people allowed to read it.

Words used on this page, such as Q-Director, Sherlock and Autopilot, are explained in the Glossary.