The most misunderstood number in Jira is not a price - it is a headcount. Only agents cost money. Customers, the people raising tickets, are free and unlimited. Get this distinction right and the product gets cheap; get it wrong and it gets expensive fast.
Jira Service Management has three human roles, and two of them are free. The agent works tickets - assigns, replies publicly, transitions, resolves - and needs a licence. The customer raises requests and follows their own - no licence, no seat limit. The third group, people in your organisation who use other Jira products, can view and comment internally on tickets without a service desk licence at all. Plans then wrap limits around the edges: the free plan has historically allowed up to 3 agents, paid plans charge per agent per month, and tiers change often enough that this page will quote shapes, not prices. What never changes is the shape itself - and the mistakes below all come from ignoring it.
The dividing line is work, not job title. A person is an agent if they need to operate the ticket: see queues, assign and transition work, post public replies to customers, and be measured by SLAs. In a typical office that is the IT support staff - two, three, maybe five people - however big the company is.
Team leads who only review numbers do not need agent seats to read reports if you route reports sensibly; a manager who jumps into queues during a crisis does. The honest test: 'will this person close tickets?' If not, they are probably not an agent, whatever their seniority.
Customers can raise requests through the portal or email, follow their own tickets, reply, and receive satisfaction surveys. They cannot see queues, other people's tickets, internal comments or reports - and that wall is a feature you get without configuring anything.
'Unlimited' deserves one honest footnote: unlimited customers still means every customer is an account on your site, and on restricted projects you control who may become one. Free plans also carry site-level limits such as storage and daily email notification caps that a busy desk can feel. Unlimited people, modest plumbing - plan your upgrade around volume, not headcount.
On the free plan the binding constraint is the agent count - historically up to 3 agents - plus reduced storage and community-only support. For a two or three person IT team serving a whole office, that is a genuinely usable helpdesk: full portal, queues, basic SLAs and reports, zero rupees.
The moment a fourth person must work tickets daily, you are on a paid plan and the per-agent clock starts. This is the real pricing conversation of Jira Service Management - not "can we afford the tool" but "how many people truly work the queue". Keep that number honest and Jira stays proportionate; inflate it and any tool looks expensive.
None of these are Jira's trickery; they are the default outcome of inviting generously and never auditing. The vendors count seats - make sure you count them first.
Between agent and customer sits a useful pattern: colleagues who already use Jira Software or another Jira product can be given access to view service tickets and add internal comments - asking the network engineer a question inside the ticket, for example - without an agent licence. They cannot reply publicly to the customer or work the queue; the agent still owns the conversation.
For offices where developers or infrastructure staff occasionally feed expertise into tickets, this is the difference between a cheap, connected setup and a wall of forwarded screenshots. Set it up deliberately, and keep the rule visible: internal comments are staff-only, public replies are the agent's door to the customer.
See every screen of the Jira helpdesk setup live, from the empty project to the first real ticket.
Watch Full VideoThe free plan for Jira Service Management has historically covered up to 3 agents, with customers free and unlimited. Plan details change over time, so confirm the current limits on Atlassian's plan page - but the shape is stable: agents are the counted resource, customers are not.
Not necessarily. Agents are the people who work tickets. A manager who only reviews performance can usually be served with shared reports and dashboards rather than a seat. If the manager regularly assigns, replies or resolves, they are working the queue and do need to be an agent.
No. Comments marked internal stay inside the agent side of the ticket. Customers see public replies and their own conversation only. That separation is built into the product, which is why agents must choose the internal note versus reply tabs carefully.