Feature Ideas

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

Having the ability to pull the catalog, availability, and pricing drastically decreases the time spent on drafting quotes/proposals. Not only does it allow you to quote faster, but it will help when following up on quotes to see if the product has changed in availability or price. Finally, it helps to reduce human errors within the quote/proposal since it is pulling directly from the distributor. Seeing Ingram Micro, D&H, and Tech Data would be a game changer for this PSA.

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

It would be really useful to be able to write an email in Outlook and pick the correct ticket number from a list or search, add time in and then send to Halo through the normal copy in the mail delivery email address as usual. The reason this works much better is: a) People don't ignore direct emails from people in the same way as they ignore automated emails from a PSA system b) The formatting used is much better and doesnt break as with the current output from Halo(and you can paste in other items without the formatting getting screwed too) You could use the same mechanism to book in ticket updates, appointments from tickets and tasks/notes from tickets to work from.

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

One of the biggest complaints I have received about Halo's Knowledge Base is navigating between articles and FAQ groups. It would be extremely helpful to have both a forward/back button within the KB. And to have the FAQ group path for each article, with the ability to select any FAQ group in that path to jump to.

We currently have the ability to only show invoices that have been synched with an integration "Only show Invoices after being synced to a third party system", but being able to more selectively show invoices to users would be helpful. A few use cases could be maintaining a shorter history of available invoices, remove invoices that have synced but been updated in the third party system, or show only specific types of invoices

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.

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.

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

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

We currently have to prefix (Do not use) or something similar on invoice templates and others that were at one point used because it will not allow us to delete. This is not good functionality and templates should have an ISACTIVE boolean that can be toggled like within other areas of Halo.

We are currently using Dynamcis as CRM which has Sharepoint linked to it where all the documentation is saved (signed contracts, opportunities technical documentation) so when we create an opportunity within Dynamics, a Sharepoint folder under that customer is created. We are going to move to HaloPSA as CRM but we would like to be able to keep using Sharepoint in the most efficient way. Getting a Sharepoint list view per customer on they’re Sharepoint folder would be a great help. Also, automatically create a Sharepoint folder with the customer name in that library when creating a customer HaloPSA ánd linking it to the customer would be a very welcome feature. At the moment, it is just a connection via a Documents module which doesn't work for us. Per HaloPSA customer a unique Sharepoint folder https://sharepoint/customers/customername Per Customers opportunity tickets, automaticaly create a subfolder https://sharepoint/customers/customername/Opportunity/ticket0011-opportunitydescription1 https://sharepoint/customers/customername/Opportunity/ticket0022-opportunitydescription2

When editing an appointment that exists, the agent cannot be changed. Currently, you have to delete the appointment and create a new one for the new technician. This is inconvenient and sends out cancellations and new appointments.