Feature Ideas

While the Azure subscription is detected, the integration is currently unable to retrieve key financial data such as pricing, cost, and sales figures. Request for Improvement: As more clients transition to Azure, it's essential to streamline the monthly billing process. To avoid manual adjustments, please enhance the integration so that Azure cost and sales data can be automatically pulled into Halo. This should support the creation and updating of invoice line items based on actual usage and pricing.

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

It would be great to get an upgrade to the ALSO integration. We could really like to see start/end date and cost/price fields beeing updated through the integration.

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

If an Optional line item is in a pending status, it should not be included in the Total on the quote until it is selected/approved. It would also be nice if they can select the optional items before Approving the quote.

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

When a category is not present Halo prompts to say there is not. You then clear the alert, add category and hit send again. Could the alerrt just come up with the category select field? Then the process is just select the category and hit send.

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've had poor surveys resulting from a 3 strike rule type scenario where the end user has been unavailable for quite some time. We would like to ensure our agents have done everything possible to reach the end user so if they called the user from the ticket it would be good to record data such as call status (busy, answered, unanswered) and possibly the duration of the call. The current call on Microsoft Teams is flawed in that the note gets added to the ticket regardless of the outcome of the call. Teams asks for approval to make the call and it can be cancelled and still result in the note on the ticket saying a call took place.

It would make it easier to read the Pie Chart at first glance rather than having to look at the colour coding labels on the side and matching the correct colour to the label. This would be especially beneficial for pie charts which display data for more than 5 categories.

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 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.

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

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.