Feature Ideas

In the settings screen it is currently only possible to search settings for a /section/ (i.e. 'integrator'). Given the vast complexity of the HALO product and the fact that a great number of settings that might be considered related are not actually grouped together, the organic way in which settings are added, and the typically very lacking documentation, please make it possible to search the actual setting 'labels' and descriptions. i.e. I should be able to search for "new user" and at least be able to click through to the exact location of, if not see the current state of, all the setting options with the string "new user" in their title or in-line help text

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

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

Our HaloPSA instance currently has many imported phone numbers (for sites and users) that contain no formatting and are pretty hard to read as a result. This proposed auto-formatting feature would allow for phone numbers to be automatically cleaned up to conform to a specified format when displayed. For example, "1234567890" would become "(123) 456-7890". Additionally, it looks like HaloPSA stores phone numbers as text (strings) rather than as an actual numbers (integers). Instead of storing phone numbers as text, perhaps HaloPSA could automatically take formatted phone numbers and convert them to raw format-less numbers/integers. This would improve data-efficiency & would standardize the format in which phone numbers are stored. This would make it significantly easier for an auto-formatter to format phone numbers as they're being displayed.

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

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.

Sometimes a ticket can relate to multiple knowledge base articles. It woule be very beneficial to be able to link multiple KB articles to a single ticket.

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.

Have an option to schedule a ticket for a specific day rather than a recurring ticket thats scheduled for every 1st of the month for example. It would be useful for one off tickets that need to be started weeks into the future

Currently, Statuses are only sortable via alphabetical order. It would be nice to be able to sort them instead via the Sequence dictated in the Configuration.

When entering time at present It must be one contiguous block that is either all billed or all not billed. Depending upon global settings it can be defined by a duration and end time, or by start and end time. But there is no way to account for other overlapping time entries. A time-tracking field that lets you enter an amount of time to deduct from a time entry without changing the start and end times would allow for this and avoid a lot of tedious small time entries. For instance, a servicedesk tech working on one matter (ticket A) gets interrupted by a call (ticket B). They handle the call, make a time entry for that, and return to the first task. In the current system, they will end up billing the duration of the call to both tickets A and B unless they make separate time entries for ticket A before and after the call (ticket B). Importantly, this gets a lot worse when that agent is interrupted more than once. With a deduction field, the tech makes their time entry for ticket B when they take the call. Then when they make their entry for ticket A, they enter the correct start and end times and then take the duration of ticket B and enter it in the deduction field. The number of time entries required to bill (or not bill) all time correctly reduces a lot and ticket notes are simpler and more readable. On top of that, an option to automatically deduct the duration of overlapping time entries would make this super simple. This could be a button or checkbox next to the deduction field that automatically calculates the deduction upon request.

Our team likes the "Action is important" checkbox but it's clunky to use and I recommend the following changes: Add ability to mark an Action as important from the 3dot Action Menu in one click - currently it takes 5 clicks and multiple screens to mark an action important When an item is marked important make the action stand out more - something like a bright colored header background on the action. currently a outlined blue star is added to the action and it can be a little hard to spot. Add ability to filter important actions from the "Select a View" Ticket Button - currently this button allows you to filter by All Actions, Conversation, Agent, etc.. Add an option for Important.

sometimes you need to re-order actions on a workflow stage so that you don't get so many crossing lines on your workflow diagram. it would be nice if you could just re-order the actions, it wouldn't impact how the stage operates, but would aid workflow readability greatly.. simple 'move action up' 'move action down' buttons would suffice.

This enhancement would dramatically improve usability and efficiency when managing large inventories, allowing users to find the devices they need faster Who Would Benefit: • IT support teams and MSP technicians managing complex fleets of devices will save time navigating device lists. • Administrators and managers will gain better visibility into device statuses and inventory health. • Helpdesk agents and end-users using the self-service portal will have a more intuitive experience locating their own equipment. How It Should Work: • Introduce a filter panel in the “My Devices” view with multi-select dropdowns and search fields (e.g., device type, model, status, customer, warranty expiry). • Allow saving of filter sets for frequent use. • Enable sorting and exporting filtered results to assist reporting and troubleshooting workflows.

Be able to create a credit to apply to the next issue of a recurring invoice and have it automatically delete itself after the next invoice is created. Either as a one time credit or have a feature that could apply a credit to an invoice for the next x amount of recurring invoices