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

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

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.

Have the ability for customers to type their name and auto generate a signature on the quote instead of having to draw a signature using the Mouse

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.

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.

Currently it can only be set globally or per agent

Currently you can only have one Closed Ticket Status. This doesn't really suit how we work as we sometimes Cancel tickets which are raised in error, where as any tickets which are brought to a successful conclusion are 'Resolved'. At the moment when we Cancel tickets, they still show in the User Portal under Open Tickets as the Status itself is classed as an Open status, not closed. We're using the only Closed status we have available as Resolved.

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

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.