Feature Ideas

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.

When entering time at present It must be one contiguous block that is either all billed or all not billed. Depending upon global settings it can be defined by a duration and end time, or by start and end time. But there is no way to account for other overlapping time entries. A time-tracking field that lets you enter an amount of time to deduct from a time entry without changing the start and end times would allow for this and avoid a lot of tedious small time entries. For instance, a servicedesk tech working on one matter (ticket A) gets interrupted by a call (ticket B). They handle the call, make a time entry for that, and return to the first task. In the current system, they will end up billing the duration of the call to both tickets A and B unless they make separate time entries for ticket A before and after the call (ticket B). Importantly, this gets a lot worse when that agent is interrupted more than once. With a deduction field, the tech makes their time entry for ticket B when they take the call. Then when they make their entry for ticket A, they enter the correct start and end times and then take the duration of ticket B and enter it in the deduction field. The number of time entries required to bill (or not bill) all time correctly reduces a lot and ticket notes are simpler and more readable. On top of that, an option to automatically deduct the duration of overlapping time entries would make this super simple. This could be a button or checkbox next to the deduction field that automatically calculates the deduction upon request.

Service tickets allow for assets (PC's printer, etc) to be connected to the ticket; however when creating an Opportunity ticket, there is no option to add an asset to reference what hardware is being replaced, etc

We would like to see within the ticket count also the tickets where an agent is additional so that you have a complete picture of open tickets for that agent.

In HaloPSA Timesheets, we should be able to enter the Start time and End times via keystrokes on the keyboard and without having to click scroll through the time scroller for both the hour field and minutes fields to add in our times. We should also be given a field to deduct time when staff need to enter a block time in with other tickets \ tasks completed during this block time in a working day. This archaic front end is a relic of the 1980's, is inefficient + cumbersome, and cost us time.

When linking a Ticket to another Ticket, often there is a long list of Tickets to select from.It would be helpful a ticket was a Parent or a Child ticket, that the -P or the -C was next to the Ticket Number.

Could you please build a Microsoft Copilot Connector that allows interaction with all the data in Halo?

Ticket notes & draft emails, etc. should autosave to the tickets in case of a browser refresh or crash. If you had started writing notes and then refresh the ticket page then you should have a button or option to reload what you had last typed in there instead of needing to start over. I'm a new Halo user coming over from Syncro and this is the most basic feature that Syncro has and Halo is missing. I've lost a few draft ticket notes already but I'm sure many of you have lost many more. Ideally this would work in forms outside of the service desk as well, in the knowledge base, in the self-service portals, etc. All of those rich text and really any field should be autosaving while you type so if you refresh then you can click a button to get back what you had.

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

The Current MCP Server doesn't work with Claude (OAuth errors). Adding OAuth 2.0 Auth Server compatibility (see https://ideas.halopsa.com/b/wmw32n0q/feature-ideas/oauth-20-authorization-server-metadata) may resolve this... but whether it does or not, Claude integration would be very useful for those of us using it as a corporate AI solution.

Timesheets in bulk are difficult to manage, and the views over a month are too much, even weekly having a team of 15 and a single timesheet manager, it becomes chaos and borderline pointless, often just hitting the final 'approval' button that does all at once for that date period. Not show weekends when viewing a month/only show working hours/days as a viewFilter by approved/unapprovedNotifications when timesheets submittedMultiple timesheet managersRejection comes from the timesheet manager, not the Helpdesk email addressTrigger warning when 'approving all' to warn that all items are about to be approvedFreeze the name and date column/row so the engineer's name and date always stay visible.Billing is typically done monthly, so the option to just view that month/week would be amazing, not having to select start and end date, and then re-select the date range because clicking 'next' retains the days selected, ( for example 28 days selected, clicking next will select the next 28, not the entire month if there are 31 days)

Have the ability for customers to type their name and auto generate a signature on the quote instead of having to draw a signature using the Mouse

I would like to propose a feature request that I believe could enhance the overall user experience. Specifically, it would be very beneficial to have the option to pin the notifications panel. Currently, when navigating between pages, the notifications panel closes automatically, requiring it to be reopened each time. Having the ability to keep it pinned would make it much easier to monitor incoming alerts without interruption. I would appreciate your thoughts on this suggestion. Thank you.

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.