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

Currently you can only have one Closed Ticket Status. This doesn't really suit how we work as we sometimes Cancel tickets which are raised in error, where as any tickets which are brought to a successful conclusion are 'Resolved'. At the moment when we Cancel tickets, they still show in the User Portal under Open Tickets as the Status itself is classed as an Open status, not closed. We're using the only Closed status we have available as Resolved.

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

Hudu has this feature so it must be possible to achieve. If Client's website is mentioned under client, it should reach out to the website, get the logo and add it to the client in Halo.

Please can a config option be added where it shows the SLA time left in days? We are a service area that uses several days as a SLA, and it would be beneficial to keep this functionality as it is what our users are used to and we can gauge how long is left on an email easier, which is more difficult when it is in hours.

I would like the option to add a user to multiple sites. we are a school society with 24 schools and have users which work on multiple schools.

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.

Currently we just use the url of the license page to go to it. But if we could reference it on the ticket similarly to how tickets reference each other, that would be a lot cleaner and easier to find inside a ticket. Would also be nice when looking at the subscription to have a tab showing references and being able to see all tickets linked to the subscription. Linking back to the original purchase order would help out with documentation.

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

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

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

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.

Looking at a use case where items on a PO were received but the information was input wrong so they essentially need to be undone. I.e., cost/price, quantity, etc. It would be nice to be able to un-receive and un-consign to be able to edit the PO line item and re-receive the stock.