[ 01 // quantumops ]
The AI service desk
layer for HaloPSA.
QuantumOps reads every ticket as it lands in Halo, drafts the triage with its reasoning, researches the fix and puts it in front of the tech: inside Halo, in a side panel, or in Slack and Teams. Dispatches, replies, merges and status changes wait for a person.
The QuantumOps for Halo side panel. The same analysis appears in the QuantumOps tabs inside HaloPSA tickets.
[ 02 // where it works ]
Wherever your team already is.
One QuantumOps instance, four ways in. The web app and the side panel’s restricted tabs follow each person’s role; the tabs inside HaloPSA show to anyone who can open them in Halo.
Inside HaloPSA
Tabs on tickets and clients
Ticket Analysis, Ticket Triage, Agent Assist and Client tabs sit in the Halo screens techs already have open, with the user’s profile one click away.
Browser extension
QuantumOps for Halo
A side panel for Chrome and Edge (Firefox in beta) that follows the tech from ticket to client to user to agent.
Web app
The hubs
Dispatch, Customer Success and CSAT, Agent Performance, QBRs, Q-Notices and AI usage, each in its own screen for the people who run the desk.
[ 03 // triage to resolution ]
Every ticket read, triaged and researched.
Halo tells your instance about every new ticket, update and customer email. QuantumOps summarizes it, scores its health, sentiment and tone, checks for duplicates and repeat problems, and researches it. Q-Director drafts the triage, and a dispatcher applies it in one click.
- Team, type, impact, urgency and routing, each with a “Why?”, a technician ranked by fit, and one confidence figure for the draft
- Technicians ranked by a 0–100 fit score: workload, skills, client familiarity, burnout risk
- Sherlock research across past tickets, ITGlue, Hudu and SharePoint docs, and the web
- Three to five resolution paths, walked step by step, with the reply drafted
- A second evaluation of every analysis, scored 0–100 for agreement
[ 04 // qubit and approvals ]
Ask Qubit. It answers from your own history.
Qubit opens from the ticket, the client or the guide already knowing the record, or from any screen of the web app. It starts from what the AI has learned about that client and user, looks up HaloPSA and your documentation while it answers, and takes files in and hands charts and documents back.
- Live, read-only HaloPSA lookups, with the tickets it used named by number
- Tools from StackJack (83+ MSP platforms, and counting), HaloPSA’s own MCP endpoint or any MCP server, under one policy gate
- Reads run and changes ask (once, for the conversation, or always), with every tool call audited
[ 05 // dispatch ]
See the whole queue. Hand it out in one move.
Every open ticket as a hex, the unassigned queue ranked by breach risk, and assignments written to HaloPSA before the board moves. Recommendations spot the breach nobody owns or the tech who is drowning, and hand you a plan to accept.
[ 06 // phones and identity ]
Know who’s calling.
Put the call on the right ticket.
Call Taking
Find the caller by phone or name, see every open ticket at their company, follow the script, and create or link the ticket with AI triage before you hang up.
Recordings and transcripts
Recordings your phone system already makes are transcribed, summarized with AssemblyAI, and posted to the matching Halo ticket. When the match isn’t certain, QuantumOps asks.
Caller verification
Before a password reset, the caller proves they control the Microsoft 365 account on the ticket, on their own phone. A mismatch is logged, never passed.
[ 07 // insights ]
Know which clients are drifting, and which techs need help.
Customer Success Center
Unhappy clients flagged from the tone of their tickets and from tickets gone quiet, with a survey or an outreach ticket one click away.
CSAT inside your Halo emails
Customers click a face in the email you already send; ratings post back to the ticket and feed a leaderboard.
Agent Performance Hub
Workload, quality and burnout risk per technician, with AI coaching profiles.
QBRs from Halo data
QBR Studio builds the deck and AI writes the commentary and recommendations. Present it, send a PDF or PowerPoint, or share an expiring link, which by default needs approval before it is published.
[ 08 // ai you control ]
Your AI, your models, your bill.
Run QuantumOps on AI we manage, or on your own Anthropic, OpenAI or Together AI keys. Either way you decide what each job costs.
Cost down to the ticket
Every AI call is priced when it happens. See spend by function and model, a month-end projection, a budget banner, and every call made for one ticket.
Keeps working when a model doesn’t
If a model or provider fails, QuantumOps falls back to another and tells you in Slack, Teams or email what to fix.
[ 09 // add-ons ]
Add what your business needs.
Six optional modules, licensed separately and off until you switch them on.
Add-on
Timeclock & Payroll
Clock-ins, PTO and a five-step payroll run on pay rules you set for each country, PDF paystubs and an accountant view.
Add-on
White Label Federation
Link your instance with partner MSPs’ instances to deliver or buy white-label support, with a credit ledger and a partner dashboard.
Add-on
Call recording and transcription
Recordings from your phone system transcribed and matched to the right HaloPSA ticket.
Add-on
QBR Studio
Quarterly business reviews written from your Halo data, ready before the meeting.
Add-on
CSAT and surveys
Ratings collected inside your Halo emails, posted to the ticket and rolled up by client and tech.
Add-on
Identity verification
Check a caller against their own Microsoft 365 account before anyone resets a password.
[ 10 // security ]
Your instance. Your keys. Your call.
Your own instance
Its own container, its own database and its own address, provisioned for you.
Encrypted secrets
Halo credentials and AI keys are encrypted with AES-256 under a key unique to your instance.
Roles and two-factor
Two-factor sign-in from day one, and 15 roles that decide who sees what.
[ 11 // pricing ]
Two ways to run it.
All-inclusive puts the AI on our bill and prices by tickets. Bring your own key puts it on yours and prices by agents. Pricing for both is to be announced.
QuantumOps
All-inclusive
AI included, priced by tickets a month.
TBA
Pricing will be published here. Until then, book a demo and we’ll walk you through it.
QuantumOps
Bring your own key
Your own AI keys, priced by agents.
TBA
Pricing will be published here. Until then, book a demo and we’ll walk you through it.
Do I need HaloPSA?
Yes. HaloPSA is the only PSA QuantumOps supports. If you’re still moving to Halo, we’re one of the original authorized onboarding partners, with 450+ implementations behind us.
Does Q-Director assign tickets by itself?
It drafts the triage (team, type, impact, urgency, routing and a technician) with its reasoning and a confidence figure. A dispatcher applies it with one click, changes it, merges the ticket or closes it as spam, and every override is recorded so managers can see where the AI and the desk disagree.
What does the AI write to Halo on its own?
In a few ways, and each is a setting. Q-Director keeps the Halo category (and the resolution category at closure) current, with a note each time; it is on for new instances and you can switch it off. With call recording, a call matched through a Call Taking session, or by the AI at 90% confidence or more, posts as a call log plus a transcript note hidden from end users, unless you turn auto-post off; other matches wait for a person to post them. With CSAT, each rating posts to the ticket as a note, private by default. Sherlock’s private research note, the guide’s path notes and Guided Work’s ticket colors reach Halo only if you switch them on. Dispatches, replies, merges and status changes wait for a person, and a tool that changes something asks first unless an admin allows it.
Which AI models does it use?
On Managed AI, Anthropic Claude models. On your own keys, also OpenAI and Together AI open models. Models come from a catalog we keep current and are assigned per role and per function. Embeddings and reranking come from Voyage AI.
How do we get started?
We provision your instance, you sign in with two-factor, and an 11-step setup wizard connects HaloPSA, sets up the AI, configures Q-Director and adds the tabs. An initial import indexes your Halo history, so matching and research start with context, and shows a cost estimate before it starts.
Is the browser extension available?
Yes. Techs install it from the Browser Extension page of their QuantumOps web app, and the store listings follow.
[ 13 // start ]
See Q-Director draft the triage on your queue.
Book a demo and bring your HaloPSA questions.