Because Jira Service Management charges per agent, every inactive or misclassified agent is money spent on a seat that does no work, and right-sizing the count is the first move before any renewal. The method is simple: separate true agents from collaborators and customers, find agents who have not acted on a ticket in months, and reduce the paid count to match real demand before you negotiate. This article sits under our Jira Service Management pricing guide for 2026.
Know who actually needs an agent seat
The most common source of overspend is confusion about who needs a paid agent licence at all. In Jira Service Management, agents are the people who work and resolve tickets; customers raise requests for free, and collaborators can contribute without a full agent seat in many configurations. Estates routinely license people as agents who only ever comment, approve or view, which is paid capacity spent on work that does not require it. The first pass is simply to confirm that every paid agent is genuinely resolving tickets.
The three populations to separate
- Working agents. People who pick up and resolve tickets. These need paid seats.
- Occasional contributors. Approvers, commenters and reviewers who may not need a full agent licence.
- Inactive agents. Licensed seats with no ticket activity over a meaningful period. These are the prime targets.
Find the inactive seats
The data you need is agent activity over time: tickets touched, transitions made, last action date. An agent with no activity over a quarter or more is almost always reclaimable, and a block of them is a direct reduction in the renewal quantity. This is the same shelfware logic that applies across every per-seat ITSM tool, set out in Jira Service Management shelfware and inactive agents. Pull the activity report, sort by last action, and the reclaimable seats surface quickly.
| Signal | What it suggests |
|---|---|
| No ticket activity in 90+ days | Strong candidate to deactivate |
| Only comments or approvals | May not need a full agent seat |
| Left the team or changed role | Reclaim immediately |
| Duplicate or test accounts | Remove before counting |
Reduce before you renew, not after
Timing matters because the agent count you carry into a renewal becomes the baseline the vendor wants to grow from. Cutting inactive seats after you have signed locks you into paying for them through the term, so the reclamation has to happen before the renewal quantity is set. The way that timing interacts with the wider Atlassian cycle is in how to time an Atlassian renewal. A right-sized count going into the negotiation also strengthens every other ask, because it shows the vendor you are managing the estate, not guessing.
Keep it right-sized
Right-sizing is not a one-off. Without a process, agent counts drift upward as people are added and rarely removed, and the next renewal inherits the bloat. A light quarterly review of agent activity, tied to your joiner and leaver process, keeps the count honest and means the saving holds rather than evaporating before the next cycle. This ongoing discipline is the core of ITSM license optimization.
Our gated Jira Service Management Negotiation Guide includes the agent activity audit template and the right-sizing checklist we run before an Atlassian renewal.
Turn the audit into a renewal number
Finding inactive agents is only half the work; the saving is realised when the reclaimed seats are removed from the renewal quantity rather than carried forward out of habit. The step buyers miss is translating the activity audit into a specific target count for the next contract, defended with the data behind it. When you can show the vendor a documented list of seats with no activity over the period, the conversation moves from a vague request for fewer licences to a precise, evidence-backed quantity, which is far harder to push back on. The audit is the leverage; the target count is what you actually negotiate.
It also resets the baseline for the whole deal. Vendors size growth and discount tiers from your current count, so a right-sized starting number improves not just this renewal but the trajectory of the next one. Walking into the negotiation with a smaller, defensible base is one of the highest-return hours a buyer can spend before an Atlassian renewal.
Watch the collaborator and customer boundary
The line between a paid agent and an unpaid participant is where the most durable savings sit, because it is structural rather than one-off. Every person reclassified from agent to collaborator or customer is a recurring saving, not a single reclaimed seat, and the boundary tends to blur over time as teams add people as agents for convenience. A deliberate review of who genuinely resolves tickets versus who only contributes, approves or observes often surfaces a population that never needed a paid seat at all. Tightening that boundary, and keeping it tight through your joiner process, is what stops the agent count creeping back up between renewals and protects the saving you worked to find.
Make reclamation routine, not a renewal scramble
The teams that hold their savings are the ones that stop treating agent right-sizing as a panic before each renewal and turn it into a standing process. A quarterly check of agent activity, wired into the same workflow that handles joiners and leavers, means seats are reclaimed as people change roles rather than discovered in a rush months later. It also keeps the data clean, so when the renewal does arrive the count is already defensible and there is no last-minute archaeology to do. The difference between a one-off cut and a sustained one is process discipline, and it is the cheapest insurance a buyer has against the agent count quietly inflating the next contract.
Where this fits with our service
We audit agent activity and reclaim inactive seats from the platform hub at Jira Service Management through our license optimization service, on fixed fee or gainshare with no fee unless we save you money. Across more than 500 engagements and over 420 million dollars of ITSM contract value negotiated, the average reduction is 30 percent, and on a Jira renewal right-sizing the agent count is usually the first and cleanest source of that reduction.
Frequently asked questions
- How do I right-size Jira Service Management agents?
- Separate working agents from occasional contributors and inactive seats, pull the agent activity report, and reclaim any seat with no ticket activity over a quarter or more. Reduce the paid count to match real demand before the renewal quantity is set.
- Do approvers and commenters need a paid agent seat?
- Often not. In Jira Service Management, agents work and resolve tickets, customers raise requests for free, and collaborators can contribute without a full agent seat in many configurations. People who only comment, approve or view are frequently over-licensed.
- When should I cut inactive agents?
- Before the renewal, not after. The agent count you carry into a renewal becomes the baseline the vendor grows from, and once the quantity is in the contract you pay for those seats through the term whether they are used or not.
Cut the agent count.
We audit agent activity and reclaim inactive seats before your renewal. Fixed fee or gainshare.
Book a Jira renewal review →