ServiceNow Advanced Work Assignment License and Pricing: What AWA Costs in 2026

Advanced Work Assignment is not a line item you can buy. It is a plugin whose entitlement rides on a subscription you already hold, and ServiceNow's published package descriptions do not name it at all. That includes the new ones: in April 2026 ServiceNow replaced the Standard, Professional and Enterprise ITSM tiers with Foundation, Advanced and Prime, and AWA appears in none of the three feature lists. So the honest answer to what AWA costs is that it usually costs nothing extra and occasionally costs a tier upgrade, and the only way to find out which applies to you is to look at your own contract. Here is how to work that out before the sales call, and what the real spend looks like once you do.

What Advanced Work Assignment actually is, in licensing terms

AWA is delivered as plugins, not as a product SKU. The base plugin is com.glide.awa, and the Agent Chat plugin com.glide.interaction.awa comes with it for the chat and messaging channels. An administrator with the admin role can activate them. That is the whole installation story, and it is why so many teams discover AWA is already sitting in their instance, switched off, after months of assuming it was something they had to purchase.

What it does is change the unit of assignment. Instead of a ticket landing in a group queue and waiting for somebody to pick it up, AWA pushes work into an agent's inbox based on group, availability, capacity and skills. Out of the box it handles Case, Incident, Chat, SMS, Walk-up, WhatsApp, Facebook Messenger and Line as service channels, and you can define custom channels for anything else. Since the Tokyo release you can also have work assigned automatically rather than offered for the agent to accept or reject, which matters more than it sounds: an accept and reject model still lets people cherry-pick by declining, and automatic assignment does not.

The gating condition that catches people is the interface. AWA has to be used with a workspace that includes the Agent Inbox. Any workspace with the Inbox module works, including Service Operations Workspace, but the classic list-and-form interface has nowhere to push work to. If your fulfillers still work in the platform UI, turning on AWA changes their day whether you planned for that or not.

The April 2026 ITSM repackaging, and why AWA is not in it

If you last looked at ServiceNow licensing before spring, the tier names on your renewal quote will not match your notes. As of April 2026 the ITSM packages are Foundation, Advanced and Prime, replacing Standard, Professional and Enterprise. Roughly:

• Foundation is the entry tier: basic Incident, Request, Asset and Cost, plus Virtual Agent, Predictive Intelligence and Now Assist for ITSM at an out-of-the-box level.
• Advanced adds the rest of the ITIL suite, Problem, Change, Major Incident, On-Call and Walk-up, along with Platform Analytics Advanced, Process Mining, and higher Assist allocations.
• Prime is everything in Advanced plus the custom AI capabilities, and it is described as the only tier that lets you build net-new custom AI skills and AI agents. It also now holds DevOps Change Velocity exclusively, which moved out of the middle tier in this repackaging.

Read those lists again and notice what is missing. Advanced Work Assignment is not mentioned in any of them. Neither is Agent Workspace, agent affinity, or routing generally. That is not an oversight in the summary, it is how ServiceNow packages routing: it travels with the workspace entitlement rather than being sold as a feature of a tier. Which means a comparison table of the three tiers, however carefully you read it, will never answer the question you actually have.

The rule that usually decides it

The practical test that longtime ServiceNow practitioners use is this: if you are entitled to ITSM Agent Workspace, you are entitled to Advanced Work Assignment for Incidents. And Agent Workspace has been entitled to new and existing ITSM customers by default. Put those together and for most customers with no unusual contract history, AWA for Incidents is included at the base ITSM level, not held behind the top tier.

The caveat is real and worth taking seriously. Entitlements are contractual, they vary by customer, and a subscription signed years ago under a different packaging can carry restrictions that today's documentation does not describe. AWA for CSM and for HR Service Delivery ride on those subscriptions rather than on ITSM, so a company with ITSM but not CSM cannot route cases with it. Nobody on the internet can read your contract. What you can do is stop treating this as a pricing question and start treating it as an entitlement question, which is a much shorter conversation with your account manager and one you can prepare for in ten minutes.

Before that call, check three things in your own instance: whether com.glide.awa already appears in the plugin list and whether it is active, which workspaces are deployed and whether any of them carry the Agent Inbox, and whether your fulfillers already hold workspace access. If the plugin is present and a workspace exists, you are almost certainly looking at a configuration project rather than a purchase.

