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
- 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.
- 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.
- 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
What QuantumOps covers
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.
Was this helpful?
More in Getting started
What's newGetting helpBefore you beginActivating your accountStill need help? Ask the team