Atlassian to charge $1 per AI agent resolution in Customer Service Management from December

Atlassian will bill $1.00 for every conversation its Customer Service Management AI agent resolves, starting 3 December 2026, with no free allowance on any plan, according to a dev.to analysis of the company's pricing documentation. The charge applies from the very first resolution, and the product involved — Customer Service Management, or CSM — is Atlassian's app for supporting external customers rather than employees.

A meter with no allowance

According to dev.to, the usage meter appears in Atlassian's platform billing as "Customer Service Management AI agent resolutions", and the Service Collection licensing FAQ states the included allowance is none. Subscriptions do not contribute credits toward it either; the meter's contributions tab reportedly shows no eligible subscriptions.

The counting rules amplify the cost. A knowledge base answer counts as a billable resolution — it is the first example of an "autonomous action" in Atlassian's own FAQ, dev.to reports. A large language model acting as a judge decides whether a conversation was resolved, and it does so once, after 24 hours of silence. Because customers cannot reopen a conversation, a repeat contact about the same issue can be billed again.

There is also no safe place to rehearse. Sandboxes do not support CSM resolutions, so any testing has to happen in a live channel — and live channels bill.

That is exactly what worried one customer. A user named Phil H. posted in the Atlassian Community, as relayed by dev.to, that the pricing notice arrived just as his team was about to roll out CSM. He asked other teams how many resolution tickets they were seeing per month, received a single unsourced estimate of 15 to 25 percent, and his team decided not to deploy — in part because benchmarking would have meant running experiments in production.

CSM versus Jira Service Management

Much of dev.to's analysis concerns which desks the meter actually touches. Help desks running in Jira Service Management (JSM), whether for employees or for customers without a CSM customer experience configured, sit on different meters entirely.

CSM comes only inside Service Collection, a bundle that also includes Jira Service Management, Assets and Rovo, and the components cannot be bought separately. An Atlassian staff member wrote in May that most JSM customers are being moved into Service Collection automatically at renewal. The same staff article carries a reassuring line for admins: if you are not using the AI agent, nothing changes.

How JSM desks pay instead

dev.to ran the JSM self service agent on a Service Collection Premium test site on 17 October 2026 and measured its cost: exactly 10 Rovo credits per reply, the same rate as a Quick answers message, with each reply logged as an invocation in the audit log. Atlassian lists that agent's cost as variable per billable event, so 10 credits reflects short answers in that mode. Request Resolver, the agent-facing counterpart, draws 100 credits per resolution plan it generates — $1.00 at the $0.01 overage price, though on a different meter from CSM's.

The older virtual service agent bills differently again: Premium and Enterprise plans include 1,000 assisted conversations a month, and beyond that they start at $0.30 per conversation. An assisted conversation counts whether the bot resolves the issue, escalates it, or the customer abandons the chat — a broader trigger than CSM's resolution meter.

For scale, dev.to sketches an internal desk with 20 agents and 1,000 employee chats a month at two replies each: 20,000 credits against included pools of 5,000 on Standard or 14,000 on Premium, or $150 and $60 in monthly overage respectively.

Why it matters

Per-resolution pricing moves the risk of AI performance from Atlassian to its customers: you pay only when the agent succeeds, but with no free tier, even modest volumes generate a bill from day one. The absence of sandbox support means teams must experiment on live customers to learn their own resolution rates — the very uncertainty that stalled Phil H.'s rollout. And with JSM desks migrating into Service Collection at renewal, the gap between CSM's $1 meter, Rovo credit consumption and per-conversation billing creates real confusion about what any given team will owe. dev.to's break-even math — $1 beats human handling time on an 8.6-minute ticket once agent cost exceeds $6.98 an hour — only pays off if the chats the AI resolves would otherwise have reached a person.