Omni-Channel Routing and AWA in ServiceNow Explained

A customer sends a chat message while another customer is waiting on a phone call. At the same time, several incidents arrive through email, and a high-priority case needs immediate attention. The service team has enough people, but the real question is: who should handle which request?

If every request simply goes to the next available agent, the result can be uneven. A technical issue may reach someone without the required skill, while an experienced agent may receive work that could have been handled by someone else.

This is where omni-channel routing and Advanced Work Assignment (AWA) become important. They help ServiceNow decide where work should go based on factors such as channel, queue, skills, availability, priority, and agent capacity.

What is actually going wrong?

Routing work sounds simple until an organisation has multiple channels, teams, and types of service requests.

A large service organisation may handle work through:

• Phone
• Chat
• Email
• Incidents
• Cases
• Tasks
• Requests
• Other digital channels

At the same time, agents may have different skills, availability, workloads, and capacity.

So the routing question is no longer simply: who is available?

It becomes: which available agent is eligible and has the right skills and capacity to handle this work?

For example, a network-related incident should ideally go to an agent with network skills. A request involving a specific product may need someone familiar with that product. A critical issue may also need to be handled before lower-priority work.

Without a proper routing model, organisations often depend on manual queue management, fixed assignment rules, or agents picking work themselves. As volumes increase, these approaches become harder to manage.

Why these terms matter

Before looking at the technical flow, it helps to separate omni-channel routing from Advanced Work Assignment.

What is omni-channel routing?

Omni-channel routing is the process of bringing work from different channels into a common routing model and directing it to the appropriate queue or agent.

The channel is only one part of the decision.

A simplified view:

1. Work arrives from phone, chat, email, incidents and cases
2. Routing logic evaluates the work
3. Queue and eligibility are determined
4. The work reaches the appropriate agent

The goal is to avoid handling each channel as a completely separate process.

A customer may start with chat and later create a case. The organisation still needs a consistent way to determine how that work should be handled.

Omni-channel routing provides that common approach.

What is Advanced Work Assignment?

Advanced Work Assignment (AWA) is ServiceNow functionality used to assign work to agents based on defined assignment criteria.

AWA looks beyond simple availability.

Depending on the configuration, assignment can consider:

• Required skills
• Agent availability
• Agent capacity
• Work item priority
• Assignment queues
• Eligibility rules
• Workload
• Other routing conditions

For example, imagine three agents are available. If a high-priority network incident arrives, sending it to the first available agent may not be the right approach.

AWA can use the configured routing criteria to identify agents who are eligible for that work and consider their available capacity.

Omni-channel routing vs AWA

A simple way to remember the relationship is:

1. Different channels feed into omni-channel routing
2. Queues and routing rules organise the work
3. AWA applies skills, availability and capacity
4. The work reaches the right agent

How does the routing process work?

A typical routing process can be understood in seven steps.

1. Work arrives

A piece of work enters ServiceNow. It could be:

• A phone interaction
• A chat
• An incident
• A customer case
• A task
• A request

The system first identifies what type of work has arrived.

2. Work is classified

The system needs enough information to understand the work. For example:

• Work type: Incident
• Priority: High
• Category: Network
• Required skill: Network Support

Classification is important because routing decisions depend on the information available about the work.

If the system does not know that an incident requires a network skill, it cannot use that skill as part of the assignment decision.

3. Work enters a queue

The work is placed into an appropriate queue or routing group.

A queue provides a place where work can wait until an eligible agent is available. For example:

• Network Issues Queue
• Hardware Support Queue
• Customer Service Queue
• Priority Support Queue

Queues help organise work before it reaches an individual agent.

4. Required skills are identified

The routing process can determine what skills are required. For example:

1. An incident arrives
2. Its category is Network
3. The required skill is Network Support

The system can then look for agents who have the required skill.

This is particularly useful in organisations where agents specialise in different technologies, products, languages, or customer segments.

5. Eligible agents are considered

The system identifies agents who are actually eligible to receive the work.

Being logged in or available does not automatically mean an agent should receive every type of work.

The routing decision can consider:

• Required skills
• Agent availability
• Capacity
• Queue membership
• Eligibility conditions
• Work priority

This reduces the chance of sending work to an agent who cannot effectively handle it.

6. Work is assigned

Once eligible agents have been identified, the routing logic selects an appropriate agent based on the configured rules. For example:

1. An incident requires a network skill
2. It enters the network queue
3. Eligible network agents are identified
4. Availability and capacity are checked
5. The work is assigned

The exact assignment behaviour depends on the organisation's configuration.

7. Agent capacity is updated

After work is assigned, the agent's workload changes.

This matters because routing should not treat an agent as equally available after they have already received several pieces of work.

Capacity helps answer: can this agent realistically take more work right now?

That is different from simply asking: is this agent online?

Why skills matter in routing

Skills connect the requirements of the work with the capabilities of the agent.

Consider a service organisation supporting networking, databases, and workplace devices. An incident related to a database problem should ideally be routed to an agent who understands database issues.

