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?

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.

You can't easily move around the email addresses when emailing from a ticket. It would be great if you could drag someone from CC and drop into the To section without having to search for that user and delete the other one.

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.

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

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.

Halo is a fantastic tool, and the customisation is beyond unbelievable - however - workflows can be lacking. Coming from ConnectWise Manage before Halo - the one thing I do actually miss about CWM is how they managed their Workflow Rules. This is a general section where it will list all the workflows, allow you to create workflows based on certain events within specified table references as well as adjust the frequency in which it occurs. For example, You could reference the Invoices table and set that the invoice is x days past due, then run an action to send an email. This is highly customisable and if Halo could implement this and centralise the management of workflow rules and expand on the current ones - I feel it would make it a game changer.

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.

Ability to merge sites for a customer, in the same way as its possible to merge a customer.

When we add our ninja agent before the stock is fully received (or if there's a mistake in the serial number), we end up with two assets. This most often occurs when we install ninja/rmm on an endpoint which creates an asset, then we receive/deliver the asset from a PO afterwards, which also creates an asset. I'd like to be able to retain the purchase information from the PO'd asset and everything else from the RMM synced asset. Or, if there's ever a field merge in question, just ask which of the two should "win". I currently do this manually via the API that copies data from the RMM synced asset into the purchased asset, then deletes the RMM synced asset.

There's currently 'forward' functionality within tickets. We'd like to see the ability to reply to an email so we can continue an email trail. Currently when sending an email from a ticket, it doesn't include the history of the ticket specific to the email you're wanting to reply to.

in the suppliers tab, can we add a filter option to the columns. when we have many suppliers, it is becoming a pain to have to scroll through the whole list to be able to see if a supplier exists. currently we can only sort the columns

In the settings we have all tickets getting 'Incident' as Ticket Type but some email tickets needs to have different Ticket Type. For some of them we have already rules in place but still we have to change Ticket Type manually.