Feature Ideas

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.

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.

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.

Here's all the things that need to be included in the next iteration of Time Sheets in Halo: Time sheet periods - The ability to establish timesheet periods to tie billing, payroll, workflows, approvals to. I expect my team to update their timesheet daily with a minimum of all hours work entered onto them. I expect the team to submit them to me every week so I can review and approve them to move over to billing to be invoiced.Time Summary View - The ability to slice & dice data on a time sheet to speed up time sheet reviews for approvals. Need to see Time by Ticket, Time by Day, Time by Charge Type, Time by Agreement Type, time by billable status, time by appointment etc. There's no point in having an approvals process without being able to see what we're approving without opening each ticket one by one... I need to make sure that every time entry is compliant. Travel time is set to travel time, communications is set to no charge, notes are clean & professional, AM/PM mistakes are caught, super long time entries are caught etc.. A single tech could have 50+ time entries per day that I have to open each one - one by one - to review. multiply that by the number of techs I supervise... there goes my day.Flagging items for rejections with a reason/explanation. As a timesheet approver, I need to redirect corrections back to the agent with context so they can correct it next time.Time Sheet notifications - Notifications should have multiple variables to notify on. Right now, timesheet notifications are based on whether they meet or exceed hours logged, but I want it to be notified on hours worked. No option for that.Lock timesheets once submitted WITHOUT affecting future actions on a ticket.Ability to enter blocks of time to non-billable/non-production activities. For example: meetings, team events, internal stuff, administrative "things"... Sure I could tell the team to create a ticket for those things, but that's time consuming and too much overhead to make it work. And I refuse to enable quick time because Quick time doesn't allow me to restrict how it's used. (I have issues with folks entering quick time against clients and that's a no no...) time against clients are only for tickets & projects. So, quick time is not allowed here. I hate to say it, but this is one area ConnectWise had right. @Halo - we are MSP's - time is money, and without a method for governing and auditing that time - Halo is nothing more than an ITSM.

In the Action context menu (the "..." on an existing Action like a Time Entry) there are options to "Copy Action to Ticket" and "Move Action to Ticket", but both require a target ticket. There is no way to duplicate an Action in place on the same ticket. Use case: splitting a Time Entry after the fact. Example: a 2h entry turns out to have been 1h Support + 1h Coaching with different Charge Types and categories. Right now I have to shorten the existing entry to 1h and create a second one from scratch, re-typing all fields (description, category, charge type, billable flag, custom fields). A "Duplicate" option in the same context menu would copy the Action on the same ticket, pre-filled with all values, so only the differing fields need to be adjusted.

In many table views, it is possible to adjust the columns via the menu, or to link a custom column profile. However, there are still certain table views (such as Awaiting Reviews for invoices) where this is not yet possible.

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

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.

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.

In the settings screen it is currently only possible to search settings for a /section/ (i.e. 'integrator'). Given the vast complexity of the HALO product and the fact that a great number of settings that might be considered related are not actually grouped together, the organic way in which settings are added, and the typically very lacking documentation, please make it possible to search the actual setting 'labels' and descriptions. i.e. I should be able to search for "new user" and at least be able to click through to the exact location of, if not see the current state of, all the setting options with the string "new user" in their title or in-line help text

wouldn´t it be great, to have the same login for the https://support.haloservicedesk.com/portal/ and https://ideas.halopsa.com/ and to be able to create an Idea from a ticket, so that dev could not only read the idea, but also the support case which lead to the feature request?

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.

Ability to merge sites for a customer, in the same way as its possible to merge a customer.

Used for Helpdesk with larger customer bases to have the option to escalate a ticket to a sites dedicated engineer for technical assistance.