Feature Ideas

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

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

Permissions with the ability to delete ones break time or a manager/admin could. Currently once you add the break there is no way to remove it. You can change the time to 00:00. but again those things should be managed by a manager/admin. Not the user.

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

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.

Add the ability to organize actions into groups in tickets. This could be accomplished with either drop-down menus with multiple actions or with brackets with actions tied to that group. Make it where we can name the group anything. An example would be having 4 Escalation actions; Escalate to Tier 2, Escalate to Tier 3, Escalate to Sales, Escalate to Manager. Most of those are not needed that often. It would be nice if there was a way to put them all together in one 'Action Group' that we could expand if one of those actions is needed.

The inclusion of personalized column profiles in crucial areas like invoicing, quotes, orders, and products would provide significant advantages for the Admin and Accounts teams. This feature enables them to optimize these sections according to their specific needs, ensuring that the most critical information is readily visible and easily accessible.

The current SharePoint integration only allows mapping to folders in the root Halo instance. It would be great to be able to map SharePoint folders to document folders at the Client level. We would specifically use to store and share client agreement documents with each client.

It would be really helpful if there was a way of generating a link for the end user portal that automatically logs users in. True passthrough SSO. This would allow us to publish a link on an internal intranet or direct users to log tickets without having to explain that the end user needs to "Login with Azure Active Directory" End users are not familiar with this terminology and Microsoft actively discourages signposting these technologies to end users.

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

The documentation for HaloPSA is nearly unanimously the biggest gripe everyone has with the product, and better documentation has been promised for ages. Let the community help take some of the burden off the Halo team. I'm thinking something that uses tech like Git to version-control, PR, and allow for an easy review process. Markdown support would help us make it readable. And something with the ability to link other pages or issues. CakePHP has some of the best documentation of any project we've ever used. I think it's autogenerated by SphinxDocs reading the Github Repo This would be a HUGE help to the platform as so many of us see things in Halo and have no idea what they do. Letting customers and fans drive documentation and having it be in a controlled environment will ensure that documentation is customer-driven, accurate, and relevant.

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.

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

I would like to change the favicon that is shown on the customer portal – right now it’s the red haloPSA favicon which doesn’t match our color scheme at all. Replacing it with our own custom icon preferred, alternatively the ability to set a HEX color code for the existing icon would be a 2nd option Also when going to our portal the loading circle is blue at first, and then changes to our green, is there any way to fix that? Right now the favicon is red, the initial loading circle is blue, and then finally things change to green, which is a pretty bad mis-match of colors Additionally, it would be great to have the option to repeat a background image vertically, right now we had to make a fairly large image in height to have it work on every possible screen/mobile device, but the caveat is that the background image takes a second or two to load in. If we could just have it repeating on the Y axis that would solve the problem, but I was told that it's not possible, even by custom CSS at this time.