HaloPSA Pricing per Agent and the Real License Cost for an MSP Service Desk

HaloPSA pricing in USD is $99 per named agent per month for 1 to 24 agents, $95 for 25 to 49, $89 for 50 to 99 and $85 for 100 to 249, billed annually. Every feature, module and integration is included, with no tiers, editions or add-ons. Required onboarding is quoted separately, and ticket routing is already part of the license.

These figures come from the live Halo pricing page and its published calculator, read October 23, 2026. HaloPSA, HaloITSM and Halo Service Desk are one platform with the same per agent pricing model. For an MSP, the buying questions are how many people need access, what implementation involves and whether the included assignment methods fit the service desk.

HaloPSA pricing bands in USD

The published named license bands depend on agent count. Each rate below is per agent per month, billed annually. Halo also offers monthly billing, but these figures are the annual billing rates rather than a separate monthly contract price list.

There is no feature upgrade to buy for a larger service desk. Growing into another band changes the license rate, not access to routing or reporting. Use the live calculator for larger teams rather than extrapolating a flat price beyond the published bands.

Third party blogs disagree on HaloPSA license cost. A quote of $99 at 10 agents matches the current US calculator, while other articles reproduce older tier tables. Blogs quoting pounds may be reading the UK page, where the price is GBP 69 for up to 24 agents. Keep currency, agent count and billing term consistent when comparing sources.

Named and concurrent licenses in Halo

A named license belongs to an individual agent. Agents are the people who log in to work tickets, deals and projects. Count the people who need that access, including service coordinators and managers who work inside the platform, rather than using only the technician headcount.

Concurrent licenses are shared across a pool and count agents logged in at once. In the published calculator a concurrent seat costs twice a named seat, so it pays off only if each concurrent seat replaces more than two named users. The calculator doubles both the agent count used to determine the band and the seat price.

That makes concurrent licensing worth examining for shifts with little overlap. Map actual login patterns before buying it. A shared pool still needs enough capacity for handovers and people working at the same time, so a roster alone does not establish whether concurrent licenses save money.

End users and customers using the portal are free. Halo is not priced by tickets, end users or data volume. Separate portal users from working agents when gathering a license count so customer growth does not get mistaken for a requirement to buy more seats.

What costs extra beyond the Halo license

Onboarding packages are required with purchase and have a bespoke cost depending on scope. There is no public figure to insert into a reliable first year budget. Ask for a written scope covering the configuration and implementation work your service desk needs, alongside the license quote.

For MSPs that want outside help defining that scope, an independent implementation consultant can help frame the required onboarding work before the purchase. Ask which work the Halo package covers, which responsibilities stay with your team and how acceptance will be agreed. Outside advice is a separate purchasing decision, not a substitute for the required package.

Halo also publishes contract discounts. Customers on standard pricing receive compounded license discounts as Halo reaches ARR Milestones, with the page showing 5 percent. Charities and not for profits receive a 15 percent discount for the contract. Confirm the applicable terms in your quote rather than subtracting assumed future discounts from a budget.

The Halo Enterprise Package is a separate commercial option with unlimited licenses and funded implementation for a fixed $1M per year. It is not a feature tier that a small MSP must purchase to access a module. Compare its scope with a standard license and onboarding quote if that purchasing model is relevant.

Yearly HaloPSA cost for named agents

These totals multiply the applicable named agent rate by the team size and then annualize it. The monthly column is the monthly equivalent of an annual subscription, not a quote for monthly billing. Required onboarding is excluded because its cost depends on scope. The figures use standard pricing without discounts.

For a purchase decision, put the annual license total and the required onboarding quote next to each other. Keep any optional routing subscription separate so the base HaloPSA cost remains visible. A license comparison alone cannot establish the total implementation budget.

How Halo compares with other MSP platforms

Halo publishes an inclusive per agent rate, which gives buyers a clear license baseline. Compare it with the quote details in our Autotask PSA pricing and ConnectWise PSA pricing posts, and the plan differences in our Atera pricing per technician guide. Match working users, included scope, billing term and onboarding before deciding which costs less for your MSP.

What ticket routing costs in HaloPSA

Halo includes Round Robin, Load Balance, Intelligent Routing and Qualification Matching at no extra cost. You never pay more for routing inside Halo. The question is whether the included methods make the right decisions for the work arriving at your desk.

Round Robin cycles by agent ID without a load input. Load Balance counts tickets rather than effort unless estimates are filled in. Availability comes from the agent status toggle and login. Those inputs can work for a disciplined queue, but ticket counts and status settings need to reflect the conditions you want dispatch to consider.

Before adding another tool, review your HaloPSA ticket rules and round robin setup. Check whether estimates are maintained, status changes reflect availability and qualification rules cover the work being assigned. A configuration problem may be solvable within the subscription you already pay for.

When an additional routing layer is worth evaluating

Assigner sits beside the PSA and picks the person by live availability, open load, skills and working hours. It records the reason on every assignment. That gives a service manager a way to review why work went to a particular person. It is an optional routing expense alongside Halo, with a separate per user subscription.

For a worked example, 10 dispatch-relevant Halo agents cost $11,880 a year in Halo. Adding Assigner Team for the same 10 users is $2,160 a year, using $18 per user per month billed yearly. Required Halo onboarding remains outside those subscription figures. See Assigner pricing for the plan scope before choosing a subscription.

Evaluate that extra cost against a specific dispatch problem. If agents receive unsuitable work because shifts, skills or open load are missing from the decision, test those cases. Our guide to MSP ticket assignment explains how to think through that routing policy.

Who should buy which setup

• A small MSP with a simple queue. A 5 person shop may need nothing beyond Halo round robin. Start with included routing and check its decisions against the way your team works.
• A service desk with overlapping work and specialist skills. Configure the included matching and balancing methods first. Evaluate Assigner if the remaining problem needs live availability, open load, skills and working hours considered together.
• A team working separate shifts. Compare named and concurrent licenses using actual simultaneous logins. Concurrent licensing only pays off when the pool replaces enough named users.
• A buyer comparing HaloITSM pricing or Halo Service Desk pricing. Use the same platform pricing model and confirm onboarding scope for the intended workflows.

HaloPSA pricing questions

How much does HaloPSA cost per agent?

Named licenses cost $99 per agent per month for 1 to 24 agents, $95 for 25 to 49, $89 for 50 to 99 and $85 for 100 to 249, billed annually. From 250 agents, the price falls gradually from $85 toward about $58 at 2,000 agents. Required onboarding is quoted separately.

Is there a free version of HaloPSA?

No free plan is offered. There is a trial, with a "Try for Free" option on the Halo site. Use it to assess workflows and assignment behavior before agreeing to a paid subscription and required onboarding.

Does HaloPSA charge for end users?

No. End users and customers using the portal are free. Agent licenses cover people logging in to work tickets, deals and projects. Ticket counts, end user counts and data volume do not determine the license price.

What is the difference between named and concurrent licenses in Halo?

A named license is assigned to an individual. A concurrent license belongs to a shared pool that limits simultaneous agent logins. In the published calculator a concurrent seat costs twice a named seat, so it pays off only if each concurrent seat replaces more than two named users.

Is HaloPSA cheaper than ConnectWise?

The Halo price list alone cannot establish that. Halo publishes the named agent bands above and requires quote-based onboarding. Compare your actual ConnectWise proposal with the same user count, contract term and implementation scope using our ConnectWise PSA pricing guide.

Source for Halo license prices, commercial terms and calculator behavior is the Halo pricing page and its pricing script, read October 23, 2026. The former halopsa.com site redirects to usehalo.com.