Feature Ideas

Just like using the @ in a ticket will bring up the ability to reference a user I would like to see similar ability to reference another ticket ie.. @ticket# or something like this which will make it a hyper link.

It would be great to have the option to set 'Other attendees' as blank by default when creating an appointment. Currently, it auto-fills with ticket users, leading to accidental booking notifications if not manually removed.

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

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

The xero integration currently makes a webhook call to Halo on allocation of payments. Halo ONLY records payments made in full leading to SIGNIFICANT divergence between the balance of un/part paid invoice in Halo compared with Xero. The impact on Account Mgmt staff in needing to access BOTH systems for invoice management is considerable. Considering that the webhook calls are already made by Xero and Halo already responds and correctly records full payments, extending this to cover the recording of partial payments would be very much appreciated and deliver considerable time savings and improvements in the accuracy of reporting on invoice states/balances within Halo.

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

Have the ablility to create a recurring invoice template which can have all line items added but only bill/show on the invoice where they is a quantity. Also in the template have the Quantity being able to be set by Assets / Licecnce / User / Subscription The Idea behind this if we add a new product to the customer "office365 E3" Licence via Pax8 we dont need to go and add the item to the customer.

We would like to request enhancements to the customer grouping functionality in HaloPSA to better support customer–reseller relationships. Current Challenge In the current setup, each customer is managed as a standalone entity. However, many of our customers are part of a larger relationship where they are served through a reseller. This creates challenges when it comes to: • Managing billing (should go to the reseller, not always the end-customer). • Grouping and reporting (seeing usage per customer but also consolidated for the reseller). • Maintaining the end-customer’s own identity (contracts, assets, users) while still linking them under their reseller. Proposed Enhancement Introduce the ability to: Assign a parent organization (e.g., a reseller) above an top-level. Maintain the end-customer as its own entity with its own assets, tickets, contracts, etc. Enable billing to roll up to the parent reseller while still showing detailed breakdowns per top/child customer. Provide flexible reporting both per customer and at the reseller/parent level. Benefits • Better reflects real-world business structures between customers and resellers. • Simplifies billing workflows (one invoice to the reseller, with optional breakdowns per customer). • Increases flexibility for MSPs managing both direct and indirect customer relationships. • Enhances reporting and visibility across multi-level customer structures.

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

I have so many canned texts that the scrolling is unbearable, please can why have a way to search and organize them into folders like the categories field?

I would love to see the ability to have a "click here to pay" on Invoices that goes to the Customer Portal and allows them to do One-Time Payments (as well as update their billing/ stored credit card). I can see the manual pay on the Agent side, but not the user side. Additionally, Add the ability to "sync" the Invoice Payment Link from Quickbooks into the outbound email or the "Bank Details" section of the Invoice. Either one of those options (or both) would be HUGE improvements for the Accounting/Billing/AR side of things.

We love to do's, helps promises or checks and balances to not get missed. Functionality is a little limited, we'd love to see the option to break it out to a Tab with a little more room to work. Perhaps a rich text etc.

Similar to user roles, have a concept of Customer roles. This can be used to show hide tabs from the customers record, as well as act as a permission set for the customer portal and ticket types. e.g a "Security/SOC" customer, can have extra customer portal functionality and ticket types granted.

Trying to match color codes to matching status tags, or any other kind, so that charts can accurately represent their demographic instead of using random colors that do not correspond to the charts. The random colors can cause confusion for what other colors are actually used to symbolize on the service desk. Current color code settings only allow for a designation of what colors the chart should use but not how they are assigned, leaving colors to be assigned in order but not by designation. So if a ticket with a specific designation is missing, it assigns the colors incorrectly.