Halo AI agent: what it is, how it works, and what it costs in 2026

Why I went deep on this one

I build AI support agents for a living, so when a tool markets an "AI agent," the first thing I want to know is what's actually running under the hood, not what the hero video implies. Halo is interesting precisely because the gap between those two things is wide.

Here's the moment that crystallised it for me. Digging through Halo's own MSP community, the single most-upvoted piece of AI feedback comes from someone who describes themselves as a Halo fan:

"We implemented an action button so openAI can clean up the email, that has never worked and sitting with HaloPSA development support for over 6 months... Don't get me wrong, I absolutely love HaloPSA... for UI and interface, it sure is [2-3 years ahead] but for these automations, it doesn't seem to be the case."

u/techie_mate on r/msp

That tension, a beautiful product whose AI lags its own marketing, is the thing to understand before you buy. I've spent the last three-plus years watching AI agents go live on real support queues, and I can tell you the failure mode that quote describes is the most expensive one: an AI feature that demos well, ships without docs, and quietly does nothing in production. So let's pull the Halo AI agent apart and see what's really there.

What is the Halo AI agent?

First, a naming note, because the keyword is fuzzier than the product. Halo doesn't actually sell something called "Halo AI Agent." What people mean by it is the Virtual Agent, Halo's AI chatbot, plus the wider AI layer that runs across HaloITSM, HaloPSA (its PSA for MSPs), and HaloCRM.

Halo is a single, no-code service-management platform that partners with 5,000+ organisations across 100+ countries, including Microsoft, Siemens, Sky, and Domino's. The AI isn't a bolt-on module; it's positioned as a platform-wide layer that every customer gets. Two distinct things hide under the "AI agent" banner:

• The Virtual Agent is the customer- or employee-facing chatbot. It answers FAQs, walks users through self-service, logs tickets, and transfers to a human when it's stuck.
• The agent-assist AI is everything aimed at your human team: auto-triage, ticket summaries, similar-case suggestions, sentiment scoring, and AI-drafted knowledge articles.

The screenshot below is the assist side in action, a real HaloITSM ticket with AI-suggested articles surfacing on the right while an agent works the case.

If you're new to the whole category, it's worth reading our explainer on what an AI helpdesk agent is before you go further, since a lot of the vocabulary below (deflection, handoff, grounding) carries across every tool, not just Halo.

How the Halo AI agent actually works under the hood

This is the part the marketing page skips, and it's where the most useful "shift" in your thinking happens. The Halo Virtual Agent is not a self-contained AI product. It's an OpenAI-powered assistant you wire into Halo's existing scripted Chat Bot, and its real power is gated behind your own configuration work.

Here's the actual flow, pulled from Halo's Virtual Agent documentation:

A few things matter here:

• It's OpenAI under the hood. A Virtual Agent runs on Halo's built-in OpenAI connection, your own OpenAI account, or Azure OpenAI. No model version is named on the marketing pages; you only learn the plumbing if you read the docs.
• Scripted flow plus AI, not pure AI. Halo distinguishes deterministic, admin-built "bot-flow steps" from AI-interpreted "Virtual Agent conversation steps," and you mix them in one chat profile. The AI figures out intent so you don't hand-build a decision tree, but you're still assembling a flow.
• Grounding needs setup. The agent answers from your knowledge base through "AI Search," which only works properly once you've connected Azure OpenAI or AWS OpenSearch. Without it, search still runs but returns limited results.
• It calls functions to do things. Out of the box it can run system functions like get_knowledge, log_incident, get_my_tickets, and transfer_to_agent (the human handoff). The AI decides which to call from what the user types.

The genuinely clever bit is automation runbooks. You can give the Virtual Agent a custom function that triggers a Halo runbook, with parameters the AI pulls out of the conversation. Halo's own worked example is an automated password reset: the user asks the chat to reset their password and gives their email, and a runbook looks up their user ID and runs the reset. That's a real, end-to-end automated action, not just a canned answer.

But here's the catch that explains the community's frustration: those custom functions and runbooks only work on Virtual Agents using your own OpenAI or Azure connection, not the locked, pre-built out-of-the-box agents. And the newest capabilities (the use_specific_action function and external MCP connections) are limited to OpenAI's Responses API, with the older Assistants API being deprecated in August 2026. In other words, to get the impressive automations, you're managing API connections, system prompts, temperature settings, and function toggles yourself. It's powerful, but it is not plug-and-play.

That's the honest answer to "how does the Halo AI agent work": it's a capable LLM toolkit bolted onto a scripted bot, and most of the magic is something you build, not something you switch on.

What the Halo AI agent can do

Setup caveats aside, the capability list is legitimately broad. Halo's AI spans the whole ticket lifecycle rather than just the chat window.

Running through the AI platform page, the named capabilities are:

• Auto-triage and smart categorisation. Halo AI reads urgency, impact, sentiment, and request history to suggest priority, category, and the best-fit team, working alongside your existing workflow logic. This is the feature MSPs single out as actually good (more on that below).
• Instant AI summaries. Long ticket threads get turned into a short summary of key facts, actions taken, and next steps.
• Similar case suggestions. The AI surfaces related past tickets and their known fixes so agents aren't solving the same problem twice.
• Sentiment and emotion detection. It scores tone in real time, flagging frustration, anger, or urgency, and feeds that back into triage.
• One-click knowledge article creation. After a ticket is resolved, Halo drafts a structured, tagged knowledge article using retrieval-augmented generation, with a human reviewing before it publishes.

