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.

Please give us the opportunity to filter/search on tenants and sites instead of clicking through every page :) it gets ridiculous when you need to adjust one site but need to sort alphabetic and then spam click next page until your on the correct letter.

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.

When a ticket is in scheduled status, do not change status of ticket to updated when client responds with a "thank you," "ok," or similar response in acknowledgement to their scheduled appointment (in the same way which closed tickets remain closed after receiving these kinds of responses).

We have a few clients with Agents with access through the Co-Manage features. We were told by Halo Support that there is no way for this co-managed agent to @ mention an agent that is in the main organisation. We would like there to be a way to allow this co-managed agent to @ specific agents of teams they have access to, currently they can only ­@ mention the whole team.

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.

Ability to customise the “Overview” tab of the customer: ---Ability to Show Fields / CRM Information on the Overview tab of the customer. ---Custom Fields such as customer grade, system fields such as next call date. ---Account Manager Name ---Importance level

In HaloPSA Timesheets, we should be able to enter the Start time and End times via keystrokes on the keyboard and without having to click scroll through the time scroller for both the hour field and minutes fields to add in our times. We should also be given a field to deduct time when staff need to enter a block time in with other tickets \ tasks completed during this block time in a working day. This archaic front end is a relic of the 1980's, is inefficient + cumbersome, and cost us time.

Allow drag and drop of calendar appointments/reminders/etc between multiple agents. Bonus points for reassigning the ticket to the agent it was dragged to (at the very least add to additional agent). This is Dispatch 101.

It would be good to be able to specify the "parent" client account for a "child" account. For example, when there is a holding company that has 5 "child companies" - you could go to the holding company and see all users across all companies, all tickets, all invoices, etc. You could specify if the child company's invoices should be billed to the child or to the parent.

We have assets syncing from our Ninja RMM system, but ran into some issues, where if we delete a device in Ninja, this does not sync through to Halo, so the devices don't get deleted. Also, if we update the device status in Ninja RMM from Active to Spare, or change it to Decommissioned in Ninja, these changes also don't pull through when it syncs over. This would be very handy if enabled, as currently you're needing to do double / triple work to make sure the different systems are all in sync.

What is the ETA for Project task date dependencies to be cleaned up? Date dependencies are behaving inconsistently, with tasks sometimes moving to unexpected dates or not moving at all. • Tasks are being pushed into weekends rather than the next available working day. • There is no ability to apply lag time between dependent tasks. • Once a dependency is established, dates cannot be manually adjusted without first removing the dependency, making schedule management inflexible and time-consuming.

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

I would like to change the favicon that is shown on the customer portal – right now it’s the red haloPSA favicon which doesn’t match our color scheme at all. Replacing it with our own custom icon preferred, alternatively the ability to set a HEX color code for the existing icon would be a 2nd option Also when going to our portal the loading circle is blue at first, and then changes to our green, is there any way to fix that? Right now the favicon is red, the initial loading circle is blue, and then finally things change to green, which is a pretty bad mis-match of colors Additionally, it would be great to have the option to repeat a background image vertically, right now we had to make a fairly large image in height to have it work on every possible screen/mobile device, but the caveat is that the background image takes a second or two to load in. If we could just have it repeating on the Y axis that would solve the problem, but I was told that it's not possible, even by custom CSS at this time.

Email alerts are noisy and out of hours they are simply not seen or when human error applies we fail. When a Notification is not attended to over a period of time, its becomes more important and the Escalation process should kick in (not by repeating the same method but rather by changing it) so we introduce two levels of Advanced Notification / Escalation System Noise Microsoft Teams phone call This way we can get the right level of attention to a situation BEFORE its too late