Proper Pax8 Integration
Currently, the Pax8 integration is just set up with the Pax8 API and pulls down some data. There appears to be a way in Pax8 to have a full Pax8-supported integration. For example, in Pax8 they have Auto Sync with PSA support for Syncro, Autotask, Connectwise, and RepairShopr. I understand that if the Halo integration were setup this way it would allow additional data o be pulled into Halo. For example, we buy a cloud printing product called Printix through Pax8. This isn't a normal subscription that is setup under a client though. Printix shows up under our account in Pax8 and then pulls usage daily and bills the assigned customers. If you look under those customers, it does not show Printix at all. So this data does not come into Halo. I was told that if the integration was setup as an Auto Sync it wold pull this data in.
Nick F#Misc 🤷#Billing 💰#Integrations 🔗5
Quotes and Order, Invoices, and Products Columns
The inclusion of personalized column profiles in crucial areas like invoicing, quotes, orders, and products would provide significant advantages for the Admin and Accounts teams. This feature enables them to optimize these sections according to their specific needs, ensuring that the most critical information is readily visible and easily accessible.
Elisha S#Misc 🤷#Billing 💰#Quotes & Orders 📄2
Allow Approval Processes to Target Agent Roles
Currently approval processes only let you define approvers based on user role, not on agent role. For internal approval processes this would be useful as I'd like to configure a simple RBAC configuration system where I can assign new staff to an agent role and have all their access and permissions based on the agent roles they hold. Having to set up roles in multiple locations, or setting up CAB's manually every time there is a staff change is going to be a lot more error prone.
David0
Time deductions from time entries
When entering time at present It must be one contiguous block that is either all billed or all not billed. Depending upon global settings it can be defined by a duration and end time, or by start and end time. But there is no way to account for other overlapping time entries. A time-tracking field that lets you enter an amount of time to deduct from a time entry without changing the start and end times would allow for this and avoid a lot of tedious small time entries. For instance, a servicedesk tech working on one matter (ticket A) gets interrupted by a call (ticket B). They handle the call, make a time entry for that, and return to the first task. In the current system, they will end up billing the duration of the call to both tickets A and B unless they make separate time entries for ticket A before and after the call (ticket B). Importantly, this gets a lot worse when that agent is interrupted more than once. With a deduction field, the tech makes their time entry for ticket B when they take the call. Then when they make their entry for ticket A, they enter the correct start and end times and then take the duration of ticket B and enter it in the deduction field. The number of time entries required to bill (or not bill) all time correctly reduces a lot and ticket notes are simpler and more readable. On top of that, an option to automatically deduct the duration of overlapping time entries would make this super simple. This could be a button or checkbox next to the deduction field that automatically calculates the deduction upon request.
A B#Servicedesk 💁🏽#Billing 💰0
Configurable Option to Mandate 'Time Taken' for Appointments
I would like to suggest having a configuration option to make the 'Time Taken' field mandatory on appointments in HaloPSA. This update would be highly beneficial for ensuring accurate billing, especially for teams with field service technicians who may occasionally overlook this field. Currently, missing entries can lead to incorrect invoicing, which requires manual intervention to fix. By implementing this change, HaloPSA could help avoid such errors and save time by adding an option to mandate a critical part of the billing process, benefitting users who rely on precise time tracking for invoicing and payroll.
Kerry K#Servicedesk 💁🏽#Billing 💰1
Better HTML Editor
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.
Josiah S10
Multiple suggestions for projects module
Projects need stages to group tasks Tasks need to be ordered No way to bulk slide task dates if there is no date to start with. Calendar view needs to be more interactive, drag/drop tasks, etc It would be nice to see all notes on child tickets at the parent level. ...in other words, I should be able to look at the top level project and see a summary of all the notes/conversations that are happening on each task.
Luke P#Project Management 📒11
Ticket Rules - Change Ticket Type
Have the ability to change the Ticket Type on Ticket Rules.
Connor - EZPC Halo C3
Merged status to reflect tickets closed via Merge
It would be very helpful to differentiate tickets that are closed via the merge action via the ticket status. I.e. tickets closed via merged should reflect "merged" as a status whilst still taking all the same action towards the SLAs for reporting that the current close action is taking. This would give far greater flexibility and insight whilst reporting.
Stewart K#Servicedesk 💁🏽5
Automatic prorata recurring invoices
It would be great if when adding a recurring item to a recurring invoice, you could select a start date for that item and have the prorated cost & price automatically calculated based on the items start date/active days for the invoice period. I.E: If the invoice creation period is 01/2 - 28/2 and an item is started from 5/2, the prorated cost/price will be shown on the following invoice.
Tiahna M#Billing 💰3
Customer & User/contacts customisable columns views
Ability to control what is visible on the front pages of these areas - similar to column views on tickets. currently you can not chose what information is presented here - so mobile number email address etc etc...
Rob C#CRM/Opportunity Management 🤑4
Ability to accept contracts like you can with quotes
Ability to send and accept contracts/agreements digitally like you can with quotes
Martin L1
Being able to edit and filter invoice list colums
As for the tickets view, it would be nice to select the columns we want to display in the invoices list. Being able to sort and filter information by colums content.
Salvador F#Billing 💰1
Users that have portal access
Visible fields on User record to determine what users have access to the self service portal, and last time they logged in. Currently only visible via a custom report.
adam#Self-Service Portal 🌍1
Customizable Items Columns
How is it that I can't edit /update columns shown for a top level table in Halo? Being unable to edit columns for all the top level columns is ridiculous. Relax with the random integrations and spend time fixing the basics. This "feature" isnt even in the roadmap as of today.
Richard R#Billing 💰#Asset Management 💻#Stock Management 📈0