Feature Ideas

A full functioning mobile app that doesn't require you to go to the browser version on your phone for 90% of your needs.

Every view is useful and that's why you added all these views. Unpaid invoices, sites & users for a client, etc. Why can't I export them? We all agree they are very useful and concise collections of business data, but we're limited to seeing 50 rows and we can't export it. It's useful! You know it's useful! You put it in the application! Let me have the data! Thanks

While the Azure subscription is detected, the integration is currently unable to retrieve key financial data such as pricing, cost, and sales figures. Request for Improvement: As more clients transition to Azure, it's essential to streamline the monthly billing process. To avoid manual adjustments, please enhance the integration so that Azure cost and sales data can be automatically pulled into Halo. This should support the creation and updating of invoice line items based on actual usage and pricing.

It would be great to get an upgrade to the ALSO integration. We could really like to see start/end date and cost/price fields beeing updated through the integration.

Ticket notes & draft emails, etc. should autosave to the tickets in case of a browser refresh or crash. If you had started writing notes and then refresh the ticket page then you should have a button or option to reload what you had last typed in there instead of needing to start over. I'm a new Halo user coming over from Syncro and this is the most basic feature that Syncro has and Halo is missing. I've lost a few draft ticket notes already but I'm sure many of you have lost many more. Ideally this would work in forms outside of the service desk as well, in the knowledge base, in the self-service portals, etc. All of those rich text and really any field should be autosaving while you type so if you refresh then you can click a button to get back what you had.

Would like the ability to map asset types in Ninja to asset types in Halo. For example, in Halo all our current assets and items are filtered where asset type is called workstation or server. However, Ninja brings servers across as Windows_Server. This means we have to go and update all our reports as well as all our items where the quanity is mapped to device name is server.

Could you please build a Microsoft Copilot Connector that allows interaction with all the data in Halo?

Would like to see an integration with Huntress. Amazing product and being able to receive tickets directly would be very useful.

Summary: Enable users to manually enter a start time and end time for ticket notes, and have HaloPSA automatically calculate the time spent based on those inputs — instead of relying solely on the live timer. Why This Matters: As a multitasking professional, I often work across multiple tickets simultaneously. The current timer-based system in HaloPSA is rigid and unintuitive for this workflow. There have been multiple instances where: The timer reset unexpectedly just as I was entering notes. I had to manually reconstruct time spent using timestamps from Teams, Outlook, and audit logs. This process is time-consuming and frustrating — especially for users who aren’t comfortable doing manual time calculations. Having to figure out the exact duration by checking timestamps across Teams, Outlook, and audit logs, then doing the math ourselves, adds unnecessary friction to what should be a simple task. Proposed Solution: Add a simple option in the time entry interface to: Manually input Start Time and End Time Let HaloPSA auto-calculate the duration Optionally allow users to override the calculated time if needed This would: Empower users to accurately log time without relying on the live timer Improve productivity and reduce frustration Support real-world multitasking workflows where time tracking isn’t linear Benefits: User autonomy: No more being a “slave to the timer” Accuracy: Time entries reflect actual work, not timer behavior Efficiency: Less time spent reconstructing work sessions Inclusivity: Supports users with different working styles and accessibility needs Who This Helps: MSPs and IT professionals juggling multiple tickets Admins and coordinators who document work after the fact Anyone who finds the current timer too controlling or unreliable HaloPSA is a powerful tool — but time tracking should work with users, not against them. This feature would be a game-changer for multitaskers.

When a category is not present Halo prompts to say there is not. You then clear the alert, add category and hit send again. Could the alerrt just come up with the category select field? Then the process is just select the category and hit send.

we use the Unifi Hardware stack for most of our networking as the controller for this is free and doesnt require a subscription. this controller uses standard Rest api to collect information. (www.ui.com) I have currently created a powershell based integration that collects all sites and hardware from the unifi controller and updates them via api in Halo. However, due to api throtteling this process is quite prone to error. It would be realy nice to have this as a proper integration. This api is Documented here: https://ubntwiki.com/products/software/unifi-controller/api

Currently, NinjaRMM remote sessions can only be launched from the asset screen, which slows down ticket handling. Adding the ability to initiate a NinjaRMM remote session directly from within a ticket would streamline workflows for technicians by reducing clicks, saving time, and ensuring faster response for end users. Other remote support integrations in HaloPSA already support ticket-based actions, so extending this functionality to NinjaRMM would create consistency and improve efficiency across platforms.

We heavily use to-do's as a way of creating checklists on common steps. However, a lot of our clients require unique custom checklists. We use IT Glue currently for this and it allows not only a to-do, but it allows that to-do to be expanded detailed steps (written in HTML). What I would like to see is the following To-dos have their own tab in tickets and not just a sidebar. To-do's can be expanded to show links or steps (See screenshot of Glue) To-dos once completed hide from the list To-do's that can be associated with a client site and be templated To-Do templates can be grouped

I'd love to see Halo automatically save drafts of notes/emails/etc when you're in a ticket (much like Office apps). Why? Let me take you on a short, but painful, journey. I was working a ticket for a good hour+, tons of notes in it documenting everything I was doing (disconnecting and deleting things)... and I accidentally closed the tab. I cried as I restored the tab and all my notes were gone, and I couldn't document them again as everything I documented was deleted from our system as I did it. I would love to see an auto save/draft feature that saves current notes and time entry like every X minutes. (either configurable or even something like every 5 minutes).

Just like using the @ in a ticket will bring up the ability to reference a user I would like to see similar ability to reference another ticket ie.. @ticket# or something like this which will make it a hyper link.