Feature Ideas

Have a secure way of sending passwords to Customers. Via a button in Halo, where you'd type in a password, it'd generate a secure link and embed it into the body of the email - then when the user clicks on the link, they are prompted to enter the ticket number for it. Or are forced into an area of the portal to retrieve the portal. Something like the attached maybe as options

We really need clients to be able to select options in quotes. i.e if we give them the option of Laptop A and Laptop B, and additional options for 3 or 5 year warranty, we need them to be able to select the options they want before accepting the quote in the portal

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.

I would like to have the capability to grant access to existing objects using access control. For instance, let's consider a scenario where I create a new role for an agent to be able to create scheduled tickets. While this functions works well for newly created tickets, the issue arises with existing scheduled tickets, which remain invisible until you manually assign permissions to each ticket using access control. This process becomes impractical, requiring manual addition of correct permissions for every object created. Ideally, permissions should be set from the root, iterating through all already created tickets, and automatically accounting for new objects. This permission model should be used for all settings that have Access Control in some form.

imagine that when receiving a call in Microsoft teams through teams calling, Copilot transcribed the entire conversation and put a summary of the conversation in your ticket. AI could set all ticket parameters, and you only need to check if everything's correct and press save... This would greatly improve ticket documentation and background information on issues that now gets lost in the manual process.

The documentation for HaloPSA is nearly unanimously the biggest gripe everyone has with the product, and better documentation has been promised for ages. Let the community help take some of the burden off the Halo team. I'm thinking something that uses tech like Git to version-control, PR, and allow for an easy review process. Markdown support would help us make it readable. And something with the ability to link other pages or issues. CakePHP has some of the best documentation of any project we've ever used. I think it's autogenerated by SphinxDocs reading the Github Repo This would be a HUGE help to the platform as so many of us see things in Halo and have no idea what they do. Letting customers and fans drive documentation and having it be in a controlled environment will ensure that documentation is customer-driven, accurate, and relevant.

Currently, we are required to present serial numbers on invoices for some serialized items. At present, there is no variable which allows us to include the serial number of a consigned item in any way on an invoice. The goal is, when we sell something (say a laptop), we should be able to select that item from inventory, and the serial number of the item selected from inventory should appear on the customer's final invoice.

Have the ability to create Dashboard Only Agent for Interactive Displays Similar to API Agent.

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

Would be extremely handy to have integration with SentinelOne Much the same way ingram works, so it can be used as a sub count against recurring invoices. Would love the ability to map manually like the Ingram connector also SentinelOne is one of the biggest security providers in the world Surely a lot of people could benefit

I know Halo say they have various backups and DR plans in place, but it's not good practice to solely rely on any one company to protect your vital data. Please implement a bulk export or database dump feature that can be scheduled to give us access to our data, should a disaster occur.

It would be good to assign To-Do's/Tasks to other agents from within a client support ticket. This could be ad-hoc or templated.

ITGlue is designed to use PSA as the primary source of truth and everything else it finds from other integrations gets complemented however there are limitations to Halo's ITGlue integration. Please help resolve these limitations: Sync assets from HaloPSA to ITGlue and allow MSPs to map categories so everything gets synced in the correct area Improving the integration to be a bit more like the Xero integration so that when clients are created they instantly populate over to IT Glue ready for data entry Allow tickets, contacts, Customers, Core + Custom/Flexible Assets(Important for MSPs to have the option to map assets so everything goes in the right place in HaloPSA and vice versa), Sites/Locations to be synced to and from ITGlue Most importantly: Please sync Primary Location Important contacts Also, push the list of agreements to quick notes, if possible Contact Roles

User custom fields are unnecessarily limited to displaying on Details or Custom Fields system tabs. It would be beneficial to have more flexibility to add them to other existing system tabs if desired. For example, we have a custom field we added related to a monthly customer report we send. It makes a lot of sense for us to display it on the Preferences tab, under Email/Marketing Settings, but that is not possible with the above limitation.

Currently when creating an appointment the subject line is prefilled with the $symptom variable. I would like to be able to add additional variables to the default subject line such as $FAULTID. If you manually specify the $FAULTID variable it will pull the value however there is no way to default this currently. Example of what I would like to set as the default subject line for every ticket $FAULTID | $symptom | $AREA