Feature Ideas

There is a setting under Customer > Billing called "Preferred Delivery Method" which can be set to "None, Print, Email". Right now, that setting doesn't do anything. A nice feature would be to have the option to generate a pdf for printing of all of the unpaid invoices for every customer who is set to "Print" so that they could all be printed at once without having to hunt each one down.

We currently have the chat facility accessible via the Self Service portal however most of our clients do not use this as they find it easier to contact us via email. It would be a game changer if Halo could have a desktop feature where a 'Tray Icon' can be placed on the users Task bar and when expanded, quick access to a few frequent options could be accessible. For example: 'Log a ticket', 'View my tickets', Chat to an Agent', Knowledge Articles' etc. With end user experience in mind, it would be great for users to engage directly with our team rather than the tradtional email process. This would boost turnaround times as well as customer satisfaction. Attached is an example of another MSP software platform where there desktop tray icon is available.

Halo’s built-in dashboards are excellent for data that already lives in Halo, but most MSPs also hold important information—security alerts, compliance scores, financial KPIs—in external systems. Many partners could benefit from an official Power BI Embedded widget that lets us surface those external metrics inside the customer portal in a simple, secure way. What the widget should do • Allow us to register our own Power BI Embedded capacity (A, F, or P SKU). • Let us pick any report/page and map the signed-in Halo company or user to the correct Row-Level Security filter in the dataset. • Show the dashboard in a portal tab or widget with no extra licences for the end user, reusing the same SSO they already use in Halo. This would give MSPs a clean, scalable path to present non-Halo data—such as security posture, patch compliance, or budget reports—right alongside native Halo metrics, delivering a single, seamless view to our customers.

Add fields for profit / cost center to labour & items / products so then you it to and qoute, order or invoice it follows all the way to the integrated billing system. For ability to follow up financials/sales more granually in Xero, QuckBooks or Fortnox etc.

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.

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

Want to send invoices that are unsent after reviewing them? Well, get prepared to tick 250 really tiny boxes and hope none of them fail to send otherwise you'll have to do it again. You should be able to filter invoices by their creation date. Likewise, you should be able to filter the sent column and enter NULL or "" or 2 to show all tickets with more than 2 hours on them. On the client screen, I should be able to filter the next call date by entering

We should have the ability to easily create rules/workflows or alerts when an appointment is missed. Something simple as: If an appointment is missed by X time, do this... If an appointment is missed by 2 hours, change ticket status. If an appointment is missed by 2 hours, update appointment to incomplete, change status to scheduling required, and email dispatcher Right now you've got to do a bunch of custom work to do this via runbooks and it should be something simply built-in.

Have a secure way of sending passwords to Customers. Via a button in Halo, where you'd type in a password, it'd generate a secure link and embed it into the body of the email - then when the user clicks on the link, they are prompted to enter the ticket number for it. Or are forced into an area of the portal to retrieve the portal. Something like the attached maybe as options

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

Have the ability to send overdue invoice reminders to customers based on a specified timeframe.

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

Send email reminders to clients to accept or reject quotes before they expire and close.

The HTML editor chosen for use across HaloPSA lacks and has a terrible time copying data from Word Docs. I would love to see an improved or replace HTML editor across HaloPSA, especially in Knowledge Base Articles.

Currently, we are required to present serial numbers on invoices for some serialized items. At present, there is no variable which allows us to include the serial number of a consigned item in any way on an invoice. The goal is, when we sell something (say a laptop), we should be able to select that item from inventory, and the serial number of the item selected from inventory should appear on the customer's final invoice.