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

Ticket notes & draft emails, etc. should autosave to the tickets in case of a browser refresh or crash. If you had started writing notes and then refresh the ticket page then you should have a button or option to reload what you had last typed in there instead of needing to start over. I'm a new Halo user coming over from Syncro and this is the most basic feature that Syncro has and Halo is missing. I've lost a few draft ticket notes already but I'm sure many of you have lost many more. Ideally this would work in forms outside of the service desk as well, in the knowledge base, in the self-service portals, etc. All of those rich text and really any field should be autosaving while you type so if you refresh then you can click a button to get back what you had.

You can't easily move around the email addresses when emailing from a ticket. It would be great if you could drag someone from CC and drop into the To section without having to search for that user and delete the other one.

Problem: In Configuration → Tickets → Views → Config Lists, all lists are displayed in a single flat table. Once you have many lists, it becomes hard to find, maintain, and govern them. Who benefits: Halo admins and service delivery teams who build lots of lists for different purposes, such as: Operational navigation lists for Agents/Teams (often tied to Areas) Dashboard/reporting lists Segmented lists for external/co-managed agents to see only their relevant tickets How it should work: Introduce List Groups (folders/categories) for Config Lists so admins can: Create/manage groups (e.g., “Internal Ops”, “Reporting”, “Co-Managed”, “Customer-specific”) View lists by expanding a group, or filter by group Optionally display “Group” as a column and allow sorting/filtering (Nice-to-have) Support permissions/ownership per group to make governance cleaner Outcome: Cleaner admin UX, faster navigation, better scalability, and easier long-term governance as a tenant grows.

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.

Hudu has this feature so it must be possible to achieve. If Client's website is mentioned under client, it should reach out to the website, get the logo and add it to the client in Halo.

ability to update clients, sites, users fields on a bulk level. by selecting multiple of them and getting a pop up of some sort with fields to edit and change.

When logging a vendor support ticket via the API integration Halo to Halo can we haev the ability to log these under the affected user of the original ticket in the customers halo. customers of ours will escalate tickets to us from their halo to ours and we need to contact the affected user not the agent who has escalated to us. At current we have to get the customer to type in the users details in the note field when raising too us and we have to manually change the contact on our side.

The current default notification sound is incredibly annoying. All of our agents complain about it. Would be nice if we could update the default sound to something a little less harsh instead of just disabling the sound all together.

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

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

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

We currently have the chat facility accessible via the Self Service portal however most of our clients do not use this as they find it easier to contact us via email. It would be a game changer if Halo could have a desktop feature where a 'Tray Icon' can be placed on the users Task bar and when expanded, quick access to a few frequent options could be accessible. For example: 'Log a ticket', 'View my tickets', Chat to an Agent', Knowledge Articles' etc. With end user experience in mind, it would be great for users to engage directly with our team rather than the tradtional email process. This would boost turnaround times as well as customer satisfaction. Attached is an example of another MSP software platform where there desktop tray icon is available.

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

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