ServiceNow Advanced Work Assignment: Round Robin, License, Skills, and Capacity

How Advanced Work Assignment routes a work item

The sequence is short and worth memorizing, because almost every AWA support thread is really a question about which of these three steps failed. A work item is created on a table AWA watches. It is added to a work item queue based on the matching conditions you wrote on that queue. It is then offered to the agents in the groups listed on that queue Assignment Eligibility related list, filtered to whoever is actually available, and ranked by the assignment strategy you picked. Agents see the offer in the Agent Inbox inside a workspace, accept it, and the record gets an owner. Turning on the Auto-assign option skips the accept step and pushes work straight to the agent. Two details do most of the damage. The Eligible at field on each eligibility record controls overflow: 0 means the primary group, and a higher number means that group only becomes eligible after a wait, so work that looks stuck is often just sitting in its first tier. And AWA offers work to people, not to groups, which is a genuine departure from assignment rules and the reason presence states matter so much.

Does ServiceNow Advanced Work Assignment do round robin?

Close, but it is worth being precise, because the gap costs teams real fairness. AWA gives you two assignment strategies on the Assignment Rules screen. Last Assigned routes the work item to the agent who has gone the longest without being assigned anything, and this is what nearly everyone means when they say AWA does round robin. Most Capacity routes to the agent with the greatest remaining capacity, where capacity starts at a per-channel value and decreases as work items are accepted. Last Assigned is idle-time rotation, not circular rotation. Classic round robin walks a list in order so that over any window everyone gets the same count. Last Assigned looks only at who has waited longest, so an agent who closes three quick tickets keeps re-entering the front of the line while a colleague working one long escalation sits at the back and stays there. On paper both look fair. In a month of real handling times they are not the same, and the difference shows up as the same two people carrying the queue. Neither strategy supports weighting, so a half-time agent, a new hire, and a senior engineer all take the same share unless you build something custom. We compare rotation and load models directly on our round-robin assignment and workload balancing pages.

ServiceNow Advanced Work Assignment license and prerequisites

AWA is not a standalone SKU you can add to a bare platform subscription, and this is the single most common surprise in scoping. The base plugin is com.glide.awa, activated by an admin from the All Applications list, and it depends on an active subscription to a product that includes it, in practice ITSM, CSM, or HR Service Delivery. The domain-specific content plugins are separate: ITSM AWA, CSM AWA, and HR AWA each ship ready-made service channels, queues, inbox layouts, and assignment eligibility records so you are not building from an empty table. Advanced Work Assignment for Incidents is its own plugin, com.snc.incident.awa, and entitlement generally follows ITSM Agent Workspace rather than being sold separately. The harder prerequisite is the workspace. AWA has to be used with a workspace that includes the Agent Inbox, because that inbox is where agents receive and accept offers. Any workspace type qualifies, including Service Operations Workspace, but if your agents live in the classic list-and-form interface, AWA means moving them. Worth knowing in the other direction: AWA does not require Agent Chat, though Agent Chat depends on AWA, so installing chat brings AWA with it. Because entitlement wording shifts between releases, confirm your exact position with your account team rather than with a forum post.

Capacity, skills, and agent affinity: what each one really measures

AWA can weigh three things beyond raw availability, and each has a caveat worth understanding before you design around it. Capacity is configured at the service channel level. When an agent goes Available for a channel they start with a number of work item slots defined in awa_agent_presence_capacity, and that number falls as they accept items. The default work item size and default capacity on the channel therefore decide almost everything about distribution, and the honest limitation is that a slot is a slot: a password reset and a P1 outage consume the same unit. Skills-based routing narrows the eligible pool to agents whose skills match, which genuinely helps on specialist queues, but it also shrinks the group AWA can balance across, so a skill applied too tightly turns into a single overloaded person. Agent affinity is the optional one and the one to be most careful with, because it deliberately routes by work history, related task, or account team affinity. Continuity is real value for a customer mid-issue. It is also, structurally, the opposite of fair distribution: the person who handled the account last keeps getting the account. Turning affinity on and then asking why the queue is uneven is a common self-inflicted wound. There is also a rejection path worth configuring deliberately, since the awa_reject_reason table carries a Reassignable flag that decides whether declined work returns to the pool or stalls.

When Advanced Work Assignment is not the right tool

