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.

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

When we are creating quotes for customers, it would be handy when the invoice has been issued for hardware payment from the ticket gets paid by the customer, a private not would be added to the ticket with the Invoice PAID date and this will also notify whoever owns the ticket to go ahead and order the product.

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

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

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.

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

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

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.

It's currently impossible to visually navigate invoices in Halo. If you want inspect the contents of of a few different invoice, you need to click in to preview it, then navigate back out and then back in to the next one. We need a button on the actual invoice preview to navigate between al invoices to the client. Hope you can make this happen !

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.

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.

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.

There currently does not seem to be any place for us to sync a current Credit Memo from QB Online to Halo. It's a disconnect that we believe would help the integration tremendously. Credits happen fairly often and we would want to sync them to HaloPSA.