Feature Ideas

Ability to customise the “Overview” tab of the customer: ---Ability to Show Fields / CRM Information on the Overview tab of the customer. ---Custom Fields such as customer grade, system fields such as next call date. ---Account Manager Name ---Importance level

Today it is possible to order users by the following: Username Main Contact, Important, General User, Username Rank It would be helpful if the following option was added "General User, Main Contact, Important, Username". This makes it a lot easier to find General User when a customer has a lot of important contacts. It would also be useful if admins could order the following "General User, Main Contact, Important, Username" in any order, but this is probably more complex to implement and I therefor recommend adding the option "General User, Main Contact, Important, Username" first.

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

Want to send invoices that are unsent after reviewing them? Well, get prepared to tick 250 really tiny boxes and hope none of them fail to send otherwise you'll have to do it again. You should be able to filter invoices by their creation date. Likewise, you should be able to filter the sent column and enter NULL or "" or 2 to show all tickets with more than 2 hours on them. On the client screen, I should be able to filter the next call date by entering

Please make it possible to configure what fields should be shown in the customer user details page. For example, we do not need a Home Mobile Number or a Fax Number for our customers. It would be very useful it that fields could be hidden.

We support customers of nearly a dozen types and just came from Connectwise where it was extremely easy to identify the type of customer that they were. Now, in Halo, we are completely lost. We've defined Customer Types and Customer Relationships, but they are buried in tabs and are not able to be added to lookups, filters, etc. It is EXTREMELY frustrating. We feel like we've gone back in time 10 years in the ability to slice and dice our customer list. As it stands right now, there is absolutley no way to look at the service queue and identify the type of customer without opening the ticket then search and scroll.

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

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.

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.

When we schedule engineers and they finish their appointment that require them to email the user for follow up information, the ticket goes on hold but if the appointment is not closed first Halo puts the status of the ticket back to in Progress. This leads to tickets that go into a stale status for us. It would be nice if their was a setting that if the ticket goes into a specific status it would close the appointment or give an option to remove the linked status of the appointment so the ticket can change status based on the work of the engineer. I have tried an action that closes the appointment and sends an email as a workaround but if the action is done outside of the scheduled appointment it does not close the appointment and the status flips back.

Currently, Halo PSA places the Alert Description that's sent over API inside the summary of an Auvik alert. The Alert Name is also delivered over the API payload, but isn't used in any way. Since the Alert Description is meant to guide engineers in their troubleshooting, even descriptions on default alerts sometimes get too lenghty and don't fit into the Summary of a Halo ticket... Idea would be a Summary and Description customization field inside the Auvik integration page, where we can customize the content of Auvik alerts by utilizing variable placeholders ourselves. That way we have full control over this and can customize the look of alerts ourselves.

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

I would like the option to add a user to multiple sites. we are a school society with 24 schools and have users which work on multiple schools.

The ability to do some advanced filtering on all table/tile overviews and bookmark these views. Example below: Field starts with "value" AND / OR Field !contains "value"

Our HaloPSA instance currently has many imported phone numbers (for sites and users) that contain no formatting and are pretty hard to read as a result. This proposed auto-formatting feature would allow for phone numbers to be automatically cleaned up to conform to a specified format when displayed. For example, "1234567890" would become "(123) 456-7890". Additionally, it looks like HaloPSA stores phone numbers as text (strings) rather than as an actual numbers (integers). Instead of storing phone numbers as text, perhaps HaloPSA could automatically take formatted phone numbers and convert them to raw format-less numbers/integers. This would improve data-efficiency & would standardize the format in which phone numbers are stored. This would make it significantly easier for an auto-formatter to format phone numbers as they're being displayed.