HaloITSM review

HaloITSM is an all-in-one service management platform for IT teams and organisations that need to manage requests, incidents, changes and assets. It is described as ITIL-aligned, with workflows for handling service delivery across employees and customers.

Its incident management tools cover SLA management and workflow automation; AI can help triage, summarise and categorise requests. A self-service portal lets users browse a service catalogue and submit requests. Teams can also manage changes, end-user assets and configuration items, with a CMDB for visualising dependencies. The product brief also lists AI support for service desk, knowledge creation and discovery, plus integrations to bring apps together.

The pricing page lists a 30-day free trial. The product is aimed at teams looking for a broad ITSM suite rather than a standalone ticketing tool, but the price depends on the licensing option and is not fully published in USD.

The clearest advantage is breadth: incident handling, service requests, change control, asset management and a CMDB sit within one platform. That can reduce the need to stitch together separate tools for core ITSM processes. The pricing page says the All-in-one plan includes all features, modules and integrations, with no charges based on ticket or data volume.

• End users and customers are free. Paid licenses are for agents, so the seat count to price is the agent team, not everyone who submits a request.
• The service catalogue supports self-service. Users can find and request services through a portal, while staff can manage requests and workflows centrally.
• AI is applied to several service desk tasks. The product brief lists triage, summarisation, categorisation, knowledge creation and discovery.

In one r/ITManagers discussion, a commenter involved in an evaluation said Halo compared well on cost versus performance and praised its customer service. That is one account, not a guarantee, but it supports putting Halo on a shortlist when evaluating full-suite ITSM options.

The main drawback is price transparency. The pricing page displays £66 per agent per month, billed annually, for All-in-one, but does not publish a USD agent price or a monthly rate. It also says monthly or annual billing is available, without showing the monthly amount. The required onboarding package is bespoke, so that cost needs to be confirmed before comparing total first-year spend.

The Enterprise Package is listed at a fixed $1 million per year, or $83,333.33 per organization per month, with unlimited licenses and funded implementation. That is a very different buying model from per-agent pricing and is a substantial commitment for most teams.

The page says All-in-one includes all features and has no ticket- or data-volume charges, but the published pricing details do not publish AI usage limits or other numeric plan caps. Ask Halo to confirm those terms, onboarding cost and the applicable currency in a written quote. The 30-day trial gives teams a chance to evaluate the product, but it does not resolve the pricing gaps.

HaloITSM does not publish a USD per-agent price. Its pricing page lists the All-in-one plan at £66 per agent/month when billed annually; the USD rate and monthly rate are not published. The page says monthly or annual billing is available, so get the actual rate and billing terms for your region in writing.

The Enterprise Package is listed at $1 million per year, or $83,333.33 per month, for unlimited licenses and funded implementation. That is a steep move from per-agent pricing, but the plans cover different team sizes and are not directly comparable. All-in-one includes the platform’s features, modules and integrations; end users and customers are free, and there are no ticket- or data-volume charges.

Budget for the required onboarding package, whose cost is bespoke. A 30-day free trial is available, but there is no free agent tier. Ask for a complete quote that covers agent seats, onboarding and renewal terms before comparing it with your current stack.

The published materials do not specify migration tools, import formats, data-export options or the work needed to move records into or out of HaloITSM. Treat those as pre-contract questions, not details to sort out after signing. Ask which ticket, asset, knowledge-base and configuration data can be imported and exported, in what format, and whether assistance costs extra. The required onboarding package has a bespoke cost, so include it in the migration budget.

Before switching, map the workflows, integrations and records you rely on, then confirm how each will be handled. HaloITSM says it can connect apps and centralise systems, but the available information does not explain how integrations or data are preserved on exit. Get the answer in writing, including any post-cancellation access or export window.

We do not have Reddit posts or comments in the published material, so we cannot responsibly claim what users say makes them leave. Pricing opacity and bespoke onboarding are visible buying concerns; they are not evidence of reported churn reasons.