Integrations # AI for HaloPSA HaloPSA already holds your tickets, contracts, time and invoices. Connected to Control Center, it is where AI triages and routes tickets, where your team approves the work, and where every AI service you sell gets billed. - 20 automations - 3 standards - 10 reports - 11 MCP questions - 3 billing items ## Automations with HaloPSA Work that runs on its own, across your tools. A person approves the steps that matter. - ### Alerts become one ticket, with the fix attached NinjaOne alerts are grouped and duplicates dropped. One HaloPSA ticket opens with the device, the user and the fix from Hudu. With NinjaOne and Hudu - ### Threats triaged before a tech looks When Huntress flags a threat, a priority HaloPSA ticket opens with who uses the device and what it can reach. With Huntress - ### Isolation, approved from the ticket A tech approves from the HaloPSA ticket and Huntress isolates the device. Releasing it works the same way. With Huntress - ### Known fixes run when a tech approves For a repeat issue, the fix your team wrote in Hudu runs through NinjaOne, and the time lands on the HaloPSA ticket. With NinjaOne and Hudu - ### New hires set up from one request A request in HaloPSA creates the user in Microsoft 365 with the right groups and licenses, documents them in Hudu and closes the ticket. With Microsoft 365 and Hudu - ### Offboarding that misses nothing One HaloPSA ticket blocks sign-in in Microsoft 365, removes licenses and closes with a record of every step. With Microsoft 365 - ### Failed backups handled overnight When a Datto BCDR job fails, a HaloPSA ticket opens with the error, the last good backup and the device’s health from NinjaOne. With Datto BCDR and NinjaOne - ### Missed time entries caught daily Tickets with work but no time in HaloPSA are flagged to the tech each afternoon. - ### Every ticket triaged and routed New HaloPSA tickets are categorized, prioritized and routed, with the client’s business context attached. - ### Agreements and invoices reconciled HaloPSA agreements are checked against Xero invoices every month, and anything unbilled is flagged. With Xero - ### New clients onboarded on rails A new client in HaloPSA gets a checklist that tracks NinjaOne agents, Huntress coverage and Datto BCDR jobs until every device is done. With NinjaOne, Huntress and Datto BCDR - ### Full disks cleaned up before anyone calls When NinjaOne flags a disk filling up, the cleanup script your team approved runs. A HaloPSA ticket opens only if that doesn’t fix it. With NinjaOne - ### Failed patches retried, then explained Devices that fail patching in NinjaOne get another try in the next window. If one fails again, a HaloPSA ticket opens with the error and the device’s history. With NinjaOne - ### Software requests installed on approval A software request in HaloPSA installs through NinjaOne once a tech approves it, and the ticket closes with what was installed. With NinjaOne - ### Password resets handled from the ticket A reset request in HaloPSA is done in Microsoft 365 once a tech approves it, and the ticket closes itself. With Microsoft 365 - ### Risky sign-ins investigated A sign-in from an unusual country, or a burst of failed sign-ins in Microsoft 365, opens a HaloPSA ticket with the user’s recent activity. With Microsoft 365 - ### MFA gaps turned into tickets Users in Microsoft 365 without MFA open one HaloPSA ticket per client, with the list attached. With Microsoft 365 - ### Failed restore tests caught early When a Datto BCDR restore check fails, a HaloPSA ticket opens before anyone needs that backup. With Datto BCDR - ### QBR action items become tickets Every action item agreed in a QBR becomes a HaloPSA ticket or project, with an owner and a date. - ### Threats remediated on approval A tech approves remediation from the HaloPSA ticket, and Huntress cleans up the device. With Huntress ## Standards checked in HaloPSA Checked every morning, for every client. Fewer tickets, better security, and every gap is a project you can sell. - ### Every client on a current agreement Clients in HaloPSA with an expired or missing agreement. - ### Leavers fully removed Accounts in Microsoft 365 still enabled for people offboarded through HaloPSA. With Microsoft 365 - ### Tickets closed properly HaloPSA tickets closed without notes or time, by tech. For you, not the client. ## Reports from HaloPSA Numbers from your tools, in the client’s language. Build a report from any data you connect. - ### The whole QBR, drafted HaloPSA, NinjaOne, Huntress and Datto BCDR in one QBR, written in the client’s business terms for your vCIO to approve. With NinjaOne, Huntress and Datto BCDR - ### Service desk, in business terms Ticket volume, response times and repeat issues from HaloPSA, explained by what they cost the client. - ### Your margin on every client Hours in HaloPSA against revenue in Xero. For you, not the client. With Xero - ### Alerts and what they cost Alert volume from NinjaOne per client, with the HaloPSA time spent on them. For you, not the client. With NinjaOne - ### Response and resolution against your SLA From HaloPSA, per client and per priority. - ### Where the tickets come from Tickets from HaloPSA by person and by issue, so you fix the cause, not the symptom. - ### What AI did this month Every AI service’s runs, hours returned and value, ready for the client’s QBR. - ### Standards scorecard Every standard you check, passed or failed at each client, with each gap priced as a HaloPSA project. - ### A one-page monthly summary Tickets, devices, security and AI work from HaloPSA and NinjaOne, on one page for the client’s owner. With NinjaOne - ### Any report you can describe Describe it in a sentence. Control Center builds it from HaloPSA and your other connected tools, then sends it on a schedule. ## Ask about HaloPSA in Claude or ChatGPT Questions your team asks in Claude or ChatGPT, answered from every tool and client. Any answer can become a report or an automation. - ### “What did we do for Meridian this month?” Answered from HaloPSA and NinjaOne. - ### “Which clients have more licenses than we bill for?” Answered from Microsoft 365 and HaloPSA. - ### “Why does Harbor’s file server keep alerting?” Answered from NinjaOne alerts and HaloPSA history. - ### “What changed at Northbridge this week?” Answered from HaloPSA, NinjaOne and Huntress. - ### “Turn that into an automation.” Any answer can become a workflow, and a person approves it before it runs. - ### “Has this happened at Harbor before? What fixed it?” Answered from HaloPSA ticket history and Hudu. - ### “What’s left on Meridian’s onboarding?” Answered from HaloPSA and Hudu. - ### “What work did we do this month that we didn’t bill?” Answered from HaloPSA time entries and agreements. - ### “Which clients made us the least per hour this quarter?” Answered from HaloPSA and Xero. - ### “Whose agreement renews next quarter, and what should we add to it?” Answered from HaloPSA agreements and each client’s AI roadmap. - ### “Draft Northbridge’s QBR.” Built from HaloPSA, NinjaOne and every other connected tool, for your vCIO to edit. ## Billing with HaloPSA Get paid for the AI work, through the tools you bill with. - ### AI services on the HaloPSA agreement Every AI service you sell is added to the client’s agreement and billed each month, at your margin. - ### Licenses matched to what you bill Microsoft 365 licenses at every client against the HaloPSA agreement, with missed billing flagged. With Microsoft 365 - ### Every AI run metered Usage per client and per workflow, behind every line you bill. ## What Control Center reads from HaloPSA Tickets, agreements, billing and time entries. Control Center connects to HaloPSA through its public API. You add it once, then choose which clients it covers and which API operations it can use. The key goes in Control Center’s vault, never in a chat. What you need: An API application registered in HaloPSA (client ID and secret). Addresses are specific to your instance. The examples on this page use a stack MSPs often run with HaloPSA: NinjaOne, Hudu, Huntress, Microsoft 365, Datto BCDR and Xero. Build your AI plan to see them with your own tools. [Connection details and what you need from HaloPSA](https://www.resultsiq.ai/docs/tools/halo/) ## Questions about HaloPSA and Control Center ### Does Control Center work with HaloPSA? Yes. Control Center connects to HaloPSA through its public API and uses tickets, agreements, billing and time entries. You add it once, then choose which clients it covers. ### What can an MSP automate with HaloPSA and AI? With Control Center, 20 automations, including: alerts become one ticket, with the fix attached; threats triaged before a tech looks; isolation, approved from the ticket; known fixes run when a tech approves; new hires set up from one request; offboarding that misses nothing. A person approves the steps that matter. ### Can I use HaloPSA with Claude or ChatGPT? Yes, through Control Center MCP. Your team connects Claude or ChatGPT once and can ask about HaloPSA at every client, with the same roles and client scopes as their login. For example: “What did we do for Meridian this month?” ### What does it cost? $1,750 a month for the Control Center platform plus $75 a month per billable workflow, with the first 90 days at no cost.