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.

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.

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.

When merging ticket A into ticket B, ticket A is set to closed which is great... but it is usually still stick floating around some random workflow stage. It would be great to have the option to automatically end the workflow for merged tickets. Thanks

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).

Some tickets are control tickets send from an application and are not relevant to the customer. We have already rules for them and would like the option 'Show to end user' to be available within those rules. I've already added this option in the ticket details but it remains handwork to tick this option on or off.

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

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.

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.

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.

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.

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.

Currently, HaloPSA pulls subscription, quantity and pricing from Pax8. It detects Azure subscription but can't pull the pricing/cost/sale etc As more and more clients are moving to Azure, it's important that we don't end up doing the adjustment manually each month so please improve the integration so Azure cost and sale price can be pulled into Halo and translate to invoice line items creation/update

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.