Feature Ideas

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.

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.

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.

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

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.

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

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.

Would like to be able to have the ability to note and warn about specific techs being banned by specific clients. Ideally this is something that can be configured outside of using the standard pop-up message so that it can be reported on and tracked. Some criteria to consider: The fields for this banned list should be structured and at a minimum include 1.) a drop down for the selection of the DTC tech name, and 2.) The start date of the Ban request, 3.) The end date of the ban (or a date by which DTC will evaluate the status of the ban and potentially remove it.There should be an option to enable a ticket popup message if/when a ban for a client is in place. This should be in addition to whatever notes are in the "normal" popup message.There should be a color option such that the color of a banned message should be different so as to highlight itThere should be a built-in report within HaloPSA in order to create/email a report and/or create a dashboard widget with this information.

In the Suppliers section when an admin(agent) creates a new list (Button "Create a new list") it should be possible in the Filters Tab to use more fields from the standard fields: Supplier is ActiveIs a SupplierIs a Manufacturer

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