Feature Ideas

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.

When entering data on some screens, you press the Escape key to efforts to close the pop up / overlay window but instead it closes out the entire series and takes you back to the parent screen.

Canada has seen a few tax rate changes in the recent years, with the latest one being April 1 2025. We need the ability to set the date at which a new tax rate takes effect, so we can refrain from unintentionally mischarging Tax Rates to our clients and vendors. Tax Rate Update: Ensure the software automatically applies the new Tax rate to all invoices created on or after April 1, 2025. Historical Invoices: Implement a feature to maintain the old Tax rate for invoices created before April 1, 2025, even if they are edited after this date.

Currently recurring scheduled tickets can be set as daily, weekly, monthly, quarterly and annually, but there isn't an option for fortnightly. The option to schedule tickets fortnightly would be extremely useful for specific tasks that don't quite need to be handled weekly, but should be handled more than just once a month.

When merging ticket A into ticket B, ticket A is set to closed which is great... but it is usually still stick floating around some random workflow stage. It would be great to have the option to automatically end the workflow for merged tickets. Thanks

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.

I would like the option to add a user to multiple sites. we are a school society with 24 schools and have users which work on multiple schools.

Our HaloPSA instance currently has many imported phone numbers (for sites and users) that contain no formatting and are pretty hard to read as a result. This proposed auto-formatting feature would allow for phone numbers to be automatically cleaned up to conform to a specified format when displayed. For example, "1234567890" would become "(123) 456-7890". Additionally, it looks like HaloPSA stores phone numbers as text (strings) rather than as an actual numbers (integers). Instead of storing phone numbers as text, perhaps HaloPSA could automatically take formatted phone numbers and convert them to raw format-less numbers/integers. This would improve data-efficiency & would standardize the format in which phone numbers are stored. This would make it significantly easier for an auto-formatter to format phone numbers as they're being displayed.

Ability to control who can delete attachments within a ticket via Role. This came out of a configuration session with a customer requesting the ability to limit agents from deleting attachments in tickets. We have options around being able or no of deleting tickets would be handy if we had one for attachments.

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

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 really need a solution to manage more HR tasks but not to any great depth Need timesheets that reflect hours worked so clock in and out (start of the day lunch and then end of day) Leave requests, these then would help schedule work as you know who is in or out sick days - help keep a track of this

Hudu has this feature so it must be possible to achieve. If Client's website is mentioned under client, it should reach out to the website, get the logo and add it to the client in Halo.

Sometimes a ticket can relate to multiple knowledge base articles. It woule be very beneficial to be able to link multiple KB articles to a single ticket.