AWA is the correct answer for a service desk that already lives in a ServiceNow workspace, routes work that extends Task or Interaction, and has agents willing to manage presence states. Three situations reliably outgrow it. The first is fairness with weighting. Neither Last Assigned nor Most Capacity supports weighted rotation, so part-time agents, ramping new hires, and senior engineers all take the same share until somebody writes a script, and that script becomes the thing nobody maintains. The second is scope. AWA cannot see work outside ServiceNow, so an agent also handling inbound sales leads or ops requests looks idle to the queue and is not. The third is explainability. When an assignment is questioned you are reconstructing the answer from queue conditions, eligibility tiers, presence history, and capacity math, which is a platform-team task rather than a service desk manager task. Assigner sits beside ServiceNow rather than replacing it, routes support tickets, leads, and ops work through one engine with skills-based routing and availability routing included, and publishes its price at $12 per user per month. Our ServiceNow routing alternative page makes the comparison in full, including the cases where staying native is clearly right. It is a companion, not a live two-way sync, and it is built to help rather than to guarantee an outcome.

What is ServiceNow Advanced Work Assignment?

Advanced Work Assignment, usually shortened to AWA, is the ServiceNow framework that pushes work items to agents automatically based on availability, capacity, and optionally skills. Instead of writing a rule that stamps an assignment group, you define service channels, work item queues with matching conditions, and eligibility pools, and AWA offers matching work to individual available agents through the Agent Inbox.

Does ServiceNow Advanced Work Assignment support round robin?

Effectively yes, through the Last Assigned strategy, which routes each work item to the agent who has gone longest without an assignment. It is idle-time rotation rather than true circular round robin, so counts drift apart when handling times differ. The alternative is Most Capacity, which routes to whoever has the most capacity remaining. Neither strategy supports weighting, so every agent takes an equal share by default.

What license do you need for ServiceNow Advanced Work Assignment?

AWA is not sold on its own. The base plugin com.glide.awa requires an active subscription to a product that includes it, in practice ITSM, CSM, or HR Service Delivery, and an admin activates it from the All Applications list. Advanced Work Assignment for Incidents is a separate plugin, com.snc.incident.awa, whose entitlement generally tracks ITSM Agent Workspace. Confirm your position with your account team, since wording changes between releases.

How do you set up Advanced Work Assignment in ServiceNow?

Activate the com.glide.awa plugin plus the domain plugin for your area, which supplies ready-made records. Confirm or create the service channel for the table you want routed. Build a work item queue with matching conditions that catch the right records. Add groups to the Assignment Eligibility related list on that queue, setting Eligible at to 0 for the primary group. Pick Last Assigned or Most Capacity on the Assignment Rules screen, set channel capacity, and make sure agents have the Available presence state in a workspace with the Agent Inbox.

What is assignment eligibility in Advanced Work Assignment?

Assignment eligibility is the related list on a work item queue, stored in awa_eligibility_pool, that names which agent groups can be offered work from that queue. The important field is Eligible at. A value of 0 makes the group the primary pool that gets offered work immediately, and higher values create overflow tiers that only become eligible after a wait. That staggering is how AWA escalates unclaimed work rather than dumping it on everyone at once.

How does capacity work in Advanced Work Assignment?

Capacity is set per service channel. When an agent becomes Available for a channel they start with a number of work item slots defined in awa_agent_presence_capacity, and each accepted item consumes slots according to the work item size on the channel. The Most Capacity strategy then routes to whoever has the most left. The limitation is that a slot measures count, not effort, so a trivial request and a major incident use the same capacity.

Why is Advanced Work Assignment not assigning work?

Usually one of four things. The work item matches no queue condition, so it is never picked up and no error appears. Or the queue has no eligible group, or the only groups are on a higher Eligible at tier that has not opened yet. Or agents have no Available presence state, or are not in a workspace containing the Agent Inbox, so there is nobody for AWA to offer to. Or all eligible agents are at full capacity for that channel.

What is the difference between assignment rules and Advanced Work Assignment?

Assignment rules are the older mechanism: they run during the save and stamp an assignment group or user onto the record, and they cannot overwrite a field that already holds a value. AWA runs after the record exists and offers work to individual agents based on live availability and capacity, through the Agent Inbox. The two can coexist only if their criteria are mutually exclusive, otherwise a rule that fills assignment_group first can leave AWA with nothing to do.