[ 01 // built by an msp, for msps ]
Every ticket triaged.
Every invoice billed.
QuantumOps reads every HaloPSA ticket as it lands, drafts the triage and researches the fix. BillingBot turns distributor invoices into HaloPSA or Autotask billing. Built by an MSP, for MSPs.
Ticket triageQ-Director[ 02 // two products ]
Two products. Built for the PSA you run.
Run one or both. BillingBot bills through HaloPSA or Autotask. QuantumOps runs on HaloPSA today, with Autotask and ConnectWise PSA on the way.
QuantumOps
The AI service desk layer for HaloPSA.
QuantumOps reads each ticket, explains its triage, researches the fix and puts it in front of the tech, in Halo, in a browser side panel or in Slack and Teams. Dispatches, replies, merges and status changes wait for a person’s yes.
- Q-Director triage with reasoning and a confidence score
- Sherlock research across your tickets, docs and the web
- Qubit, the assistant that answers from your own history
- Dispatch, phones, CSAT, QBRs and agent coaching
- AI included, or run it on your own keys
- StackJack built in: 83+ MSP platforms, and counting
- Autotask and ConnectWise PSA support on the way
Pricing TBA
BillingBot
Distributor invoices, straight into your PSA’s billing.
BillingBot reads the invoices your distributors actually send, prorates and arrears included, and bills them through HaloPSA or Autotask. On Halo, the lines arrive coded for QuickBooks Online or Xero. Most MSPs are live within hours.
- Bills through HaloPSA or Autotask
- Pax8, Ingram Micro, D&H, ITCloud.ca and Twilio
- Any other vendor by CSV import
- New, appended or recurring invoices, your choice per client
- New SKUs created in Halo for you
- Unlimited users
$99/mo · 7-day free trial
[ 03 // what’s new ]
QuantumOps grew up.
It started as a set of HaloPSA dashboards. Now it is the layer your whole desk works in.
A side panel that follows the tech
QuantumOps for Halo, for Chrome and Edge with Firefox in beta: the ticket, the triage, the guide, the caller and Qubit next to whatever Halo page is open.
Reads run. Changes ask.
Dispatches, replies and merges wait for a person, and Copilot suggestions wait for a verified tech. For Qubit’s tools, admins decide what runs, what asks and what never runs.
A dispatch command center
Every open ticket on one board, the queue ranked by breach risk, and assignments written to Halo before the board moves.
Phones on the right ticket
Call Taking, recordings transcribed and matched to the Halo ticket, and caller verification against their own Microsoft 365 account.
Insights leadership uses
The Customer Success Center and CSAT inside your Halo emails, the Agent Performance Hub and QBRs written from Halo data.
[ 04 // how it works ]
Plug in once. Q-Director drafts, a person decides.
01
Connect your Halo
An 11-step setup wizard, saved as you go, connects your own QuantumOps instance to HaloPSA with signed webhooks, adds the QuantumOps tabs to tickets and clients, and imports your ticket history with a cost estimate first.
02
Pick your AI
Run on the AI we manage, or bring your own Anthropic, OpenAI or Together AI keys. Choose the model for each job and set a monthly AI budget, and a banner warns you when the month-end projection is on course to pass it.
03
Work the queue together
Every new ticket is summarized, triaged with its reasoning and researched. A dispatcher applies the recommendation in one click, and overrides are recorded for review.
[ 05 // built for your role ]
Built for every seat in the shop.
Service managers
Stop hand-sorting the queue.
Q-Director drafts team, type, urgency and technician on arrival. The dispatch board shows who can take the next ticket.
Technicians
Answers without leaving Halo.
The summary, Sherlock’s research, a guided fix and Qubit sit next to the ticket, with the reply already drafted.
Owners
See the whole shop at once.
Which clients are drifting, which techs are overloaded, and a QBR ready before the meeting.
Finance
Month-end without the spreadsheet.
BillingBot bills distributor invoices through HaloPSA. The payroll add-on runs clock-ins through to paystubs.
[ 06 // integrations ]
Masters of middleware.
HaloPSA in the middle. Your AI, docs, phones and distributors around it.
The center
HaloPSA
Everything we build lands in HaloPSA, in every Halo hosting region, custom domains included. We’ve run 450+ Halo implementations, so the plumbing is familiar. BillingBot also bills through Autotask, and QuantumOps support for Autotask and ConnectWise PSA is on the way.
AI models · QuantumOps
Documentation · QuantumOps
Chat and alerts · QuantumOps
Phones and speech · QuantumOps
Identity · QuantumOps
Tools · QuantumOps
Distributors · BillingBot
Accounting, via Halo · BillingBot
[ 07 // pricing ]
Prices on the page.
No sales pitch required.
QuantumOps comes two ways: AI included, or on your own keys. Pricing for both is to be announced. BillingBot is one flat price.
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 Anthropic, OpenAI or Together AI keys, priced by agents.
TBA
Pricing will be published here. Until then, book a demo and we’ll walk you through it.
BillingBot
One plan
One price, unlimited users.
| Monthly | $99/mo |
| Yearly | $999/yr |
| Free trial | 7 days |
[ 08 // security ]
Your instance. Your keys. Your call.
The short version. The long one is on the security page.
Independently audited
SOC 2 Type II certified.
An independent auditor tested how TechPulse protects customer data over a period of months, not on a single day. The details are in our Trust Center.
Your own instance
Every MSP gets its own QuantumOps instance: its own container, its own database, its own address.
Encrypted keys
Halo credentials, AI keys, Slack and Teams secrets and tool-server tokens are encrypted with AES-256 under a key unique to your instance.
Signed traffic only
HaloPSA webhooks are rejected unless their HMAC-SHA256 signature checks out.
Two-factor and roles
Two-factor sign-in from day one, and 15 roles that decide who sees which dashboards and tools.
A person decides
Dispatches, replies, merges and status changes wait for a person. On the Halo tabs, Copilot suggestions also need a technician verified by email code; in the side panel, a tech linked to their Halo agent. Each approval is recorded under their name.
Your AI, your rules
Run on your own AI keys if you prefer, choose the models, see the cost of every AI call, or pause AI processing of new tickets with one switch.
Do I need HaloPSA?
Yes. QuantumOps runs alongside HaloPSA, and BillingBot bills through it. If you’re still moving to Halo, we’re one of the original authorized onboarding partners, with 450+ implementations behind us.
Does the AI change tickets 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 QuantumOps use?
On Managed AI, Anthropic Claude models. On your own keys, also OpenAI and Together AI open models such as Llama, Qwen and DeepSeek. You pick the model for each job from a catalog we keep current, and embeddings and reranking come from Voyage AI.
Where does our data live?
In your own QuantumOps instance and database on Microsoft Azure in the US. Ticket text also reaches the AI provider doing each job, Voyage AI for search and a US search index; the security page lists every service. The credentials you give us are encrypted with a key unique to your instance.
How long does BillingBot take to set up?
Most MSPs are fully up and running within hours: connect Halo, authenticate your distributors, map your clients and set your billing rules.
Is there a QuantumOps trial?
Trial terms are to be announced. Book a demo and we’ll walk through QuantumOps on a real HaloPSA queue.
[ 10 // built by an msp ]
Born in the bayou. Forged in the cloud.
TechPulse started in 2009 as an MSP in Louisiana, and it still runs one. Everything we build is used on our own desk first: BillingBot began as a PowerShell tool for our own Pax8 invoices.
The team works out of Youngsville, Louisiana and Medellín, Colombia.
2009
Founded as a Louisiana MSP
450+
HaloPSA implementations
2
Offices: Youngsville and Medellín
[ 11 // start ]
Let’s talk shop.
No sales pitch required. Bring your Halo questions.