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

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

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.

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

Would like the ability to map asset types in Ninja to asset types in Halo. For example, in Halo all our current assets and items are filtered where asset type is called workstation or server. However, Ninja brings servers across as Windows_Server. This means we have to go and update all our reports as well as all our items where the quanity is mapped to device name is server.

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

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.

When entering data on some screens, you press the Escape key to efforts to close the pop up / overlay window but instead it closes out the entire series and takes you back to the parent screen.

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.

Our team likes the "Action is important" checkbox but it's clunky to use and I recommend the following changes: Add ability to mark an Action as important from the 3dot Action Menu in one click - currently it takes 5 clicks and multiple screens to mark an action important When an item is marked important make the action stand out more - something like a bright colored header background on the action. currently a outlined blue star is added to the action and it can be a little hard to spot. Add ability to filter important actions from the "Select a View" Ticket Button - currently this button allows you to filter by All Actions, Conversation, Agent, etc.. Add an option for Important.

This enhancement would dramatically improve usability and efficiency when managing large inventories, allowing users to find the devices they need faster Who Would Benefit: • IT support teams and MSP technicians managing complex fleets of devices will save time navigating device lists. • Administrators and managers will gain better visibility into device statuses and inventory health. • Helpdesk agents and end-users using the self-service portal will have a more intuitive experience locating their own equipment. How It Should Work: • Introduce a filter panel in the “My Devices” view with multi-select dropdowns and search fields (e.g., device type, model, status, customer, warranty expiry). • Allow saving of filter sets for frequent use. • Enable sorting and exporting filtered results to assist reporting and troubleshooting workflows.

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

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.

It seems Halo’s Microsoft Teams “End-User Chat” integration (installed via manifest.json) still relies on the Skype legacy connector, which is outdated and not fully compatible with modern Teams functionality. Because of this, sending Teams-native emojis (from the emoji picker) or images/files will always break the chat, resulting in the following message: “The bot encountered an error. Please cancel the current conversation if necessary and try again. If the issue persists, contact support for assistance.” Current Issues • In the manifest.json configuration, supportFiles is set to false. This means the integration isn’t built to process attachments. • The Chat Profile setup includes options like “Allow file uploads,” suggesting this should work — but it doesn’t. • Since Teams automatically sends emojis and pasted images as inline image attachments, this mismatch causes consistent chat failures when users use an emoji or paste an image into the chat using keyboard shortcuts. • Users must type a “/Start a new conversation” command to begin chatting, which isn’t consistent with normal Teams behavior and feels unnatural – especially for non-native English speakers who expect to start typing in their own language as they would in any regular Teams chat. If they miss this step and type anything else, the chat replies with “I do not understand the command”, which feels confusing and off-putting in what should be a natural, conversational experience. Proposed Solution Rebuild the Teams “End-User Chat” integration using the Microsoft Bot Framework v4, which would require an Azure Bot registration. From our understanding, this would address the underlying limitations by: • Supporting Teams-native emojis and inline images properly. • Enabling reliable handling of files, images, emojis, and attachments. • Aligning Halo’s Chat Profile upload settings with actual functionality. • Allowing removal of the “/Start a new conversation” command by automatically detecting new conversations. Why This Matters • The Skype legacy connector is deprecated and not compatible with modern Teams message formats. • The Bot Framework v4 supports Teams-native emojis, attachments, adaptive cards, and conversation events. • This would add significant value for many customers, allowing end users to reach their service provider through Halo natively within Teams, where they already work every day.