Choose Jira Service Management for an SLA-focused shortlist when customer contracts require different clocks by tier, region or workflow state. Its documented strength is configurable measurement: calendars, matching goals and optional pauses work together. It can receive external customer requests through portals and email, so restricting it to internal IT would miss a relevant support use case.
Buy the current Service Collection package
Atlassian’s former JSM pricing address now redirects to Service Collection pricing. The cloud package includes Jira Service Management, Customer Service Management, Assets and Rovo. The current calculator’s first fifteen-agent band is $26.90 per agent/month for Standard and $61.60 for Premium. Its default seventy-five-agent display shows lower effective volume rates. Free covers up to three agents; customers are unlimited and do not need a Service Collection license. For five agents, the current annual tiers are $1,350 Standard or $3,100 Premium, before tax and paid usage.
Agents can work requests and communicate with customers. Other Jira users can contribute internal comments and watch tickets without a service agent license, subject to their own product access. Do not budget every technical collaborator as a free customer, or assume an internal collaborator can send public replies.
Calendars, tiers and customer waits
The calendar guide supports named schedules with time zones, working days, daily time periods and holidays. A goal selects its calendar, which lets different commitments count different regional hours. Configure which contract determines the calendar when a case moves between regions.
Customer and organization details can select goals through JQL using fields such as support tier or region. Those details need reliable values. Start, pause and finish conditions define each SLA’s measurement. Waiting for a customer is a documented optional pause, so a status named “waiting” does not by itself prove that every clock stops.
First response, later replies and approaching breaches
First response and resolution are documented metrics. A promise covering every subsequent reply needs its own configured start and stop events. The platform supports repeated SLA cycles after a completed clock encounters another start event; test that configuration with multiple customer replies, internal notes and reopenings.
Agents see remaining time and color-coded SLA states in queues and requests. For an active warning, the SLA threshold automation trigger can run a chosen interval before breach. Add the intended notification or escalation action and size the subscription’s automation allowance. A retrospective report and a visible timer serve different purposes from that rule.
Trial two customer tiers, two regional holidays, a customer-wait pause and a warning thirty minutes before the deadline. That shows whether the configured service promise matches the contract. Read the pricing explanation, compare alternatives, or open the SLA management comparison and Help Desk category.