Feature Ideas

Instead of having to create multiple teams for escalations and permissions. It would be good to have a team, and people are assigned a level within that team. This level would determine permissions, ticket assigning and escalations. So, if a ticket comes in, you can specify assign to the blue team round robin to level 1's,2's or all. When escalating you can then escalate to next level, or a different team. Would mean far less teams are created.

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 would like to send notifications from Halo to Teams chat for agents (e.g. mentions etc.) but based on the Guides and our tests Webhooks only allow sending notifications to channels, not chat TeamsBot does not have the option to receive notifications

It would be great to pull in license information for Check Point Harmony Products such as Endpoint protection and Email Security. This would allow a reoccurring invoice line to be linked to the subscription and avoid manual updates from an external report.

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

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.

Currently only administrators have access to create scheduled tickets. Being able to grant ad-hoc access to agents to create scheduled tickets for their customer's might be useful. For example: A customer account manager could create scheduled tickets for the customers they manage.

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

At the moment, the print ticket function can only export public notes and resolution notes which are visible to the end user, we have tried configuring the HTML of the print ticket PDF template but unable to include all private notes and actions. The purpose of this is to allow us conducting internal investigation when needed, we tried using report function to extract all actions & note entries against a ticket, but it does not include any images inserted.

In our previous ticket system, it was very straightforward to enter the date, a start time and end time for a time entry if we are updating entries from being on site for example. It looks like currently in Halo, I can enter a time of completion but I then will have to work backwards to work out how long I took for that particular entry. If we can have the ability to manually enter the start and finish time it would make things a lot easier rather than trying to work backwards from the finish time only.

Our teams would really like to be able to set Ticket Tags against tickets logged from the service portal. If ticket tags could be sett on on a ticket template this would work well. I've confirmed the current Tags in service portal are actually for search not for Ticket Tags.

Halo's asset management is strong, but it's difficult for engineers to quickly understand how a client is configured. Currently, the main approach is to view all assets and filter by client, which works for inventory management but not for understanding a client's environment. I'd like to see a client-centric view that brings together sites, network information, cloud platforms, applications, voice systems, documentation, and key operational details in one place. Rather than creating custom asset types and fields for everything, Halo should provide an out-of-the-box way to present this information logically and visually. Enhancements to the dependency map would also be valuable, including custom asset icons, logical and physical layouts, improved relationship mapping, and client/site filtering. The goal is to make Halo the single source of truth for client knowledge, reducing reliance on third-party tools such as Auvik, Zabbix, IT Glue, or Hudu for understanding how a client's environment is connected and supported.

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

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.