Short answer: HaloPSA is a flexible, highly configurable PSA that runs ticketing, contracts, billing and reporting for a large share of MSPs. Toolqit is AI-native and built for automation and speed. MSPs keep Halo as the system of record for contracts and billing, and their techs and operators work in Toolqit, which syncs two ways with HaloPSA (cloud or on-prem). Toolqit also replaces a lot of the tooling MSPs still pay for outside of Halo. The median tech gets 11.5 hours back a week.
Why do MSPs pick HaloPSA?
Halo earned its following. It is configurable down to the field, it handles ITIL-style workflows, contracts and billing well, and many MSPs moved to it for flexibility and a cleaner commercial relationship. Halo also lets you connect an AI provider to your instance for features like ticket matching and AI insights.
As configurable as Halo is, it was built as a rules-based system, and its AI features sit on top of that. Someone has to configure the rules, and most Halo shops we talk to have spent real hours on ticket types, rules and runbooks. Their techs still leave Halo all day to get the work done.
What does AI-native mean here?
Toolqit was designed around AI from day one. Triage, dispatch, research, replies, workflows, time entries and documentation all run through AI, so every step of a ticket is faster. We also built it to be a joyful experience that makes techs incredibly fast at their job.
What does a Halo ticket look like today?
A user writes in about Outlook asking for a password. The tech opens the ticket in Halo, checks email history for the same user, opens IT Glue or Hudu for the tenant details, signs into the Microsoft 365 admin center, checks the device in NinjaOne or Datto RMM, remotes in, fixes it, and comes back to Halo to write the note, the reply and the time entry. Halo recorded the ticket well. The tech did the work in six other places.
What does the same ticket look like in Toolqit?
The ticket lands triaged: ticket type, priority and the right tech are set from your own Halo history, with a summary and the user’s prior tickets linked. Toolqit has already checked the sign-in log, the device and the client’s docs, and the likely fix is on the ticket with a drafted reply.
The tech confirms the fix, launches the remote session from the ticket if needed, and presses resolve. The note, the documentation and the time entry are written and synced back to Halo. One tab, no logins, nothing reconstructed from memory at 5pm.
HaloPSA and Toolqit side by side
| HaloPSA | Toolqit | |
|---|---|---|
| Primary job | System of record: tickets, contracts, billing, reporting | Place of work for techs and operators |
| Setup effort | Highly configurable; rules and ticket types built by your team | Learns from your existing Halo tickets; onboarding in 30 to 45 minutes |
| Triage | Rules, plus AI features when you connect a provider | Set on arrival from your own history, summarized, prior tickets linked |
| Tools on the ticket | Integrations surface data inside Halo | RMM, docs, Microsoft 365, security and remote sessions worked from the ticket |
| Repeat work | Runbooks you configure | Workflows built from tickets you already solved; tech approves each run |
| Time and documentation | Entered by the tech | Logged as the work happens and written on resolve, synced to Halo |
| Projects | Halo projects | Native projects with two-way sync to Halo projects |
| Profitability | Halo reporting | Margin by client, technician and ticket on one screen |
| Tools outside the PSA | Separate subscriptions for dispatch, AI triage, automation and CSAT | Built into Toolqit |
Do I need to migrate off Halo?
No. You keep Halo, and nothing moves. Tickets, contacts, agreements, notes, time entries and statuses sync both ways, and Halo stays the source of truth for contracts and invoicing. If you run Halo on-prem, that works too. What changes is that your techs work in Toolqit.
What tools can Toolqit replace?
Most Halo shops pay for a few point solutions on top of the PSA: a dispatch or routing tool, an AI triage or service desk add-on, an automation platform for onboarding and offboarding, a CSAT tool. Toolqit covers that work in the same place techs solve tickets, so those subscriptions (and their logins) can go.
When is Halo alone enough?
If your techs are few, your ticket volume is low and most of your work happens inside Halo already, Halo on its own may be all you need. Toolqit pays off once techs are spending their day jumping between Halo, the RMM, documentation and the Microsoft 365 admin center. That is most MSPs with three or more techs.
FAQ
Does Toolqit work with HaloPSA on-prem?
Yes. Toolqit syncs two ways with both cloud and on-prem HaloPSA.
Will Toolqit change my Halo configuration?
No. Toolqit reads your ticket types, priorities and agreements and writes back into them. Your Halo setup stays yours.
Does Toolqit sync Halo projects?
Yes. Projects sync two ways with Halo, and teams can run projects natively in Toolqit with the same AI help they get on tickets.
What permissions does Toolqit need in Halo?
Least-privilege API access only. We send the permissions sheet before you connect anything.
How is Toolqit priced?
Per tech or per outcome, whichever creates the most value for your MSP. No setup or integration costs.
About Toolqit
Toolqit is the AI-native place of work for managed service providers (MSPs). It sits on top of an MSP’s PSA, RMM and Microsoft 365, syncs two ways with ConnectWise PSA, HaloPSA, Autotask and SyncroMSP, and gives technicians and operators one screen for triage, workflows, documentation, remote sessions and profitability. Toolqit, Inc. is based in San Francisco.
Sources: HaloPSA guide: Leveraging AI in Halo
#73291