Migrating Complex Skill Groups to CXone Omnichannel Routing

How-To-Articles
1

Migrating Complex Skill Groups to CXone Omnichannel Routing

Executive Summary & Architectural Context

When migrating from a legacy on-premise PBX (like Avaya or Cisco) to NICE CXone, the most common architectural mistake is attempting a 1:1 translation of legacy “Hunt Groups” or “Split/Skills” into CXone Skills.

Legacy systems often required you to build 50 different Hunt Groups because they couldn’t dynamically evaluate agent proficiency or interaction channels. NICE CXone utilizes a true Omnichannel Routing Engine powered by Proficiency-Based Routing. If you migrate 50 legacy Hunt Groups directly into 50 CXone Skills, your Studio scripts will become a tangled mess of IF/ELSE statements, and cross-channel reporting will break.

This masterclass details the engineering blueprint for collapsing legacy Hunt Groups into consolidated CXone Skills, utilizing Proficiency levels and Channel typologies to achieve elegant, high-efficiency Omnichannel routing.

Prerequisites, Roles & Licensing

  • Licensing: NICE CXone (Omnichannel Routing enabled).
  • Roles & Permissions: ACD > Contact Settings > Skills, ACD > Users.
  • Platform Dependencies:
    • CXone Studio (for routing script modifications).

The Implementation Deep-Dive

1. The Consolidation Strategy (The Paradigm Shift)

Legacy Architecture (Avaya):
You had HuntGroup_Support_Voice, HuntGroup_Support_Email, HuntGroup_Support_Chat, HuntGroup_Support_VIP_Voice. (4 separate queues).

CXone Architecture:
You only need ONE conceptual routing group: Technical Support.
CXone separates the Channel from the Intent.

2. Creating the CXone Skills

  1. Log into the CXone ACD platform.
  2. Navigate to ACD > Contact Settings > Skills.
  3. Create Skill 1:
    • Name: IB_Voice_TechSupport
    • Media Type: Phone Call
    • Inbound/Outbound: Inbound
  4. Create Skill 2:
    • Name: IB_Email_TechSupport
    • Media Type: Email
  5. Create Skill 3:
    • Name: IB_Chat_TechSupport
    • Media Type: Chat

Note: While these are technically 3 separate Skills in the CXone database, they map to the exact same human agents.

3. Assigning Proficiency (The VIP Replacement)

Instead of creating a separate “VIP” queue, use Proficiency to manage escalation.

  1. Navigate to ACD > Users.
  2. Select your top-tier agent, “Jane Doe”.
  3. Go to the Skills tab.
  4. Assign IB_Voice_TechSupport to Jane with a Proficiency of 1 (Highest).
  5. Select a junior agent, “John Smith”. Assign him the same skill with a Proficiency of 5 (Lowest).
  6. The Routing Logic: When a call arrives, CXone evaluates everyone with the skill. It will always route the call to Jane (if she is available) before routing to John. If Jane is busy, it falls back to John. You have just eliminated the need for a separate VIP queue.

4. Omnichannel Elevation (Blending)

To make the agents truly omnichannel, you must configure how CXone handles conflicting media types. If Jane is typing an email, can she receive a phone call?

  1. Navigate to ACD > Contact Settings > Skills.
  2. Open IB_Email_TechSupport.
  3. Go to the Post Contact or Interrupt settings (depending on your CXone release).
  4. Elevation: You must configure Voice skills to interrupt Email skills. If Jane is drafting an email (lower priority SLA), and a voice call arrives (immediate SLA), the CXone MAX client must pause her email timer and force the voice call onto her screen.
  5. If you do not configure elevation correctly, agents will hide in long-running email interactions to avoid taking phone calls.

Validation, Edge Cases & Troubleshooting

Edge Case 1: The Studio Script Routing

In CXone Studio, you use the REQAGENT action to request an agent.

  • Troubleshooting: If you hardcode the Skill property in the REQAGENT block, you lose dynamic flexibility.
  • Best Practice: Use a snippet to dynamically map the Skill ID based on the incoming DNIS or an IVR database lookup. Assign the Skill ID to a string variable (e.g., TargetSkill), and map that variable to the REQAGENT action. This allows you to use a single monolithic Studio script to handle 50 different skills dynamically.

Edge Case 2: Reporting Metrics (AHT)

If you blend Voice and Chat into the same agent group, your Average Handle Time (AHT) reports will look erratic if you do not segment by Media Type.

  • The Trap: An agent might have an AHT of 300 seconds for Voice, and 1200 seconds for Chat (because they handle 3 chats concurrently). If you look at an aggregated AHT metric, it will say 750 seconds, which is useless for WFM forecasting.
  • Solution: In CXone Reporting, you must always slice Agent Performance dashboards by Media Type. Never look at blended AHT unless you are performing specialized cost-per-interaction financial modeling.

Official References