Feature Ideas

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.

It would be great to have the option to set 'Other attendees' as blank by default when creating an appointment. Currently, it auto-fills with ticket users, leading to accidental booking notifications if not manually removed.

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.

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

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

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.

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 be great if we could alert on M365 service health - https://learn.microsoft.com/en-us/graph/api/resources/service-communications-api-overview?view=graph-rest-1.0&preserve-view=true

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.

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.

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.

Often have similar invoices that are not reoccurring, would be nice to clone existing invoices like Quotes, or have an Invoice Template we would be able to reference.

We would like to request enhancements to the customer grouping functionality in HaloPSA to better support customer–reseller relationships. Current Challenge In the current setup, each customer is managed as a standalone entity. However, many of our customers are part of a larger relationship where they are served through a reseller. This creates challenges when it comes to: • Managing billing (should go to the reseller, not always the end-customer). • Grouping and reporting (seeing usage per customer but also consolidated for the reseller). • Maintaining the end-customer’s own identity (contracts, assets, users) while still linking them under their reseller. Proposed Enhancement Introduce the ability to: Assign a parent organization (e.g., a reseller) above an top-level. Maintain the end-customer as its own entity with its own assets, tickets, contracts, etc. Enable billing to roll up to the parent reseller while still showing detailed breakdowns per top/child customer. Provide flexible reporting both per customer and at the reseller/parent level. Benefits • Better reflects real-world business structures between customers and resellers. • Simplifies billing workflows (one invoice to the reseller, with optional breakdowns per customer). • Increases flexibility for MSPs managing both direct and indirect customer relationships. • Enhances reporting and visibility across multi-level customer structures.