Feature Ideas

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

Trending
  1. Automatically add Client logo if their website is added

    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.

    Sam A

    7

  2. Time deductions from time entries

    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.

    A B

    7

  3. Ability to link assets to Opportunity tickets

    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

    Jeremy

    0

  4. Include additional agents in the ticket count

    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.

    Patrick M

    0

  5. Linking a ticket to another Ticket - Denote if the tickets in the list are Parent or Child tickets

    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.

    Andrew D

    0

  6. A working mobile app

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

    Chad H

    36

  7. Microsoft Copilot Connector

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

    Craig M

    36

  8. Drop and Drop email address between To, CC and BCC

    You can't easily move around the email addresses when emailing from a ticket. It would be great if you could drag someone from CC and drop into the To section without having to search for that user and delete the other one.

    Tony P

    7

  9. Outlook Plugin to update tickets

    It would be really useful to be able to write an email in Outlook and pick the correct ticket number from a list or search, add time in and then send to Halo through the normal copy in the mail delivery email address as usual. The reason this works much better is: a) People don't ignore direct emails from people in the same way as they ignore automated emails from a PSA system b) The formatting used is much better and doesnt break as with the current output from Halo(and you can paste in other items without the formatting getting screwed too) You could use the same mechanism to book in ticket updates, appointments from tickets and tasks/notes from tickets to work from.

    Rob D

    10

  10. 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

    7

  11. Notification of Emoji reactions to actions

    Add a notification option when someone reacts to your action using an emoji reaction. Right now the function is not as useful as it could be. This could clear a lot of small internal notes just saying someone agreeing.

    Ian

    3

  12. Option to select a category when one is not present on close of ticket

    When a category is not present Halo prompts to say there is not. You then clear the alert, add category and hit send again. Could the alerrt just come up with the category select field? Then the process is just select the category and hit send.

    Andrew S

    1

  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

    26

  14. 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

    23

  15. More than one Closed Ticket Status ID.

    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.

    Rob A

    20