Feature Ideas

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

The call handling screen is great But I'd like the ability to create a 3CX Call Flow App where the call history is recorded directly against the customer/site/contact if using a DID Also need to be able to log this to the agents timesheet, overlaying the activity of thr agent. This call history should optionally be used for billing clients who are in Pay as you Go. Clients make many calls, at times without needing a ticket. This should be billable depending on the clients contract etc If a ticket is overlapping the time period of a ticket assigned to the customer, and for the same agent on the call, then we should be able to choose what time logs to bill on I have lots of calls with customers while traveling, I cannot open a ticket while driving, and I would forget to log the time at the end of the day. This could a significant loss of revenue.

Similar to the Automatic Billing Delay (and maybe replacing this feature request?) the Invoices have a status of DRAFT or SUBMITTED or AUTHORIZED that syncs to the accounting package such as Xero and others. If we set the invoice to DRAFT then we have to manually review the and approve invoices in Xero before they "go live" Expand on this to create a method inside HaloPSA to review and move invoices from DRAFT status to Submitted (and make sure Stripe and others only bill once the invoice is no longer a draft) allowing for checking and correcting of invoices in advance of the actual billing

Would like to see an integration with Huntress. Amazing product and being able to receive tickets directly would be very useful.

Would like the ability to map asset types in Ninja to asset types in Halo. For example, in Halo all our current assets and items are filtered where asset type is called workstation or server. However, Ninja brings servers across as Windows_Server. This means we have to go and update all our reports as well as all our items where the quanity is mapped to device name is server.

Add the ability to organize actions into groups in tickets. This could be accomplished with either drop-down menus with multiple actions or with brackets with actions tied to that group. Make it where we can name the group anything. An example would be having 4 Escalation actions; Escalate to Tier 2, Escalate to Tier 3, Escalate to Sales, Escalate to Manager. Most of those are not needed that often. It would be nice if there was a way to put them all together in one 'Action Group' that we could expand if one of those actions is needed.

I know Halo say they have various backups and DR plans in place, but it's not good practice to solely rely on any one company to protect your vital data. Please implement a bulk export or database dump feature that can be scheduled to give us access to our data, should a disaster occur.

We desperately need the functionality to have a minimum charge calculated by the total ticket time, vs each individual time entry & via the charge type. For example, we have PAYG clients with a minimum charge of 1hr. Currently, charge types have a minimum minute amount, but if this is set to 1hr and multiple time entries are added, it results in overcharging clients. So for instance if there are 3 time entries on the ticket, 15 mins, 5 mins and 20mins. We want the total billed time to be a minimum of 1hr, currently it would be calculated as 3hrs.

would be nice to add clock-in/out with location tracking in mobile app for payroll purpose

there should be an option / trigger that the notification trigger also executes for additional agents.

Allow filtering of kanban boards by various fields such as client/assigned agent etc.

We heavily use to-do's as a way of creating checklists on common steps. However, a lot of our clients require unique custom checklists. We use IT Glue currently for this and it allows not only a to-do, but it allows that to-do to be expanded detailed steps (written in HTML). What I would like to see is the following To-dos have their own tab in tickets and not just a sidebar. To-do's can be expanded to show links or steps (See screenshot of Glue) To-dos once completed hide from the list To-do's that can be associated with a client site and be templated To-Do templates can be grouped

Have a secure way of sending passwords to Customers. Via a button in Halo, where you'd type in a password, it'd generate a secure link and embed it into the body of the email - then when the user clicks on the link, they are prompted to enter the ticket number for it. Or are forced into an area of the portal to retrieve the portal. Something like the attached maybe as options

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

Have the ability to send overdue invoice reminders to customers based on a specified timeframe.