Feature Ideas

Just like using the @ in a ticket will bring up the ability to reference a user I would like to see similar ability to reference another ticket ie.. @ticket# or something like this which will make it a hyper link.

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 only administrators have access to create scheduled tickets. Being able to grant ad-hoc access to agents to create scheduled tickets for their customer's might be useful. For example: A customer account manager could create scheduled tickets for the customers they manage.

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

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.

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

The ability to do some advanced filtering on all table/tile overviews and bookmark these views. Example below: Field starts with "value" AND / OR Field !contains "value"

Have an option to schedule a ticket for a specific day rather than a recurring ticket thats scheduled for every 1st of the month for example. It would be useful for one off tickets that need to be started weeks into the future

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.

Centrally managed groups of MSPs (or franschise) would like to distribute and regularly update Products/Items to their Sub-companies to have the same service offering to their customers (Nation/region wide). Every member of the group is their own organisation/company and therefore they would like to have separated HaloPSA instances. There is a central organisation that is in charge of the Product (and Service Catalogue) that all the local offices should offer to their local market. They now asks how they best would be able to transfer information and product catalogue from the central organisation the local offices (all as separate HaloPSA instances). From the Centralized HQ they would like to: Be able to send/update the local offices Product Catalogue From the Local Offices they would like to: Send reports and/or data about sales, profit and information related to the Centralized offerings/product catalogue. What possibilities are there for them to work closer together local offices the central organisation?

Have the ablility to create a recurring invoice template which can have all line items added but only bill/show on the invoice where they is a quantity. Also in the template have the Quantity being able to be set by Assets / Licecnce / User / Subscription The Idea behind this if we add a new product to the customer "office365 E3" Licence via Pax8 we dont need to go and add the item to the customer.

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.

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

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.

It would be great to see something like ChatGPT integrated directly into the Knowledgebase article creation for HaloPSA. We already do this manually - would be nice for HaloPSA to just read from a ticket and make recommendations using ChatGPT to automate creating SOP's and Knowledgebase articles based on tickets coming through.