Feature Ideas

The xero integration currently makes a webhook call to Halo on allocation of payments. Halo ONLY records payments made in full leading to SIGNIFICANT divergence between the balance of un/part paid invoice in Halo compared with Xero. The impact on Account Mgmt staff in needing to access BOTH systems for invoice management is considerable. Considering that the webhook calls are already made by Xero and Halo already responds and correctly records full payments, extending this to cover the recording of partial payments would be very much appreciated and deliver considerable time savings and improvements in the accuracy of reporting on invoice states/balances within Halo.

I have so many canned texts that the scrolling is unbearable, please can why have a way to search and organize them into folders like the categories field?

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

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

Currently, you cannot select which columns to show in customer portal for assets, only 3 key fields are displayed by default. The generic description as Key field does not let the end user know, what is included, and it can include different fields for different asset types. Also adding fields from linked product such as SKU will be very useful.

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

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.

Would like to see an integration with Huntress. Amazing product and being able to receive tickets directly would be very useful.

Currently the problem finder (I think that's what it's called) option only seems to use tickets and KB's in Halo, it would be good if this could also query the global KB's and client KB's in Hudu

It would be really useful to be able to write an email in Outlook and pick the correct ticket number from a list or search, add time in and then send to Halo through the normal copy in the mail delivery email address as usual. The reason this works much better is: a) People don't ignore direct emails from people in the same way as they ignore automated emails from a PSA system b) The formatting used is much better and doesnt break as with the current output from Halo(and you can paste in other items without the formatting getting screwed too) You could use the same mechanism to book in ticket updates, appointments from tickets and tasks/notes from tickets to work from.

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

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.

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.