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.

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.

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.

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.

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

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.

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 <0 to show all unsent invoices. You should also be able to filter tickets by any of their fields, such as "Time Taken" and let me put in >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 <=today if I want everything today or earlier, etc.

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.

We get quite a few tickets that are duplicates for various reasons and need to merge them together. They have similar but not accurate names and then when going to view tickets/opportunities by type and looking at all - or by going to the client and looking at the ticket screen, it just isn't always easy to tell what is what. It would be great if there was a global option to basically hide all merged tickets from any view, other than by search, if typing that ID directly.

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.

It would be awesome to have integration for Keeper password manager to sync the licenses into our customers license list. This helps with the invoicing for the customer.

Most end users do not understand the term “Login with Azure Active Directory” but all over the web most SSO services use the “Sign in with Microsoft” button https://learn.microsoft.com/en-us/entra/identity-platform/howto-add-branding-in-apps It would be great to implement "Sign in with Microsoft" as this is way more familiar to end users.

The "ESC" key will force close a current task at the worst times occasionally. When write a new ticket and when KB or canned text is suggested "ESC" key will close the entire action or ticket being worked. Add an option to disable the key activity or changing its functionality would be helpful for user experience.