Get a first look at what's coming. The Developer Passport Australia Release Preview kicks off March 12. Dive in! 

How to Configure AWA for Incident and catalog task based on availability and capacity

DhathriC
Tera Contributor

Hello ServiceNow Community,

I am seeking guidance on configuring Advanced Work Assignment (AWA) to automatically assign new incidents to agents within a specific assignment group based on their current workload. Specifically, I aim to:

  • Identify active members within an assignment group.
  • Determine the number of active incidents assigned to each member.
  • Assign new incidents to the member with the fewest active incidents to ensure balanced workload distribution.

For example, if each member in a team has 3 tickets and one member has 2 tickets, the latest incident should be assigned to the member with the least number of tickets.

Could you provide guidance on how to configure AWA to achieve this functionality?

#AWA #Assignmentrules
8 REPLIES 8

Opps:

 

https://www.servicenow.com/community/agent-chat-routing-and-sidebar/understanding-servicenow-awa-wha...

 

https://www.youtube.com/watch?v=fANNto5TG-0

 

*************************************************************************************************************
Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/dratulgrover [ Connect for 1-1 Session]

****************************************************************************************************************
Advanced Work Assignment lets you automatically assign work items to your agents, based on their availability, capacity, and optionally, skills. AWA pushes work to qualified agents using work item queues, routing conditions, and assignment criteria that you define. This video provides an overview

I don't want the Rejection option for assigned to. How to achieve that?

 

Hi @DhathriC 

Rejection is an out-of-the-box functionality and cannot be removed. It is required from the user side. A user may choose not to act on it or may be busy, but this behavior is as per OOTB design.

*************************************************************************************************************
Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/dratulgrover [ Connect for 1-1 Session]

****************************************************************************************************************

Tanushree Maiti
Giga Sage

Assignment behavior in ServiceNow is controlled using the Assign By field in the Assignment Rule, which is part of Assignment Eligibility and configured within Queues.

TanushreeMaiti_1-1770731373485.png

 

The Assign By field has two options:

  • Most Capacity:
    Assigns the task to the eligible agent with the highest available capacity.

  • Last Assigned:
    Used for continuity; the system attempts to assign the task to the agent who last handled similar work, provided the agent is still eligible and has available capacity.

Also, skills can be enforced as mandatory during assignment too. Here is the detailed video - Advanced Work Assignment (AWA) Tutorial: Automatically assign work to agents by skill 

Ref: - AWA Assignment and Routing 

 

 

Please mark this response as Helpful & Accept it as solution if it assisted you with your question.
Regards
Tanushree Maiti
ServiceNow Technical Architect
Linkedin: