Feature Ideas

It'd be great to have a way to conditionally display an "Allow Action" in a workflow step. For example in Step 3 if CFParcelType = Delivery show action Make Collection and if CFParcelType = Collection then show action Make Delivery Currently the only way to do this is to create an extra "decision step" and then you have to duplicate your step so that one step has the "Make Collection" action and the other has the "Make Delivery" action. The problem is, when you have 3+ actions in each step, and your one action is the only difference, it's a lot of work to replicate the actions. You already have the "Conditions to evaluate prior to queuing the automation" for "Quick Action". This just needs to be replicated for "Allow Action".

Currently, if you want to clone a step in your workflow that has several actions/rules, you have to create a new step and manually add everything in again. It would be create if going in to edit a step, then gave you a "clone" or "duplicate" function.

Currently it appears that change freeze schedule collision detection is only done on the initial creation of the change request ticket. This leaves a huge gap as when/if the change schedule is modified on any occasion after ticket creation (eg via action button or ticket details modification) Halo does not check or alert, meaning that changes can and do get scheduled during identified and configured change freeze periods. A big part of change management is to confirm/adjust the change schedule as appropriate so this leaves a really big gap in what on the surface is a great feature with change freeze periods. This change freeze / collision detection really needs to be done on any update to the change schedule, not just on initial ticket creation.

add recalculate billing button to the ready for invoicing labor area, this would allow a final recalc of only those specific tickets that possibly had their contract changed

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 great to get an upgrade to the ALSO integration. We could really like to see start/end date and cost/price fields beeing updated through the integration.

The Goal Enable a full two-way sync of projects and tasks between HaloPSA and Galactic Advisors for both our company and clients. This would allow us to manage all project and task activities within HaloPSA while leveraging the robust security capabilities of Galactic Advisors. The Problem We use Galactic Advisors for security oversight, including built-in projects and tasks. Managing these separately in both Galactic Advisors and HaloPSA leads to fragmented workflows, redundant data entry, and potential oversights. The Solution Implement a two-way integration between HaloPSA and Galactic Advisors: Two-Way Sync: Automatically synchronize projects and tasks between both platforms. Real-Time Updates: Reflect changes in one platform immediately in the other. User Mapping: Align users and permissions so tasks are accurately assigned and tracked. Unified Notifications: Consolidate alerts and status updates, reducing communication overhead. API Utilization: Secure, efficient data exchange using available APIs from both platforms. Benefits Efficiency Gains: Reduces manual data entry and potential errors. Centralized Management: Simplifies workflow by allowing teams to operate primarily in HaloPSA. Enhanced Security Oversight: Integrates security tasks into our main PSA workflow for improved tracking and compliance. We believe this integration would significantly enhance HaloPSA for teams who rely on Galactic Advisors for security management, making it easier to track projects, allocate resources, and maintain alignment across both systems. Thank you for considering this feature request. We’re available to provide any additional information to facilitate this integration.

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.

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.

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

Allow tickets, contacts, Customers, Core + Custom Assets, Sites/Locations and most importantly: Primary Location Important contacts Also, push list of agreements to quick notes, if possible to be 2 way sync

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.

currently there is just the yellow star, it would be great to have more colors and icons

We need a feature to improve how recurring invoices handle new license types coming from the CSP. Right now, the system automatically updates the license count from the CSP on the customer record, and recurring invoices use this count when they are created. However, if a new license type is added to the customer’s record, it doesn’t automatically appear on the invoice, and it has to be added manually. The new feature should allow recurring invoices to automatically include new license types from the CSP, with an option to review the changes before the invoice is finalized. This ensures accurate billing for all licenses, including new ones, while giving the user control to confirm the invoice details before sending. This approach would streamline the process, reduce manual effort, and maintain accuracy in billing.

Timesheets in bulk are difficult to manage, and the views over a month are too much, even weekly having a team of 15 and a single timesheet manager, it becomes chaos and borderline pointless, often just hitting the final 'approval' button that does all at once for that date period. Not show weekends when viewing a month/only show working hours/days as a viewFilter by approved/unapprovedNotifications when timesheets submittedMultiple timesheet managersRejection comes from the timesheet manager, not the Helpdesk email addressTrigger warning when 'approving all' to warn that all items are about to be approvedFreeze the name and date column/row so the engineer's name and date always stay visible.Billing is typically done monthly, so the option to just view that month/week would be amazing, not having to select start and end date, and then re-select the date range because clicking 'next' retains the days selected, ( for example 28 days selected, clicking next will select the next 28, not the entire month if there are 31 days)