Without skill-based routing, an incident simply goes to the next available agent.

With skill-based routing:

1. The incident arrives
2. The required skill is identified
3. Eligible agents are found
4. Availability and capacity are checked
5. The work is assigned

This can reduce unnecessary transfers and help agents work on issues they are equipped to handle.

Skills can represent more than technical knowledge. Depending on the business, they may represent:

• Language
• Product knowledge
• Certification
• Geography
• Customer segment
• Specialised support capability

Why capacity matters

Availability and capacity are not the same thing.

An agent might be logged in and technically available but already handling several active tasks. For example:

• Agent A: available, current work 5 items, capacity nearly full
• Agent B: available, current work 1 item, capacity available

If both agents have the required skill, capacity provides another factor for deciding where the work should go.

This is important in high-volume environments because simply distributing work based on availability can create uneven workloads.

What does this mean for the business?

Routing may sound like a technical configuration, but it affects day-to-day service operations.

Faster resolution

When work reaches an agent with the right skills, there may be fewer transfers and less time spent understanding issues that are outside the agent's area.

That can contribute to faster resolution.

Better use of skilled employees

Specialised employees are often limited resources.

If highly skilled agents spend too much time handling work that other agents could manage, the organisation is not using those skills efficiently.

Skill and capacity-based routing helps distribute work more appropriately.

Customer experience

Customers generally do not care which internal queue or routing rule was used.

They care about getting their issue handled without repeatedly explaining the problem or being transferred between teams.

Routing therefore has a direct connection to the customer experience.

Sales and revenue impact

For organisations where service issues affect customers, partners, or active deals, delays can have a wider business impact.

A customer waiting too long for support may delay a renewal, expansion, or new purchase.

Sales teams may also spend additional time following up with service teams when important customer issues are not reaching the right people quickly.

So routing is not only an operational concern. It can also affect customer relationships and revenue-related activities.

Lower operational cost

Manual queue management requires people to monitor workloads, move work between queues, and follow up on assignments.

Better routing can reduce some of that manual coordination and allow service teams to spend more time resolving issues.

Why do traditional routing models struggle?

Traditional routing approaches often depend on simple rules such as: if the category is Network, send it to the Network queue.

That works for straightforward environments.

The difficulty starts when the routing decision becomes more complex. Organisations may have:

• Separate queues for different teams
• Fixed assignment rules
• Manual reassignment
• Spreadsheet-based workload tracking
• Skills maintained outside the service platform
• Custom scripts for individual routing scenarios
• Different routing approaches for different channels

Over time, these rules can become difficult to maintain.

A change in one team structure may require changes to several routing rules. A new skill may require additional configuration. A new channel may introduce another assignment process.

The challenge is therefore not simply that legacy systems cannot route work. The bigger issue is that routing logic can become fragmented and difficult to manage as the organisation grows.

Traditional vs modern routing

The goal is not to add complexity for its own sake.

It is to use the information already available about the work and the agent to make routing decisions that fit the service operation.

How omni-channel routing and AWA work together

The complete journey can be viewed like this:

1. A customer interaction or piece of work arrives through a channel
2. The work is classified
3. It enters a queue
4. Required skills are identified
5. Eligible agents are found
6. Availability and capacity are checked
7. The assignment is made
8. The agent completes the work

Omni-channel routing provides the broader framework for bringing work from different channels into the routing process.

AWA then helps determine which agents are eligible to receive that work based on the configured assignment criteria.

This allows organisations to move away from "who is free?" toward "who is eligible, available, and has the capacity to handle this work?"

Where automation and AI can help

Automation can remove some of the manual steps around routing.

For example, information from an incoming request can be used to determine:

• Work type
• Priority
• Category
• Required skills
• Assignment group

AI can also support classification and recommendation scenarios where the organisation has the appropriate data and configuration.

The important point is that AI does not replace the underlying routing model.

The organisation still needs clear rules around:

• Which work goes to which queue
• Which skills are required
• How capacity is measured
• Which priorities take precedence
• What happens when no eligible agent is available

Good automation depends on having a clear process underneath it.

Keeping routing rules up to date

Routing is not something that can simply be configured once and forgotten.

Teams change. Skills change. Products change. Customer priorities change.

For example, if a new product is introduced, the organisation may need to:

1. Define the new support skill
2. Update skill mapping
3. Identify eligible agents
4. Review the routing rules

Without regular maintenance, the routing model can become inaccurate.

It is also useful to monitor whether:

• Skills are assigned correctly
• Queues are receiving the expected work
• Agents are overloaded
• Some queues are consistently building backlogs
• Priority work is being handled appropriately
• Routing rules are still aligned with the service model

How can you measure routing effectiveness?

Organisations can use operational metrics to understand whether routing is working as expected.

These metrics should be viewed together.

For example, a low assignment time does not necessarily mean routing is working well if the transfer rate is high. Work may be assigned quickly but sent to the wrong agent.

The goal is to balance speed, skills, capacity, and resolution quality.