Feature Ideas

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

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

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

  3. Variable: ticket history of all public, non-system actions (without exposing internal action names/status) in conversation-style for email

    Problem: AFAIK there is currently no reliable way to embed a clean, user-friendly, conversation-style history of a ticket into an email or notification template also without exposing internal action names/status What We've Tried (And Why It Fails): $EMAILHISTORY: specifically the actions that truly sent an email; not even SMS via twilio or other forms of comms are included which seems to be driven off the "outgoingid": not being -1 and instead being linked to an outgoingid which seems to only apply with emails AFAIK$RICHALLACTIONS: not conversation-style; includes internal action names/status (don't want that); and worse it often breaks formatting creating tables in tables (note we use GMail) when the notes include even basic rich formatting$ALLNONSYSACTIONS: similar to above, but notably this one doesn't break with rich formatting... The "Print Ticket" function suggests the system can already gather the correct, complete data, using the variable: $ACTIONLISTCONV. We need a variable for email templates that combines the complete and accurate data of $ACTIONLISTCONV with the clean, threaded, user-friendly formatting of $EMAILHISTORY. Use Cases & Business Value: This would allow us to: Update Clients: Provide a full summary they can actually read without exposing internal action names/statusEscalate to Vendors Send Closure Notifications: Give the user a complete and accurate record of the entire interaction, building confidence and reducing follow-up questions.

    Adam

    3

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

  7. Integration with 1Password (or Password Manager of any sort)

    I think it would be really beneficial to have Customer passwords be accessible directly within the Halo UI, if I could click on an asset and be given a password with that name, it would save me and my engineers loads of time...

    Jacob N

    3

  8. Ability for end-users to filter the report from the service portal

    It would be a very useful feature for end-users to filter reports from the service portal.

    Miguel S

    1

  9. CSS customization on agent side

    I would really enjoy having the possibility to add custom CSS to the agent portal. It would allow us to customize colours and personalize the appearance in order to adapt it to our business needs.

    Olivier L

    4

  10. Full HTML/CSS customization of the Self Service portal

    Current state The Self Service portal currently supports CSS overrides via the configuration settings. While this is useful for basic brand alignment (colors, fonts), it is limited to style adjustments on top of the existing portal structure. The underlying HTML cannot be modified, which means the layout, component hierarchy, and DOM structure are fixed. Requested improvement We would like the ability to fully customize the Self Service portal at the HTML level — either by editing the underlying templates directly, or by providing a way to inject custom HTML blocks alongside the existing CSS override functionality. Ideally, this would allow us to rebuild the portal layout entirely from scratch while still leveraging HaloPSA data (logged-in user context, ticket lists, asset data, etc.) through available template variables or data bindings. Specific capabilities requested Edit or replace portal HTML templates directly, not just overlay CSS on top of the existing structureControl over the layout structure, header, navigation, content areas, footer. Without depending on the default component hierarchyAccess to Halo template variables in custom HTML (e.g. current user name, company, ticket count) to enable dynamic, data-driven layouts Business case MSPs operate across multiple customers with different branding requirements. As it stands, all customers share the same portal structure, only colors and fonts can be differentiated. Full HTML/CSS control would allow us to deliver a genuinely white-labeled experience per customer, improving portal adoption and customer satisfaction. It would also allow the portal to be redesigned to match modern UX standards rather than being constrained by the default layout.

    Jesper V

    1

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

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

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

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

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