Feature Ideas

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.

Attachments can't currently be added to canned text. The only workaround is adding hyperlinks but teams would like the ability to add attachments to canned text.

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

I think it would be really beneficial to have Customer passwords be accessible directly within the Halo UI, if I could click on an asset and be given a password with that name, it would save me and my engineers loads of time...

We can set Advanced Settings > Default Editor Font but not the size. We need the default size to be set so everything in Halo is always set to the same font and size (email templates, pdfs, notes,etc.) Support was unable to find a solution for this.

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.

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

It would be good if the "Holiday" event types synced to Exchange calendars with Microsoft 365. As it stands the "Appointment" event type synchronises to calendars, but holidays do not.

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

There are some times where you have a complex multi company structure, but have some admin people that work cross company. Top levels (Thanks Rhys @ Halo!) work great to some degree, but, other parts (reports for example) are only for the company that the user belongs to. It would be great if we could associate a person with multiple companies and give them the option to "switch" companies in order to see the portal as a member of a different company

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

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

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.

Halo has a few N-able integrations but is missing a key offering, Cove Data Protection Cove is an amazing cloud based backup product, It would be amazing to have a link for simple things like subscription tracking to link to recurring invoice items. Primarily 365 backup items but all would be beneficial

It would be very helpful to differentiate tickets that are closed via the merge action via the ticket status. I.e. tickets closed via merged should reflect "merged" as a status whilst still taking all the same action towards the SLAs for reporting that the current close action is taking. This would give far greater flexibility and insight whilst reporting.