What ServiceNow actually costs, when you need a number

ServiceNow does not publish list prices, and anyone quoting you a per-user figure for it is guessing. The nearest thing to real data comes from procurement platforms that see signed contracts. Vendr's ServiceNow data, last updated February 2026, puts the median annual contract value at about $127,117, with observed deals ranging from $42,842 at the low end to $695,435 at the high end across 108 purchases in its dataset, and an average saving of 8.1 percent on the deals it negotiated directly.

Two structural details from the same source matter more than the median when you are budgeting. Terms run one to three years, with three-year terms most common for enterprise agreements, and annual prepayment is standard, with monthly billing available at higher rates. And true-ups are annual: as your fulfiller count grows, the adjustment is priced either at renewal or through a mid-term amendment. That last one is the line that surprises finance, because the number you signed is not the number you pay if you hired. It is a good argument for watching software spend as it moves rather than finding out during a renewal conversation.

The cost lines nobody puts on the quote

Turning AWA on is cheap. Making it work is where the money goes, and almost none of it is licensing.

Package composition verified in August 2026 against a ServiceNow Community ITSM licensing article describing the April 2026 Foundation, Advanced and Prime tiers; plugin names, channels and role requirements against ServiceNow Community documentation for Advanced Work Assignment; contract figures against Vendr's ServiceNow marketplace data, last updated February 2026. ServiceNow does not publish list pricing and entitlements are contractual, so treat every figure here as a benchmark for a conversation rather than a quote. Verify your own entitlement with your account manager before you plan around it.

The configuration bill, in the order it arrives

The reason AWA projects run long is that four things all have to be right before a single ticket routes, and each one fails silently.

Service channels define what kind of work is routed. Queues hold it. Assignment rules decide which groups are eligible for which queue. Capacity is set per service channel, so an agent's limit for chats is separate from their limit for incidents, and getting those numbers wrong in either direction is the most common early complaint: too low and work pools in the queue while agents sit idle, too high and AWA cheerfully pushes eleven incidents at somebody.

Then there are the roles. Every member of a group named in an assignment rule needs the awa_agent role and access to the work item itself. Miss the role on two people out of nine and the rotation quietly runs across seven, which nobody notices until a workload review. This is the same failure shape as most ServiceNow routing problems, and it is worth checking membership properly rather than eyeballing the related list. ServiceNow group membership covers where membership actually lives and why the parent group you pointed the rule at may contain nobody at all.

AWA can also run alongside the legacy assignment rules in sysrule_assignment, provided the criteria are mutually exclusive. In practice that is harder to guarantee than it sounds, and overlapping conditions are a reliable source of tickets that get assigned twice or not at all. ServiceNow assignment rules execution order covers what runs when, and why a rule that looks correct gets overwritten before anyone sees it.

When AWA is worth it, and when it is the wrong purchase

AWA earns its configuration cost when three things are true: your fulfillers already live in a workspace, work arrives faster than people can triage it by hand, and you have real channel differences to model, such as chat that needs a response in seconds sitting next to incidents that can wait an hour. Push routing with per-channel capacity is genuinely good at that, and nothing you build with business rules will match it.

It is the wrong purchase in two situations. The first is when your agents are not in a workspace and do not want to be. AWA has no way to deliver work to the classic interface, so the project becomes a UI migration wearing a routing project's name, and those take a quarter, not a sprint. The second is when the work you need balanced does not all live in ServiceNow. The same engineer who holds four incidents also has a Jira ticket and two requests in a help desk, and AWA counts the ServiceNow number because that is the only number it can see. Capacity limits calculated on a fraction of somebody's workload produce a routing decision that is precisely wrong rather than roughly right.

That second case is what Assigner is built for. It sits beside ServiceNow rather than inside it, keeps one workload picture across every system the same people work in, routes by skill, current open work and real availability, and records which rule made each decision along with the candidates it passed over. It is a companion designed to help you decide the assignee rather than a two-way sync into your instance, and the AI assists while the rules stay yours. Pricing is published per user, so the honest comparison is against the configuration quarter and the tier conversation you would otherwise be having.

For the rest of the picture, ServiceNow Advanced Work Assignment covers how AWA routing actually behaves once it is on, ServiceNow round robin explains what ServiceNow does and does not ship for rotation, and ServiceNow assignment groups covers the group record that every one of these rules ultimately points at.