Feature Ideas

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

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

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.

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.

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

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

The HTML editor chosen for use across HaloPSA lacks and has a terrible time copying data from Word Docs. I would love to see an improved or replace HTML editor across HaloPSA, especially in Knowledge Base Articles.

I would like to change the favicon that is shown on the customer portal – right now it’s the red haloPSA favicon which doesn’t match our color scheme at all. Replacing it with our own custom icon preferred, alternatively the ability to set a HEX color code for the existing icon would be a 2nd option Also when going to our portal the loading circle is blue at first, and then changes to our green, is there any way to fix that? Right now the favicon is red, the initial loading circle is blue, and then finally things change to green, which is a pretty bad mis-match of colors Additionally, it would be great to have the option to repeat a background image vertically, right now we had to make a fairly large image in height to have it work on every possible screen/mobile device, but the caveat is that the background image takes a second or two to load in. If we could just have it repeating on the Y axis that would solve the problem, but I was told that it's not possible, even by custom CSS at this time.

Would be great if we could alert on M365 service health - https://learn.microsoft.com/en-us/graph/api/resources/service-communications-api-overview?view=graph-rest-1.0&preserve-view=true

There are multiple places in Halo where it is possible to navigate away from a page without saving your changes. Ideally a warning message should pop up indicating that "you have unsaved changes, would you like to continue". For example, we found out the hard way that it is possible to edit an invoice (i.e. add new line items) and hit send invoice to the client. If you did not hit Save at the invoice level (not the line item level), the PDF sent to the client does not include the changes. There are also inconsistencies on which pages require hitting the save button and which automatically save. Finally, the save button is not in the same location on all screens. Often it is placed at the bottom of the screen and may not be visible when editing a field at the top of a page.

When you use Azure AI translation on the agent portal to translate a communication, the translation is stored somewhere in the database. Therefore, later on when you ask for a translation of that same communication, Halo doesn't send out an API call to Azure AI translation again but fetches the previously stored value out of the database. On the Self Service Portal, this isn't the case. Either the translated communication isn't stored in the database, or the fetch doesn't work. In the end, doesn't really matter, but the problem is that every call for translation triggers a new API call to Azure AI translation. Which is causing waste (unnecessary api calls + extra costs). Therefore it only seems fair that the working mechanism for the agent portal is also applied for the end-user portal.

When a ticket is created automatically from an inbound email, HaloPSA appears to retain the mailbox that generated the ticket as the sender address for outbound communications. Currently, the Mailbox Override configured on the Ticket Type is only applied when the ticket is created manually. As a result, tickets created automatically may send outbound emails from an unexpected mailbox, even when a Ticket Type Mailbox Override is configured. Example Ticket Type: Supplier Notification Ticket Type Mailbox Override: support@company.com Ticket created automatically from mailbox: notifications@company.com Expected behavior Outbound emails use the Mailbox Override defined on the Ticket Type (support@company.com). Current behavior Outbound emails continue to use the mailbox that created the ticket (notifications@company.com). It would be very useful to have either: The same Mailbox Override behavior for both manually created and automatically created tickets. An option to force the Ticket Type Mailbox Override to take precedence regardless of how the ticket was created. This would provide a consistent sender identity and simplify scenarios where incoming and outgoing communications need to use different mailboxes.

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 helpful to have an integration with Docusign so that we can create a quote within HaloPSA and have it send out through Docusign when we go to send the quote. Then, it would need to sync back the status of the signature, as well as the signed document once all parties sign the document.

For us, being new to HaloPSA, one of the things that frustrated us the most was the lack of good documentation when it comes to integrating with the system. It would be nice if this could be improved a ton, as we now have to try and reverse engineer how the system is set up to do.