Feature Ideas

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.

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.

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

Ever since we turned on Attachment scanning it is giving false positives for attachments. I have noticed this on msg and docx file types so fare and would like to be able to configure what is scanned/allowed.

In an action configuration there is a tab named "other uses" that shows where that specific action is used on workflows+ticket types. It would be great if this tab also included references to the action for all dependencies (E.g. webhook event triggers)

We would like to send notifications from Halo to Teams chat for agents (e.g. mentions etc.) but based on the Guides and our tests Webhooks only allow sending notifications to channels, not chat TeamsBot does not have the option to receive notifications

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.

At the moment, the status remains with "scheduled" or whatever is defined for after creating the appointment, when the customer cancels the appointment, the status should go to "cancelled" or similar status.

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

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

It would be awesome to have integration for Keeper password manager to sync the licenses into our customers license list. This helps with the invoicing for the customer.

Looking at a use case where items on a PO were received but the information was input wrong so they essentially need to be undone. I.e., cost/price, quantity, etc. It would be nice to be able to un-receive and un-consign to be able to edit the PO line item and re-receive the stock.

Currently only administrators have access to create scheduled tickets. Being able to grant ad-hoc access to agents to create scheduled tickets for their customer's might be useful. For example: A customer account manager could create scheduled tickets for the customers they manage.

Since a recent update we can open tabs within Halo, great! It would be nice to be able to move the order of the tabs.

A team can only have one registered Timesheet Approver, which makes absence approval a single point of failure. We'd like to be able to assign more than one approver per team. Current behaviour A team can have only one registered Timesheet Approver. The role cannot be shared across two or more people.If that approver is unavailable (for example on leave), no one else can approve the team's absence requests. Swapping in a different approver does not help either: because a request is tied to the approver at the time of submission, pending requests stay locked to the original approver and the employee has to submit a new request. Requested improvement Allow multiple Timesheet Approvers per team (or an approver group / role-based approval), where any of the assigned approvers can action the team's absence requests, including requests that are already pending. Why it matters With a single approver per team, approval stops the moment that person is away, and there is no clean way to hand requests over. For organisations managing many teams, including MSPs managing multiple customer tenants, being able to assign more than one approver keeps absence approval running without manual workarounds. This would also resolve a related auto-approval problem. Today, when a team has no approver, absence requests are auto-approved with no review, and removing a team's only approver silently auto-approves any pending requests. With two or more approvers assigned, removing one would leave the others in place rather than dropping the team to zero approvers, so requests would no longer be auto-approved unintentionally.