Feature Ideas

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.

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

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

When entering data on some screens, you press the Escape key to efforts to close the pop up / overlay window but instead it closes out the entire series and takes you back to the parent screen.

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.

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.

I think this is one of those things that I spend a lot of time thinking about when I'm fumbling to set a time in a calendar invite. Click the time, set the hour. Drop down disappears. Click the time again, set the minute. Drop down disappears. Set AM/PM. Realize the time has changed on the appt's end time. Repeat the process again. The calendar's shared view is a mess. Viewing the same week for two techs requires a 40" wide screen and a lot of eye movement. Syncing back and fourth between Exchange happens either quickly (Halo>Exchange) or every 24 hours (Exchange>Halo) which effectively means that I can't use my Exchange calendar to make appointments that will show up at a reasonable time in Halo. I would love to see big refinement and simplification of this functionality. Many people on The Tech Tribe also share this feeling: https://portal.thetechtribe.com/community/topic/19349-loving-halo-what-are-you-feelings-about-the-calendar-function/#comment-164309

The "ESC" key will force close a current task at the worst times occasionally. When write a new ticket and when KB or canned text is suggested "ESC" key will close the entire action or ticket being worked. Add an option to disable the key activity or changing its functionality would be helpful for user experience.

When agents create a holiday calendar item, as we have requiring approval enabled, they must then manually click the holiday request, more options (three dots) and request approval. Holiday requests should automatically request approval if approvals is enabled for the holiday type.

We've had poor surveys resulting from a 3 strike rule type scenario where the end user has been unavailable for quite some time. We would like to ensure our agents have done everything possible to reach the end user so if they called the user from the ticket it would be good to record data such as call status (busy, answered, unanswered) and possibly the duration of the call. The current call on Microsoft Teams is flawed in that the note gets added to the ticket regardless of the outcome of the call. Teams asks for approval to make the call and it can be cancelled and still result in the note on the ticket saying a call took place.

We have a variety of non-profit clients that need to view their pre pay usage every month for accounting and auditing processes. Our last PSA (Autotask) natively supported this report and filtering capability in their customer portal. After migrating, that has now pushed a lot of work back onto our administration team.

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.

I know we can update logos for clients and for agent's but it would really be nice if we could update images for clients. There are so many times a field tech is trying to find an employee and a photo would help them out so much.

Have the ability to create Dashboard Only Agent for Interactive Displays Similar to API Agent.

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