Feature Ideas

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

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

    13

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

    38

  3. Exchange Online calendar inbound sync should not use the "User Update" action

    When two-way calendar sync is enabled with Outlook calendars of agents, and the calendar item of a Halo appointment in Outlook gets moved, this also updates the appointment in Halo. That's great, but this update: Creates an entry in the ticket, which preferably should be a toggle in the first place;But the worst thing is that this entry uses the User Update action, and not a eg. a dedicated "Appointment Update" action. Because of this odd behaviour, notification flows towards the end user can get triggered without it being the intention of the engineer / planner / service manager that updated the appointment in Outlook. We have a flow that alerts all recipients on a ticket when any user replies to the ticket (is a logical flow when working together with internal IT teams), but this notification gets triggered now due to an appointment shift in the agent's Outlook calendar, causing weird superfluous notifications to all recipients in the ticket... Halo told us this is intended functionality... Our opinion differs, but anyhow - here's the feature idea :)

    Niels B

    0

  4. Add Anthropic (Claude) as an AI Engine option

    Allow HaloPSA to connect to the Anthropic API so Claude models can be selected as the AI engine, alongside the engines already offered. Customers would enter their own Anthropic API key under the AI integration settings and pick a model (e.g., Sonnet, Opus, Haiku) for the existing AI features β€” ticket summaries, suggested replies, categorization, knowledge-base drafting, and any other place Halo calls an AI model. Same settings surface as the current engine options, just a second provider behind it. Reason: Choice of provider. We already standardize on Anthropic for our own tooling and have the account, keys, and usage policy in place. Being forced onto a different provider just for Halo means a second vendor to approve, pay, and govern.Data governance. Our customers (and our own security posture) require that we know and control which AI vendor sees ticket content. Keeping Halo on the same provider we've already vetted keeps that story simple.Quality and cost. Claude models are strong on long-context summarization and tone-matched customer replies, and the pricing tiers let us pick a cheaper model for routine classification and a stronger one for customer-facing text. Locking the engine to one vendor removes that lever.It is a thin integration. Anthropic's Messages API is a simple HTTPS call with a key header and a messages array, so this is adding a provider adapter, not a new feature set. Impact if not added: MSPs who have standardized on Anthropic either skip Halo's AI features or run a second AI vendor just for Halo.

    Ross P

    0

  5. KB usability: clickable tags, synonyms, failed-search reporting and better navigation

    Our agents struggle to find articles in the Halo Knowledge Base. Search often returns many unrelated results, tags can be searched but not clicked or filtered, and it is hard to tell where an article sits in the FAQ list structure. The following improvements would make a major difference for any team that relies on the Knowledge Base daily: Clickable tags – Clicking a tag on an article should open a list of every article with that same tag. Tags should also be available as a filter on the search results page.Synonyms list – Allow administrators to define words that mean the same thing (for example, "MFA", "2FA" and "multi-factor"), so a search for one term also returns articles that use the others.Failed search report – A report showing what agents searched for that returned no results, or where they opened no article. This would show Knowledge Base owners which articles are missing or poorly titled.Search within the selected FAQ list – When an agent has an FAQ list or group open, the search should only return articles from that list, with an option to search everything.Better result filters and ranking – Allow filtering results by FAQ list, tag, author and last updated date, and rank articles whose title matches the search above articles where the match is only in the body text.Breadcrumb – Show each article's FAQ group path at the top (for example, Knowledge Base > Microsoft 365 > Email), with each level clickable. Favorites and pinned articles – Allow agents to save favorite articles, allow administrators to pin key articles to the top of an FAQ list, and show a "Recently updated" list on the Knowledge Base home screen. Many dedicated documentation platforms (such as Confluence, Document360 and Zendesk Guide) offer these features as standard. Having them in Halo would let us keep all documentation inside Halo instead of relying on a separate tool.

    Jafet

    0

  6. Option to Set Calendar Sync Availability Status (via Graph API)

    When Halo appointments (such as ticket reminders) sync to Outlook calendars via the Graph API, they are automatically set with "busy" availability status. This prevents Microsoft Teams Phone from ringing when technicians receive calls, as Teams respects the "busy" calendar status. It would be good to have a configuration option to control the availability status for appointments synced to Outlook calendars through the Graph API. Specifically, we would like the ability to set appointments as "free" instead of "busy" by default. My understanding is that the Graph API has a showAs property that can be used for this, to set statuses as free, tentative, busy, etc. This could perhaps be implemented as both a global setting for all calendar synced appointments, as well as a per appointment type setting.

    Ollie T

    3

  7. Click to Edit Field

    Instead of having to click edit and save every time you want to just change one field, it would be great to be able to just click into that field to update the value and when you click out of the field, it saves the information. Other systems like Zoho offer this.

    Marc B

    0

  8. MCP runbook tools: make the calling agent available to the runbook

    Runbooks exposed as MCP tools ("Execute a Runbook") receive the tool's parameters via , but nothing identifying who called the tool. Any Halo API step in the runbook (e.g. creating an action) is therefore recorded as "System", even though the MCP session is authenticated per agent via OAuth. Request: expose the calling agent to the runbook, e.g. / , or an option for Halo API steps to "run as the calling agent". This would let MSPs safely build custom MCP tools (sending emails to any recipient, multi-step ticket updates, etc.) that are correctly attributed to the agent who asked for them, instead of everything showing as System.

    Matthew S

    0

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

    30

  10. Further Portal Customizations

    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.

    Corey D

    16

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

    12

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

    13

  13. Pax8 integration - cancellation should cancel on recurring invoice

    At present if you change quantity of a Pax8 item using the subscription recurring billing method it will go up or down as expected. However if you cancel an item rather than go to 0 or remove itself from the recurring invoice it will stay at its previous quantity (whatever that may be). So you have to go and manually remove from the recurring otherwise face billing the customer for 10,20,50,100 licenses you have since cancelled. This is apparently not an oversight of the integration but as expected: "This design gives businesses the liberty to choose when to stop charging for the item." Smells like another unwanted manual step to me. What say you!

    Sam J

    8

  14. Quotes reminders

    Send email reminders to clients to accept or reject quotes before they expire and close.

    Gabriel L

    3

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

    17