That last one is a nice loop, and Halo shows the output directly: an article auto-created from a resolved ticket, with the source ticket number attached.

On the customer-facing side, the HaloCRM version adds suggested replies and runs the Virtual Agent across email, chat, social, and WhatsApp. Here's the Halo Bot working a real support conversation, troubleshooting a printer step by step and offering to log the incident:

One gap worth flagging: there's no explicit reply-drafting feature on the ITSM AI page (the closest is similar-case suggestions). If you've used a Zendesk AI agent or Freshservice's Freddy and expect the AI to hand your agent a ready-to-send draft, that specific feature isn't front and centre here.

How much does the Halo AI agent cost?

Halo's pricing is unusually clean in structure and unusually opaque in practice. There's one all-inclusive plan, no tiers, and AI is bundled in, but the public number only appears once you're already enterprise-sized.

A worked example makes the scale concrete. The public platform pricing slider starts at 250 agents, where £55 per agent per month works out to about £16,500 a month, or £198,000 a year. That's the floor for the transparent pricing. If you're a 15-person IT team or a small MSP, you won't see a per-agent number at all; you'll fill in the HaloITSM pricing form and wait for a quote.

The "AI is free" framing is technically true and practically slippery. The AI is only free once you've committed to Halo's per-agent platform cost, and the community's loudest value complaint isn't the licence at all, it's the onboarding:

"Our rep hit us with the mandatory $4000 onboarding training which caused us to hit the brakes as it negates the whole point of a month to month contract."

r/halopsa

If you're sizing this against other tools, our comparison of AI agent versus human agent cost is a useful frame, because per-seat pricing and usage-based pricing diverge fast once volume grows.

What real users actually say about Halo's AI

The star ratings are strong: HaloITSM sits at 4.7 on Gartner Peer Insights across 232 ratings, and 4.7 on Capterra. But those scores rate the whole product, and the AI-specific signal lives on Reddit, where people get specific.

The good news first: when Halo's AI triage works, people genuinely like it and want it to do more.

"I love how Halo AI checks over a ticket with its Triage capability, drawing from previous tickets and the Knowledge Base is great but the cherry on top would be if the AI could allocate the ticket to a Tech."

u/welshrogueuk on r/halopsa

The recurring friction is twofold. First, the steep learning curve, Halo is repeatedly described as powerful once configured and overwhelming before that, which is why even a Halo implementer warns one-person shops not to buy it. Second, the over-promised-AI problem from the intro, where features ship faster than the docs and support to back them. The most detailed first-hand review on Reddit, a net-positive ConnectWise-to-HaloPSA migration, is telling about what actually wins teams over:

"It's fast, has a modern look and feel... Working through tickets feels far less painful... I don't regret the decision to move, the App is the biggest let down."

u/Defconx19 on r/msp

Notice what's praised: speed and UI. Not the AI. That's the consistent read across the community, the ticketing experience is excellent, and the AI is a work in progress that trails what MSPs see in rivals.

The bigger decision: bundled platform or layer-on agent

Step back and the Halo question is really a category question. To get Halo's AI agent, you adopt Halo, the whole service desk, the per-agent pricing, the onboarding, the configuration surface. For some enterprises replacing a creaking legacy ITSM, that's exactly the right move. For most teams who already have a helpdesk they don't hate, it's a lot of rip-and-replace to bolt on AI.

This is the distinction I'd weigh hardest. A bundled platform like Halo, ServiceNow, or Jira Service Management ties the AI to the suite. A layer-on agent connects to the helpdesk you already run and adds the AI without the migration. If you're shopping the broader market, our roundup of the best AI helpdesk software and our guide to ITSM for smaller teams both map the trade-off in more detail.

Try eesel for an AI agent that layers onto your helpdesk

If the Halo story has a recurring villain, it's the gap between the demo and production. That gap is the exact problem eesel AI was built to close. eesel is an AI agent that plugs into the helpdesk you already use, learns from your historical tickets and existing knowledge base, and goes live in minutes rather than after a multi-thousand-dollar onboarding.

The piece that matters most given everything above: before eesel answers a single live customer, you can simulate it against thousands of your real past tickets and see exactly what it would have said and how much it would have deflected. That's the antidote to "we turned it on and it never worked." One DTC supplements support lead we worked with put the mindset perfectly: the AI will never answer 100% of questions, so they wanted "an AI who is only handling the tickets that it's confident to handle... all the other ones, leave them alone." That control is the point. Across 8,000+ customers, eesel routinely resolves a large share of tier-one volume from day one, Gridwise saw 73% of tier-1 requests handled in the first month, without anyone touching an OpenAI API key or rebuilding a bot flow. And because pricing is usage-based rather than per seat, you're not committing to a 250-agent floor to find out if it works.

Halo's AI agent is a real, capable system if you're ready to live inside Halo. If you just want an AI agent on the helpdesk you already have, try eesel free and simulate it on your own tickets first.