Feature Ideas

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

Trending
  1. Make every configuration setting searchable

    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

    Phillip B

    2

  2. one user at multiple sites

    I would like the option to add a user to multiple sites. we are a school society with 24 schools and have users which work on multiple schools.

    gert.vanderstappen@agora.nu

    8

  3. Pause Timer when Halo Tab is idle / Only run timer on active Halo Tab

    Currently my team opens up Mutiple tab's when viewing tickets, they are manually pausing the clock between tabs'.

    Mark S M

    2

  4. Microsoft Copilot Connector

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

    Craig M

    19

  5. Email delays

    We currently use Outlook rules where it can add a two minute delay to sending. This helps if, in the unlikely event, an officer has sent an email to the wrong place. Please can something similar be added to HALOITSM if possible when sending an email?

    Benjamin S

    2

  6. Knowledge Base, One URL per article with previous versions stored within instead of each version being a different URL #

    We have saved links to articles or have articles bookmarked. Because each version is a unique URL, our bookmarks link to outdated articles. There is a "new version" button that shows on the top but it would be simpler to have one URL per article. We tested setting old version URLS to "inactive" but this would hide the "new version available" button on the top further misleading our techs. We do not use the Edit button because there is no approval process on changes AND there is no version / change log with the Edit button. If you delete or make a bad change then save with the Edit button we cannot undo or see who made the change.

    mark n

    0

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

    34

  8. Single Sign On for Ideas and Support Portal

    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?

    Andreas S

    3

  9. Every view needs export to CSV/XLSX

    Every view is useful and that's why you added all these views. Unpaid invoices, sites & users for a client, etc. Why can't I export them? We all agree they are very useful and concise collections of business data, but we're limited to seeing 50 rows and we can't export it. It's useful! You know it's useful! You put it in the application! Let me have the data! Thanks

    Eric R

    3

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

    16

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

    5

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

    20

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

    4

  14. Holidays approval process configuration

    It would be nice to configure approval process for holiday requests from agents. Now, agent's manager receive approval request only. For specific roles in company we need to receive approval from two approvers to accept holiday request. Also some approvers are not the same person, who need to see timesheets of the team agents. But the agent's manager is the only one who have ability to see timesheets of the team and have ability to approve a holiday request.

    Branislav K

    2

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

    2