Right sizing a HaloITSM agent count starts with a single honest measurement: how many people actually logged in, picked up tickets and resolved work in the last quarter, against how many agents you are paying for. The difference is your overspend, and on a per-agent platform it is almost always larger than the team assumes. Because HaloITSM bundles every module into one all-in price, buyers tend to scrutinise the feature set and never the headcount, which is exactly backwards: the modules are already paid for, but each surplus agent is a recurring line you chose to carry. This article sits under our HaloITSM pricing guide and the broader complete guide to ITSM license optimization.
Start with demonstrated use, not the org chart
The org chart tells you who is on the service desk team. It does not tell you who works the HaloITSM queue. Those are different lists, and the gap between them is the first thing to find. Pull a usage report for the last 90 days and rank agents by tickets touched, work logged and last login. You will typically see a clean active core, a middle band of occasional users, and a tail of accounts that have not resolved a ticket in months: leavers never deprovisioned, managers who were given a licence "to look", project staff whose engagement ended. Each of those is a candidate for removal at renewal.
Named versus concurrent: match the model to the shift
HaloITSM supports both named and concurrent agent licensing, and choosing the wrong one is a quiet, recurring overcharge. A named licence is tied to one person and makes sense for agents who sit on the queue all day. A concurrent licence is shared across a pool and is counted by how many are logged in at the same moment, which suits part-time staff, follow-the-sun coverage, and teams where nobody is online around the clock. The classic mistake is putting a 24-hour, three-shift team on named licences, one per body, when a concurrent pool sized to the busiest shift would cover the same coverage for a fraction of the seats.
| Team shape | Better fit | Why |
|---|---|---|
| Full-time agents on the queue all day | Named | One person, one seat, always in use |
| Three-shift or follow-the-sun coverage | Concurrent | Sized to peak concurrency, not total headcount |
| Part-time or occasional responders | Concurrent | Pool covers many bodies with few seats |
| Seasonal or project surge staff | Concurrent | Avoids carrying named seats year round |
Separate true agents from request submitters
Not everyone who touches HaloITSM needs an agent licence. End users raising tickets through the self-service portal are not agents and should never be counted as such. The line to police is the middle: approvers, occasional contributors, and managers who only review. If someone resolves and owns tickets, they are an agent. If they only submit, approve or read, they are not, and licensing them as an agent is overspend dressed up as convenience. Mapping each role to the right access level is the single most effective right-sizing move on a per-agent model.
Build the defensible number before the rate talk
Right sizing has to happen before you negotiate price, not after. Once the vendor has anchored a quote on your current inflated count, walking it back is a concession you have to argue for; walk in with a clean number and the inflated baseline never gets set. Do the work about nine months out, the same point in the timeline covered in the HaloITSM renewal checklist. Document the active-use analysis so the count is defensible: a buyer who can show "these 42 agents resolved 96 percent of tickets last quarter" negotiates from evidence, while a buyer guessing at "about 60" is negotiating from the vendor's number.
Re-check the count every renewal, not once
Agent counts drift in one direction. New hires get seats, leavers keep them, and projects add licences that outlive the project. Left unchecked, the count ratchets up renewal after renewal and the flat-price simplicity masks it because the per-agent figure looks the same. Make the active-use pull a standing item in every renewal cycle, not a one-time clean-up. The discipline that recovers seats this year is the same discipline that stops them re-accumulating before the next term, which is why right sizing pairs naturally with the protections in HaloITSM price protection and multi year deals and the discovery work on the HaloITSM platform page.
A practical habit makes the re-check almost free: deprovision the HaloITSM agent licence as part of the standard leaver process, the same step that revokes email and building access. Most count drift comes not from deliberate over-buying but from accounts that were never closed when someone moved teams or left, so closing that loop at source means each renewal starts from a count that is already close to right. Pair it with a quarterly glance at the lowest-activity accounts and the annual right-sizing exercise becomes a confirmation rather than a clean-up.
The gated HaloITSM Buyer Guide includes the active-use worksheet and the named-versus-concurrent decision grid we use to right size before a renewal.
The bottom line on right sizing HaloITSM agents
Measure who actually works the queue, license each group on the model that fits its shift pattern, keep request submitters off agent seats, and lock the corrected number in before any price is quoted. On a flat-price platform the features are settled, so the agent count is where the money moves, and it moves toward the buyer who counted honestly. We run that analysis for clients through our license optimization service on fixed fee or gainshare, drawing on more than 500 engagements at a 30 percent average reduction across 10 platforms.
Frequently asked questions
- How do I right size HaloITSM agent counts?
- Pull the list of agents who actually logged work and resolved tickets in the last 90 days, compare it to the agents you are paying for, and remove the gap. Then test whether a named licence per person or a concurrent licence for a shared pool fits your shift pattern better. The right number is the smaller of demonstrated active use and the model that matches how your team works.
- Does HaloITSM charge per named agent or concurrent agent?
- HaloITSM supports both. Named licences are tied to an individual and suit agents who work the queue full time. Concurrent licences are shared across a pool and suit part-time, follow-the-sun or seasonal staff who are never all online at once. Right sizing means choosing the cheaper fit for each group rather than putting everyone on the same model.
- When should I right size before a HaloITSM renewal?
- About nine months out, well before the rate conversation. Correcting the count after the price is anchored to an inflated number is far harder than walking in with a clean, defensible agent total. Right sizing first means you negotiate the seats you actually need, not the seats that accumulated.
Book a HaloITSM review.
We measure real agent use, fix the licence model, and lock the corrected count in before the rate talk. Fixed fee or gainshare.
Book a HaloITSM review →