Feature Ideas

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

Update Addigy Integration to use Addigy v2 API and remove the dependency on the NHServer in HaloPSA for alerts. Addigy appears to support Webhooks like Ninja does.

We heavily use to-do's as a way of creating checklists on common steps. However, a lot of our clients require unique custom checklists. We use IT Glue currently for this and it allows not only a to-do, but it allows that to-do to be expanded detailed steps (written in HTML). What I would like to see is the following To-dos have their own tab in tickets and not just a sidebar. To-do's can be expanded to show links or steps (See screenshot of Glue) To-dos once completed hide from the list To-do's that can be associated with a client site and be templated To-Do templates can be grouped

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.

Would like the ability to map asset types in Ninja to asset types in Halo. For example, in Halo all our current assets and items are filtered where asset type is called workstation or server. However, Ninja brings servers across as Windows_Server. This means we have to go and update all our reports as well as all our items where the quanity is mapped to device name is server.

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.

I recomend the implementation of JSONata (https://jsonata.org/) to retrieve and work with JSON data in customer runbooks and custom integrations. JSONata is a powerful framework to query and transform JSON data for custom integration. Just an easy example you cannot do in HALO version 2.184: ✅ HTTP-Get all users of a company by Id Your response is a set of users: {"response": { "users": [ { "id": 6481, "client_id": 273, "name": "Heiko P.", "customfields": [ {"id": 274, "name": "CF3rdpartyContactId", "value": "860"} ] }, { "id": 6482, "client_id": 273, "name": "John K.", "customfields": [ {"id": 274, "name": "CF3rdpartyContactId", "value": "861"} ] }, { "id": 6483, "client_id": 273, "name": "Paul D.", "customfields": [ {"id": 274, "name": "CF3rdpartyContactId", "value": "862"} ] }, { "id": 6484, "client_id": 273, "name": "Peter X.", "customfields": [ {"id": 274, "name": "CF3rdpartyContactId", "value": "863"} ] } ] } } A JSONata codeline of {"company": response.users[0].client_id, "contacts": response.users[].customfields[id=274].$number(value) } Transforms this into { "company": 273, "contacts": [ 860, 861, 862, 863 ]} that you can directly submit to a 3rdParty solution.

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

Have the ability to create Dashboard Only Agent for Interactive Displays Similar to API Agent.

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.

At the moment even if an Agent is marked as On Holiday/Sick in Halo, if a User replies back to a ticket the ticket remains with the Agent that is on holiday meaning a lot of manual intervention is needed to check and move tickets. This feature idea is to have a setting/configuration option that would allow a ticket to move to Unassigned when a User replies back to a ticket 'On Hold' or 'In Progress' where the Agent is On Holiday/Sick. I don't think there is currently another way of achieving this (e.g. via rule) - and have checked this out.

Add the ability to organize actions into groups in tickets. This could be accomplished with either drop-down menus with multiple actions or with brackets with actions tied to that group. Make it where we can name the group anything. An example would be having 4 Escalation actions; Escalate to Tier 2, Escalate to Tier 3, Escalate to Sales, Escalate to Manager. Most of those are not needed that often. It would be nice if there was a way to put them all together in one 'Action Group' that we could expand if one of those actions is needed.

Halo has a few N-able integrations but is missing a key offering, Cove Data Protection Cove is an amazing cloud based backup product, It would be amazing to have a link for simple things like subscription tracking to link to recurring invoice items. Primarily 365 backup items but all would be beneficial

We have started to use planner to really help our projects, Halo Projects still quite threadbare. Integrating the two would really be great.

WatchGuard Cloud has a well documented API. The management portal would allow us to sync over assets for billing as well as creating alerts from the WatchGuard Threat Sync solution.