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

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

When Quotes are sent, it would be helpful to choose who should receive notifications of when quotes are viewed for others, instead of only the person who sent the quote.

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.

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

W are purchasing Azure resources from Ingram Micro - Azure New Commerce Experience (NCE). Halo picks up this subscription which shows a quantity of 1, which is correct. There is only a single subscription. The important data, what has been consumed under the subscription and is billed to us by Ingram Micro is not available. We have to manually go into Ingram, find the subscription for the relevant customer and then manually update the recurring invoices every month. Please work with Ingram to made the consumption data available for the subscription. This is what is important to us and I am sure many other MSP's are doing that are not large enough to purchase directly from Microsoft.

Currently the use of to do lists gives you only 2 options: either you performed the tot do list item and you mark it as donethe to do list item is not needed and you delete/remove the to do list item from the list Now the issue with the second option is that while some to do list item might not be needed in the context of a particular task, reporting wise you have no clue that that to do list item even existed before it was removed. Therefore my suggestion to have a 3rd option: to do list not applicable/not needed. It would count as a valid performed to to list action. And here the to do list item would remain on the ticket. Visually we could have a to do item for which the text is formatted in strikethrough.

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

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.

Under ticket ID: 1010499, we will be making the following improvements to One-Time Password sending: Allowing link to be sent without the need to log into the portal to use. Log an action into the ticket when a link is generated A default for the validity period. This is currently planned for November 2025. If there are any further refinements you would like, please suggest them below before then.

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.

the notification if a quote has been viewed is great, but it be even better if I have a log file under the opportunity and/or quote to see when the quote has been viewed. We usually have 10-20 open quotes and I cant keep track of all the notifications who watched the quote after a couple of days. We also.omtimes create two quotes under one Opportunity (V1 and V2) so the logile of the views of the quote should cumulate unter the opportunity.

We don't always want to use projects to default Charge Types. In ConnectWise, we had a billing tab that let us change a Charge Type at the ticket level. This meant that every time an entry was added to that ticket, it received the assigned Charge Type. We frequently have billable tickets where using a project would be overkill.

Currently it is possible to filter the progress feed based on a couple of parameters (internal/external, public/private, time entries,...) I think it would also be beneficial to be able to filter based on origin. Take for example the project and the project tasks. It is possible to add every action from a project task to the related project. This means that the project manager would be able to follow all the actions going on on his/her project through the progress feed on the project, instead of having to open every project task individually. But this makes the progress feed on the project potentially very long and difficult to read. You might for example have some difficulties to identify the project notes. That's where a filtering on origin would be great.