Feature Ideas

Hello, On the New Call screen, (wether we select a end-user or the system could match automatically a end-user), we get a Dashboard displaying some field about any ticket related to the user who called. I am trying to add some fields, specifically for opened tickets of related site or client, not only the end-user related tickets as it is proposed out of the box. Thanks

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.

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

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

We currently have the chat facility accessible via the Self Service portal however most of our clients do not use this as they find it easier to contact us via email. It would be a game changer if Halo could have a desktop feature where a 'Tray Icon' can be placed on the users Task bar and when expanded, quick access to a few frequent options could be accessible. For example: 'Log a ticket', 'View my tickets', Chat to an Agent', Knowledge Articles' etc. With end user experience in mind, it would be great for users to engage directly with our team rather than the tradtional email process. This would boost turnaround times as well as customer satisfaction. Attached is an example of another MSP software platform where there desktop tray icon is available.

The call handling screen is great But I'd like the ability to create a 3CX Call Flow App where the call history is recorded directly against the customer/site/contact if using a DID Also need to be able to log this to the agents timesheet, overlaying the activity of thr agent. This call history should optionally be used for billing clients who are in Pay as you Go. Clients make many calls, at times without needing a ticket. This should be billable depending on the clients contract etc If a ticket is overlapping the time period of a ticket assigned to the customer, and for the same agent on the call, then we should be able to choose what time logs to bill on I have lots of calls with customers while traveling, I cannot open a ticket while driving, and I would forget to log the time at the end of the day. This could a significant loss of revenue.

I know Halo say they have various backups and DR plans in place, but it's not good practice to solely rely on any one company to protect your vital data. Please implement a bulk export or database dump feature that can be scheduled to give us access to our data, should a disaster occur.

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.

Direct password integration of passwords from 1Password to Halo PSA manage site passwords, agent passwords, and asset passwords.

I want to be able to select the type of automatic payment to apply to a contract or recurring invoice or disable the automatic payments on those items. For example, domains names we want to have a credit card on file for automatic payments, however we don't want to take payments over $5k for our per-seat contracts and would prefer EFT so we are not handling so much of the credit card processing fees on larger transactions.

Store and manage supplier currencies and exchange rates. Automatically convert supplier prices to your default currency (CAD) for quotes and invoices. Centralized Currency Table: You want a table that lists all your suppliers and the currency they use for invoicing. This table would also include the exchange rate (multiplier) to convert their currency to your default currency (CAD). Default Currency Billing Details: For each supplier, you want to specify the currency they use for invoicing. This information will be stored in the table. Exchange Rate Management: The table will allow you to manage and update the exchange rates for each supplier’s currency to CAD. Automatic Currency Conversion: When you upload wholesale prices in your items table (in the supplier’s currency), the system will automatically convert these prices to CAD using the exchange rate from the table. This ensures that quotes and invoices are always displayed in your default currency (CAD). -Supplier Name -Supplier Currency -Exchange Rate to CAD -Wholesale Price (Supplier Currency) -Wholesale Price (CAD) Supplier A USD 1.25 $100 $125 Supplier B EUR 1.45 €80 $116 Supplier C GBP 1.70 £70 $119 Explanation: Supplier Name: The name of your supplier. Supplier Currency: The currency in which the supplier invoices you. Exchange Rate to CAD: The multiplier used to convert the supplier’s currency to CAD. Wholesale Price (Supplier Currency): The price provided by the supplier in their currency. Wholesale Price (CAD): The converted price in CAD, calculated using the exchange rate. This table allows you to easily manage and update exchange rates, and ensures that all prices are automatically converted to your default currency (CAD) for quotes and invoices.

The documentation for HaloPSA is nearly unanimously the biggest gripe everyone has with the product, and better documentation has been promised for ages. Let the community help take some of the burden off the Halo team. I'm thinking something that uses tech like Git to version-control, PR, and allow for an easy review process. Markdown support would help us make it readable. And something with the ability to link other pages or issues. CakePHP has some of the best documentation of any project we've ever used. I think it's autogenerated by SphinxDocs reading the Github Repo This would be a HUGE help to the platform as so many of us see things in Halo and have no idea what they do. Letting customers and fans drive documentation and having it be in a controlled environment will ensure that documentation is customer-driven, accurate, and relevant.

Currently, we are required to present serial numbers on invoices for some serialized items. At present, there is no variable which allows us to include the serial number of a consigned item in any way on an invoice. The goal is, when we sell something (say a laptop), we should be able to select that item from inventory, and the serial number of the item selected from inventory should appear on the customer's final invoice.

We have alot of our customers using the Halo application and have requested to use the 'Calendar' feature however they are all on different tenants. The issue is that when you setup the Exchange Integration, it is linked to your own M365 tenant and that is why when they try to connect it, it produces an error as there accounts are part of a different M365 tenant. Can it be looked into to allow multiple tenants to connect to the Calendar feature

Define the background color of an action, how it is displayed in the ticket so Agents can more clearly identify what is comunication with the customer and what is internal communication See crudely made screenshot for example