Feature Ideas

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.

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.

wouldn´t it be great, to have the same login for the https://support.haloservicedesk.com/portal/ and https://ideas.halopsa.com/ and to be able to create an Idea from a ticket, so that dev could not only read the idea, but also the support case which lead to the feature request?

I would like the option to add a user to multiple sites. we are a school society with 24 schools and have users which work on multiple schools.

right on the tin. We have team leads on each team and would like to exclude those individual from the teams load balance. so far I have not seen any such setting for individuals per team. I have seen excluding a full team and agents of a particular status such as 'away' or 'offline'. While we could hack a way to make it work, it would be nice to see some additional load balance refinement in a centralized place and be able to exclude individuals.

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

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.

Ability to control what is visible on the front pages of these areas - similar to column views on tickets. currently you can not chose what information is presented here - so mobile number email address etc etc...

The "ESC" key will force close a current task at the worst times occasionally. When write a new ticket and when KB or canned text is suggested "ESC" key will close the entire action or ticket being worked. Add an option to disable the key activity or changing its functionality would be helpful for user experience.

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.

Direct password integration of passwords from 1Password to Halo PSA manage site passwords, agent passwords, and asset passwords.

Having minimum stock quantities per stock location would allow for better inventory management. If a company has work vehicles then these could be used as a stock location, allowing for quick and easy restocking.

At the moment, the print ticket function can only export public notes and resolution notes which are visible to the end user, we have tried configuring the HTML of the print ticket PDF template but unable to include all private notes and actions. The purpose of this is to allow us conducting internal investigation when needed, we tried using report function to extract all actions & note entries against a ticket, but it does not include any images inserted.

Currently when adding a tenant via the CSP integration there is a grant consent button, which works fine, problem is there no way to differentiate between one you have done vs once that you need to do. It would be great if the button was only there when you needed to grant access or maybe background process that showed a checkmark next to ones that are granted already