Jira Service Management pricing: agents, customers and billing
Work out who needs a Jira Service Management (JSM) agent licence. Compare current Service Collection five-agent prices, annual tiers, free customer access and a mid-cycle handover example.
In this guide
- How does Jira Service Management pricing work?
- Who needs an agent licence?
- Count unique people in a mixed support team
- What does a stable five-agent subscription cost?
- Why can a handover change the bill when the team ends at five?
- Does a free customer mean the whole service is free?
- Run a scoped access and billing review
- Download the roster, quote comparison and handover sheets
How does Jira Service Management pricing work?
Start with the people who need agent access, then price their Service Collection tier and billing cycle. Customers submitting requests are a different licence population. The current cloud offer groups Jira Service Management with other Service Collection applications; a historic standalone price is not automatically the right quote.
The public pricing calculator was checked on 16 October 2026 with five agents. Standard displayed $26.90 per agent per month, while annual billing displayed $1,350 for the 4–5 agent tier per year. Those are different payment units. The worked example below keeps US-dollar base references separate from tax, currency conversion and other costs.
Who needs an agent licence?
| Person’s work | Agent entitlement decision | What to verify |
|---|---|---|
| Works the queue and communicates with customers | Agent access is required | Assigned product access and permitted service-space role. |
| Submits and follows permitted requests | Customer access does not require an agent licence | Customer account, access settings and request visibility. |
| Approves a request as a customer | Approval alone does not require an agent licence | Approver is a customer of the service space and can use the intended approval route. |
| Occasionally assists with internal comments | A correctly licensed and permitted collaborator can assist | Existing Jira licence and Service Desk Team permissions; do not assume agent capabilities. |
Atlassian’s space-role documentation distinguishes agents from collaborators. Its approval guide says approvers can approve as customers without an agent licence. Its customer account guide distinguishes portal-only accounts from Atlassian accounts with product roles. A person with an Atlassian login is not automatically a paid agent.
Match access to the actual task. If a collaborator must start managing the queue or replying directly to customers, reassess the entitlement and permissions rather than relabelling the same work as free collaboration. Keep an export of assigned access for your own authorised review.
Count unique people in a mixed support team
This fictional baseline has ten people. Five work as agents; three are customer-only requesters or approvers; two assist internally under assumed existing Jira licences. A01 also requests service, and R02 both requests and approves. The downloadable role file has twelve assignments but only ten distinct people.
| Person / role | Required access | Agent counted? |
|---|---|---|
| A01 — Service lead | Agent and requester | Yes |
| A02 — Support specialist | Agent | Yes |
| A03 — Support specialist | Agent | Yes |
| A04 — Support specialist | Agent | Yes |
| A05 — Support specialist | Agent | Yes |
| R01 — Employee requester | Customer | No for this scoped role |
| R02 — Manager | Customer and approver | No for this scoped role |
| R03 — Employee requester | Customer | No for this scoped role |
| J01 — Developer | Collaborator | No for this scoped role |
| J02 — Developer | Collaborator | No for this scoped role |
The agent population is five, not twelve. A01’s requester role does not create a second agent licence. R02’s approval does not make that person an agent. J01 and J02 are not assumed to have free Jira access: their existing licence and permitted internal role are separate prerequisites.
On a paid tier, do not subtract the Free plan’s three-agent allowance from five and budget for only two. The Free offer is a separate plan for up to three agents. Capacity alone is also insufficient to choose Free: inspect the retained features and limits your service needs.
What does a stable five-agent subscription cost?
The four alternatives below use the same five-agent input. For monthly billing, Standard was $26.90 per agent/month and Premium $61.60. Annual billing showed full yearly totals for the 4–5 agent tier. Multiplying the monthly reference by twelve gives a twelve-month illustration, not an annual quote.
| Alternative | First base payment | Twelve-month base reference | Price unit |
|---|---|---|---|
| Standard / Monthly | $134.50 | $1,614.00 | 5 agents × monthly unit price |
| Standard / Annual | $1,350.00 | $1,350.00 | Annual 4–5 agent tier total |
| Premium / Monthly | $308.00 | $3,696.00 | 5 agents × monthly unit price |
| Premium / Annual | $3,100.00 | $3,100.00 | Annual 4–5 agent tier total |
At these unchanged references, the annual Standard total is $264 below twelve monthly payments; the Premium difference is $596. Standard and Premium have different feature scope. These figures exclude taxes, conversion, promotions, prorations, usage extras, other licences and internal operating costs. They are alternatives, not a combined bill.
Use your actual agent count in the live calculator. Its initial 75-agent display had a different average unit rate, so copying that headline into a five-agent budget would be misleading. Keep the selected count, tier, billing radio and quote time with the price. Confirm currency and tax on the actual quote using Atlassian’s purchasing and licensing guidance.
Why can a handover change the bill when the team ends at five?
Consider a separate 30-day handover. Start with A01–A05. Add incoming agent A06 from day 11, then remove A02 from day 21. There are six simultaneous agents during days 11–20 and five again at the end. The stable-five-agent prices above must not be applied unchanged to this scenario.
| Checkpoint | Active agents | Count |
|---|---|---|
| Day 1 | A01, A02, A03, A04, A05 | 5 |
| Day 11 | A01, A02, A03, A04, A05, A06 | 6 |
| Day 21 | A01, A03, A04, A05, A06 | 5 |
The Service Collection licensing FAQ describes Maximum Quantity Billing for monthly subscriptions: seats added mid-cycle are prorated for the remaining period, while removing seats mid-cycle does not reduce that period’s bill. An ending screenshot of five agents is therefore insufficient to reconstruct what was charged.
The access CSV records a first-active day and a first-excluded day. A02 is active through day 20; A06 is active from day 11. Check the billing cycle, assigned-seat history, any reusable seat capacity and actual invoice lines. The example does not calculate a partial-cycle charge or an annual-tier expansion, and it is not a recommendation to grant extra access.
Does a free customer mean the whole service is free?
No agent licence is needed merely to use the permitted customer route. That does not make every associated service cost zero. Check the app, feature and usage meter: agent subscriptions, AI-assisted conversations or resolutions, Assets, automation capacity and Marketplace apps can have separate scope.
Atlassian’s feature and usage details distinguish tiers and Jira Service Management virtual service agent conversations. The collection licensing guidance also describes Customer Service Management AI agent resolutions. Keep the relevant application and meter with each estimate; do not treat all AI activity as one interchangeable allowance.
Current collection packaging also differs from an existing standalone subscription. The transition guidance describes staged account eligibility and migration. Inspect your own subscription and notifications before assuming a historic offer, feature or migration date applies to it.
Run a scoped access and billing review
Use a controlled request and authorised test participants to check the requester, approver, agent and collaborator routes separately. Record the actual account, retained tier, permissions and outcome. An internal developer comment and a public reply to a customer are different acceptance checks.
Then reconcile the product-access list against the billing period, including temporary access. Name any required external apps, paid usage and internal setup work. The software total-cost guide covers the wider budget; the Jira Service Management profile provides the product overview. For a different IT-service shortlist, start with the Freshservice profile.
No account, licence, request, approval, comment, trial or purchase was operated for this article. The worksheets contain proposed checks and blank observation fields. They do not assign roles or change billing.
Download the roster, quote comparison and handover sheets
Download the twelve role assignments ↓
Download the four quote alternatives ↓
Download the six access intervals ↓
Download the six-check evaluation sheet ↓
Read the scope and file notes ↓
Keep the baseline quote and changing-access scenario separate. Fill in the actual quote and complete cost only after checking the retained subscription. The comparison scorecard can help record your service requirements and evidence.
Frequently asked questions
How much does Jira Service Management cost for five agents?
On 16 October 2026 the Service Collection calculator showed Standard at $26.90 per agent/month and Premium at $61.60 for five agents. The corresponding annual 4–5 agent tier totals were $1,350 and $3,100 per year. These are US-dollar base references; confirm actual tax, scope and quote.
Do Jira Service Management customers need paid agent licences?
Customers submitting and following permitted requests do not need agent licences merely for that customer access. Assigned product roles, request visibility and separately metered service usage still need review.
Do Jira Service Management approvers need agent licences?
Atlassian says approvers can approve as customers of the service space without a Jira Service Management agent licence. Confirm the person’s customer access and intended approval route.
Can Jira users help through internal comments without becoming agents?
Properly licensed and permitted collaborators can assist internally. The documented collaborator role has limited scope; do not assume it permits managing the queue or replying publicly as an agent.
Is Jira Service Management Free for five agents?
The reviewed Service Collection Free plan is limited to three agents. A five-agent paid subscription is not priced by deducting three free agents and paying for only two.
Why did the bill not fall after removing an agent?
Under the reviewed monthly Maximum Quantity Billing guidance, removing seats mid-cycle does not reduce that period’s bill. Mid-cycle additions are prorated, so review the billing period, assigned-seat history and invoice rather than only the ending roster.
Is Jira Service Management now part of Service Collection?
Current Cloud pricing is presented through Service Collection. Existing standalone subscriptions can have account-specific transition and renewal arrangements; check the actual subscription and notifications.
Put the guide into practice
Explore help desk tools, then compare your shortlist.
Explore the category →