Feature Ideas

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

The HTML editor chosen for use across HaloPSA lacks and has a terrible time copying data from Word Docs. I would love to see an improved or replace HTML editor across HaloPSA, especially in Knowledge Base Articles.

Would be great if we could alert on M365 service health - https://learn.microsoft.com/en-us/graph/api/resources/service-communications-api-overview?view=graph-rest-1.0&preserve-view=true

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.

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.

Current Functionality: When an agent is tagged in a ticket it shows up in their notification pane. When the agent clicks on this notification it takes them to the very top of the ticket. In many cases other actions/updates may have been added since the user has been able to check the notification, especially on collaborative project or estimate tickets. Why it matters: This creates a lot of time spent for the agent looking for the update that they were tagged in specifically. In larger estimates and projects this can be very time consuming. Especially for the cases where you may be tagged in multiple places in the same ticket, then you have to filter through which notification is associated with each tag. Proposed Solution: The proposed solution is to add an HTML anchor to notifications that have agents tagged. This way when they click the notification it will still open the ticket, but take them to the associated action that triggered the notification. Saving them time searching through the ticket. It likely can be accomplished by anchoring to the action div id.

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.

Add the ability to make actions dynamically visible/invisible to agents based on ticket criteria such as the ticket status.

We heavily use to-do's as a way of creating checklists on common steps. However, a lot of our clients require unique custom checklists. We use IT Glue currently for this and it allows not only a to-do, but it allows that to-do to be expanded detailed steps (written in HTML). What I would like to see is the following To-dos have their own tab in tickets and not just a sidebar. To-do's can be expanded to show links or steps (See screenshot of Glue) To-dos once completed hide from the list To-do's that can be associated with a client site and be templated To-Do templates can be grouped

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

At the moment even if an Agent is marked as On Holiday/Sick in Halo, if a User replies back to a ticket the ticket remains with the Agent that is on holiday meaning a lot of manual intervention is needed to check and move tickets. This feature idea is to have a setting/configuration option that would allow a ticket to move to Unassigned when a User replies back to a ticket 'On Hold' or 'In Progress' where the Agent is On Holiday/Sick. I don't think there is currently another way of achieving this (e.g. via rule) - and have checked this out.

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.

We get quite a few tickets that are duplicates for various reasons and need to merge them together. They have similar but not accurate names and then when going to view tickets/opportunities by type and looking at all - or by going to the client and looking at the ticket screen, it just isn't always easy to tell what is what. It would be great if there was a global option to basically hide all merged tickets from any view, other than by search, if typing that ID directly.

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