Feature Ideas

When logging in, please automatically put the cursor in the text box of the MFA prompt. If it matters, I'm using Firefox with uBlock Origin and password manager plugins.

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 :)

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.

Would love to see a schedule send button when emailing customers. This would be very useful for people who work outside of the normal business hours and send replies to tickets without the client thinking they are open during these times.

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

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

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

We use @mentions frequently when assigning tickets, following up on tasks or asking questions internally. Having a way to Aknowledge or "Complete" an @ mention without responding would be helpful. e.g., Manager assigns ticket to agent, then leaves @mention with breakdown of task. Agent Aknowledges the @mention action inside the ticket. Manager knows agent has confirmed reciept. It would be helpful to have a signifier inside the ticket grid view- similar to flagged or starred or attachment icons - to designate tickets w/ unaknowleded @ mentions, that way agents/managers could track tickets with unaknowledged @mentions. Using status for this would be tough because those are tied to end-user and SLA requirements, not intenral coordination.

We can set Advanced Settings > Default Editor Font but not the size. We need the default size to be set so everything in Halo is always set to the same font and size (email templates, pdfs, notes,etc.) Support was unable to find a solution for this.

Currently, Halo's email threading functionality (In-Reply-To / References headers) is only compatible with Microsoft/O365 mailboxes. Customers using Google Workspace, and particularly those using third-party email clients such as Front, receive every ticket update as a new email thread rather than as a reply within the existing conversation. This creates a poor customer experience - a single ticket can generate 10-15 separate email threads, making it difficult to follow the conversation and cluttering inboxes unnecessarily. Request: Extend email threading support to be compatible with Google Workspace and widely-used email clients such as Front, ensuring that outgoing ticket updates are recognised as replies within the existing thread regardless of the recipient's mail platform. Impact: Affects MSP customers and end users who use Google Workspace as their primary mail environment. Currently no viable email-based workaround exists for this combination of platforms.

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.

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.

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.

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

We currently have the chat facility accessible via the Self Service portal however most of our clients do not use this as they find it easier to contact us via email. It would be a game changer if Halo could have a desktop feature where a 'Tray Icon' can be placed on the users Task bar and when expanded, quick access to a few frequent options could be accessible. For example: 'Log a ticket', 'View my tickets', Chat to an Agent', Knowledge Articles' etc. With end user experience in mind, it would be great for users to engage directly with our team rather than the tradtional email process. This would boost turnaround times as well as customer satisfaction. Attached is an example of another MSP software platform where there desktop tray icon is available.