Feature Ideas

Let us know what you'd like to see in a future release of HaloPSA

Trending
  1. Microsoft Copilot Connector

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

    Craig M

    11

  2. Monitor M365 Tenant Health through CSP

    Would be great if we could alert on M365 service health - https://learn.microsoft.com/en-us/graph/api/resources/service-communications-api-overview?view=graph-rest-1.0&preserve-view=true

    Jeremy

    3

  3. Clicking on a Notification should take you to that section of the ticket

    Current Functionality: When an agent is tagged in a ticket it shows up in their notification pane. When the agent clicks on this notification it takes them to the very top of the ticket. In many cases other actions/updates may have been added since the user has been able to check the notification, especially on collaborative project or estimate tickets. Why it matters: This creates a lot of time spent for the agent looking for the update that they were tagged in specifically. In larger estimates and projects this can be very time consuming. Especially for the cases where you may be tagged in multiple places in the same ticket, then you have to filter through which notification is associated with each tag. Proposed Solution: The proposed solution is to add an HTML anchor to notifications that have agents tagged. This way when they click the notification it will still open the ticket, but take them to the associated action that triggered the notification. Saving them time searching through the ticket. It likely can be accomplished by anchoring to the action div id.

    Andrew H

    0

  4. Attachments Permissions within Roles

    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.

    Joe P

    27

  5. Better HTML Editor

    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.

    Josiah S

    20

  6. Add BCC list to "Edit Email Recipients" list

    Its not editible in the button, but it is editable in the "Email Actions" Probably just an oversight, but it should be added so you don't have to start an action to edit the fields.

    Kyle S

    1

  7. Autosave everywhere

    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.

    Ari M

    1

  8. Calendar Drag and Drop

    Allow drag and drop of calendar appointments/reminders/etc between multiple agents. Bonus points for reassigning the ticket to the agent it was dragged to (at the very least add to additional agent). This is Dispatch 101.

    Bryan L

    2

  9. Move Tickets to Unassigned if Agent is marked as On Holiday/Sick (Automatically)

    At the moment even if an Agent is marked as On Holiday/Sick in Halo, if a User replies back to a ticket the ticket remains with the Agent that is on holiday meaning a lot of manual intervention is needed to check and move tickets. This feature idea is to have a setting/configuration option that would allow a ticket to move to Unassigned when a User replies back to a ticket 'On Hold' or 'In Progress' where the Agent is On Holiday/Sick. I don't think there is currently another way of achieving this (e.g. via rule) - and have checked this out.

    Paul U

    7

  10. Dashboard Only Agents

    Have the ability to create Dashboard Only Agent for Interactive Displays Similar to API Agent.

    Connor - EZPC Halo C

    5

  11. Allow "Holiday" event types to sync to 365 Calendars

    It would be good if the "Holiday" event types synced to Exchange calendars with Microsoft 365. As it stands the "Appointment" event type synchronises to calendars, but holidays do not.

    Ollie T

    19

  12. Merge sites

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

    Andreas H

    0

  13. Ubiquiti Unifi Controller integration

    we use the Unifi Hardware stack for most of our networking as the controller for this is free and doesnt require a subscription. this controller uses standard Rest api to collect information. (www.ui.com) I have currently created a powershell based integration that collects all sites and hardware from the unifi controller and updates them via api in Halo. However, due to api throtteling this process is quite prone to error. It would be realy nice to have this as a proper integration. This api is Documented here: https://ubntwiki.com/products/software/unifi-controller/api

    Marco

    22

  14. Treat merged tickets as one (Hide from closed view)

    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.

    William Hilsum - E

    5

  15. Timesheets - Time Entry - We're in the 21st century and not the 1980s

    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.

    Timothy W

    2