The best AI service desk agent for most companies is the one their ITSM already ships: Now Assist on ServiceNow, the virtual service agent and Rovo on Jira Service Management, Freddy AI on Freshservice Enterprise. Buy a separate agent only when your ticketing system is the thing you want to leave, and in that case Atomicwork is the one that publishes a price per resolved outcome. Standalone Moveworks is the pick we would steer a non-ServiceNow shop away from in 2026. It is still a strong product, but ServiceNow now owns its roadmap and it is priced on total headcount.
Prices below were checked on each vendor's live pricing page or documentation on October 27, 2026. Where a vendor says "contact sales", the table says so.
| Product | Best fit | Pricing model (checked Oct 27, 2026) | Published price? | Who should not buy it |
|---|---|---|---|---|
| ServiceNow Now Assist / EmployeeWorks | Shops already on ServiceNow ITSM | AI bundled into every package; consumption pool | No, contact sales | Anyone not on ServiceNow |
| Moveworks (standalone) | Large ServiceNow customers wanting the Moveworks front end | Per employee per year, annual contract | One public list price: $150/user/year (AWS Marketplace, 1,000 to 2,500 users) | Non-ServiceNow shops, anyone under ~1,000 employees |
| Atomicwork | Mid-market teams replacing a weak ITSM, or adding an agent to JSM/ServiceNow per outcome | Platform from $25,000/year, or $1 to $3+ per outcome | Yes, partly | Large enterprises happy with their ITSM who just want deflection |
| Freshservice Freddy AI Agent | Freshservice customers on Enterprise | Included in Enterprise (1,200 sessions per license per year) | Enterprise tier is contact sales | Freshservice Starter, Growth or Pro customers expecting it in their plan |
| Jira Service Management virtual service agent + Rovo | Atlassian shops, engineering-led IT | 12,000 assisted conversations/year included on Premium/Enterprise, then from $0.30 each | Yes, overage rate | Teams on JSM Standard, or IT orgs whose requests live outside Jira |
What ServiceNow's $2.85B Moveworks Deal Changed for Customers
ServiceNow now sets Moveworks' roadmap, and its published statements are about folding Moveworks into the ServiceNow platform, with nothing said about rival ITSM platforms. ServiceNow agreed to buy Moveworks for $2.85 billion in March 2025 and completed the acquisition on December 15, 2025. The closing release says about 250 customers already used both products, and that ServiceNow "is already one of Moveworks' more than 100 technology integrations." It says nothing about the others.
What followed, in ServiceNow's own words:
- February 26, 2026, EmployeeWorks: ServiceNow launched EmployeeWorks, which brings Moveworks' chat and search into the ServiceNow platform, alongside a Level 1 Service Desk AI Specialist slated for general availability in Q2 2026. The same coverage reports that Moveworks remains a standalone product that can be deployed on its own or inside a ServiceNow implementation.
- April 2026, AI in every package: on the Q1 2026 earnings call, ServiceNow said "AI, data, security and governance are now built into every product and package, not a separate purchase." We covered the packaging change in ServiceNow Eliminates AI Sidecar Purchases.
- May 5, 2026, Otto: the Otto launch release says Otto "combines the intelligence of Now Assist, Moveworks, and AI Experience" and "will be rolled out across all products in the year ahead." It names no third-party ITSM integrations.
Moveworks' integrations page still lists Jira, Zendesk, Freshservice, BMC Helix and Ivanti Service Desk as of October 27, 2026. So nothing has been switched off. What you lack, if your tickets live in Jira or Freshservice, is a published commitment that those connectors get the same investment as the ServiceNow path. A three-year contract signed today will renew into whatever Otto becomes.
The strongest case for Moveworks is its track record. Moveworks' own Broadcom case study reports 88% of support requests resolved autonomously as of 2025, up from about 10% at launch, across more than 75,000 IT issues. If you run ServiceNow and want that front end, you no longer need to buy it separately to get the direction of travel, because ServiceNow is shipping it into the platform.
How Each Vendor Defines "Resolved"
No two vendors count a resolution the same way, so a published deflection rate tells you little until you know the formula behind it. Ask for the definition before you compare numbers.
- ServiceNow calculates deflection in Now Assist in Virtual Agent as resolved queries divided by total query responses, and marks a query resolved when "the user found the response to be useful and effective or the user didn't provide any feedback," so silence counts as success. Every unrated chat pushes this number up.
- Freshservice defines ticket deflection rate as queries resolved by Freddy AI Agent "without human help", with no negative feedback and no ticket created. That is stricter, because a conversation that ends in a ticket counts against it.
- Jira Service Management uses two definitions. The help center performance page counts a conversation as resolved when the virtual service agent handled it without any human intervention, while the conversation view requires the customer to mark it resolved. A conversation resolved and then escalated later can show as resolved in the performance metrics and escalated on the conversations page.
- Moveworks does not define "autonomous resolution" on the Broadcom case study page. Ask for the formula in writing.
- Atomicwork reports 50% deflection "out of the box" at Abzena and 65% at Ammex, and 50% less ticket volume at Zuora, on its own customer page. Its outcome pricing (below) forces a sharper definition, because it bills for each one.
Treat every number in this section as a vendor or customer claim. For planning, assume your first-quarter rate will be well under any figure here, and that it rises only as fast as your knowledge base improves.
What Each Option Costs at the Same Workload
On the same workload, the built-in agents cost a small fraction of a standalone agent priced on headcount. The workload: 2,500 employees, 25 IT agents, and 3,000 employee conversations with the agent a month (36,000 a year), of which 40% resolve without a human (14,400 a year). Seat and platform licences for the ITSM itself are excluded unless noted, because you pay those either way.
For standalone Moveworks, the only public price is the AWS Marketplace listing: $150 per user per year on a 12-month contract for 1,000 to 2,500 users. At 2,500 employees that is $375,000 a year at list, before implementation. Negotiated prices will be lower, but the unit is every employee, whether they ever open a ticket or not.
Jira Service Management Premium and Enterprise include 12,000 assisted conversations a year on annual billing (1,000 a month on monthly billing). Atlassian set the overage at $0.30 per assisted conversation, with volume discounts, when it introduced consumption pricing in October 2024, and its billing documentation still points to that row of the pricing page. The extra 24,000 conversations cost about $7,200 a year at the starting rate. That covers the virtual service agent only: Atlassian's usage-based pricing page says billing for Rovo credits and its other meters "begins on Dec 3, 2026 for most meters," so model Rovo use separately. Atlassian's per-agent seat prices sit in a calculator that did not render a figure when we checked; get them from the quote.
Atomicwork's pricing page publishes three outcome plans: $1 per resolved knowledge query (25,000 outcomes a year minimum), $2 per access request handled end to end (12,000 minimum) and from $3 per ticket goal achieved (8,000 minimum). If you keep ServiceNow or JSM, Atomicwork's "bring your own platform" option has no platform fee. At 14,400 knowledge resolutions you still pay the 25,000 floor, so $25,000 a year. Its full platform starts at $25,000 a year for up to 250 end users, so a 2,500-person company lands in the Business or Enterprise tier, which is contact sales.
On Freshservice, Freddy AI Agent (Classic) is included in the Enterprise plan, and each Enterprise licence carries 1,200 sessions a year. With 25 agent licences that is 30,000 sessions. A session is one unique user interacting with the agent in a 24-hour window, so 36,000 conversations is likely to land close to the allowance. Freshworks does not publish the overage rate; it says to contact your account manager. Enterprise itself is contact sales. Below it, Starter is $19, Growth $49 and Pro $99 per agent per month on annual billing, and Freddy AI Copilot is a $29 per agent per month add-on.
ServiceNow Now Assist is contact sales. AI is included in every package since the April 2026 change, but ServiceNow publishes neither package prices nor the size of the consumption pool behind them. Negotiate the pool size, the overage unit rate and price protection on renewal as separate line items.
The ranking at this workload: JSM is cheapest and most transparent, Atomicwork per-outcome is next and the only one that bills on results, Freshservice and ServiceNow cannot be priced without a quote, and standalone Moveworks costs the most by a wide margin.
What Has to Be Connected Before Any of These Work
An agent that cannot reach your identity provider, HR system and device manager can answer questions but cannot fix anything, and most of the resolution rate comes from fixes. Password resets need Okta or Entra ID. "I need access to X" needs your identity governance or group management. Onboarding needs Workday or your HRIS. "My laptop is slow" needs Intune or Jamf.
Moveworks has the widest catalogue, with Okta, Workday and Microsoft Intune among the listed integrations. Atomicwork names Okta, Workday, Microsoft Entra and Intune on its help desk page. The built-in agents depend more on what already sits in your ITSM: ServiceNow's agents act on the workflows and CMDB you have built, and JSM's agent acts on Jira request types and the knowledge in Confluence and connected sources.
The practical test: list your ten highest-volume ticket categories and mark which system has to change for each one to close. If the answer is mostly "the knowledge base", any of these agents will do. If it is mostly Okta, Entra and Intune, check that each integration can write, not just read, in your tenant before you sign.
Who Should Not Buy a Standalone Agent
If your ITSM platform already ships an agent, a second one mostly adds another knowledge base to maintain and another renewal to negotiate. That is the default case for ServiceNow customers (Now Assist is in the package), for JSM Premium customers (12,000 conversations are already paid for) and for Freshservice Enterprise customers (sessions come with each licence).
A standalone agent earns its place in three situations:
- Your ITSM is the problem. If you are on an old on-premises tool and the migration is coming anyway, Atomicwork's combined platform and agent is a reasonable replacement for a mid-market team.
- Your requests span several ticketing systems after an acquisition or across IT and HR, and you need one front door. This was Moveworks' original pitch. For a non-ServiceNow buyer, weigh it against the roadmap risk above.
- You want to pay only for results. Atomicwork's per-outcome plans on top of JSM or ServiceNow are the only published pricing here that moves with resolution.
And who should not buy each built-in option: ServiceNow's agent is wrong for anyone not already on ServiceNow, since the agent is the smallest part of that purchase. Freshservice's agent is wrong for teams on Pro or below who assumed Freddy AI Agent was in their plan; it is listed for Enterprise. JSM's agent is wrong for IT teams on Standard, which does not include the assisted conversation allowance, and for organisations whose employees never touch Jira.
The Criteria That Predict Regret
Buyers who regret this purchase usually priced it on the wrong unit or measured success with the vendor's definition. Check these before you sign:
- The billing unit: per employee (Moveworks), per agent seat plus conversations (JSM), per session (Freshservice), per outcome (Atomicwork) or a consumption pool (ServiceNow). Model each at your real volume and at double it.
- The resolution formula. Write your own definition into the contract (for example, no ticket created within 72 hours on the same topic) and measure it yourself.
- Change-of-control terms. The Moveworks deal is a live example. Ask for price protection and integration continuity clauses that survive an acquisition. Our coverage of Freshworks buying Torii shows the same question arising elsewhere in ITSM.
- Write access. An agent with read-only access to Okta cannot reset a password.
What changes the answer: a ServiceNow written commitment to fund Moveworks' non-ServiceNow connectors would reopen it for Jira and Freshservice shops. A published Freshservice overage rate would make Freddy easier to recommend. An outcome guarantee like Atera's 50% resolution guarantee from any of the five would shift risk to the vendor.
What to Do This Quarter
This Week:
- Pull the last 90 days of tickets and rank the top ten categories by volume. Mark which system has to change for each to close.
- Check what your current ITSM plan already includes: assisted conversations on JSM, sessions on Freshservice Enterprise, the AI package on ServiceNow.
This Month:
- Turn on the built-in agent for your top three knowledge-only categories and measure resolution with your own definition, not the dashboard's.
- If you are on Moveworks without ServiceNow, ask your account team in writing what happens to your connectors at renewal.
Before Your Next Renewal:
- Get an Atomicwork per-outcome quote as a benchmark, even if you do not buy it. It is the only published price that tells you what a resolution is worth.
- Put price protection, a resolution definition and change-of-control terms into whichever contract you sign.
The Bottom Line
Email suites absorbed standalone spam filtering the same way: the platform underneath took over the feature. ServiceNow bought the category leader, put it in every package and folded it into Otto. Atlassian and Freshworks priced their agents into the tiers most mid-sized IT teams already pay for. The standalone agent is now a choice you make when your ITSM is weak or fragmented, and Atomicwork's outcome pricing is the clearest way to make it.
Start with the ten-category ticket list. It tells you which integrations you need, and the integrations tell you which agent to buy.
Continue Reading
- ServiceNow Eliminates AI Sidecar Purchases for All Customers
- ServiceNow's AI Specialists Resolve Tickets 99% Faster
- Atera Guarantees 50% Ticket Resolution or Money Back
- AI Agents Cut ITSM Costs 50% While Resolving 80% of Tickets
- Atlassian Says Rovo Sends Data to Third-Party LLMs by Default
- Glean Alternatives 2026: Copilot, Rovo, Onyx and Quick Compared