Migrating CXone Personal Connection Dialer Strategies to List-Driven Flows

How-To-Articles
1

Migrating CXone Personal Connection Dialer Strategies to List-Driven Flows

Executive Summary & Architectural Context

Legacy outbound dialers operated on a very simple premise: upload a CSV file, press “Start”, and let the predictive engine dial as fast as possible to keep agents busy.

Modern compliance laws (TCPA in the US, Ofcom in the UK) have made traditional “spray and pray” predictive dialing incredibly dangerous. If your abandonment rate exceeds 3%, you face massive fines. Furthermore, customers no longer answer unknown numbers. To achieve high contact rates, outbound campaigns must be intelligent, context-aware, and highly targeted.

NICE CXone Personal Connection (PC) is a patented outbound dialer that eliminates the predictive delay (the “telemarketer pause”). However, migrating legacy campaigns into PC requires abandoning generic CSV uploads in favor of List-Driven Routing Strategies. This masterclass details how to construct advanced dialer strategies in CXone, utilizing Skill mapping, dynamic filtering, and cadence management.

Prerequisites, Roles & Licensing

  • Licensing: NICE CXone (Personal Connection Add-on).
  • Roles & Permissions: Outbound > Skills > Edit, Outbound > Campaigns > Edit.
  • Platform Dependencies:
    • Access to the PC Dialer Configuration interface.

The Implementation Deep-Dive

1. Creating the PC Skill (The Engine)

In CXone, the Outbound dialer is not a separate application; it is a Skill.

  1. Navigate to ACD > Contact Settings > Skills.
  2. Click Create New.
  3. Media Type: Phone Call.
  4. Inbound/Outbound: Outbound.
  5. Outbound Strategy: Select Personal Connection.
    • Note: If you select Manual, agents must click every record. If you select Predictive, the system dials ahead. PC is the optimal balance of efficiency and compliance.

2. Defining the Calling Strategy (Cadence)

You cannot call the same customer 5 times a day. You must define a cadence.

  1. Open your newly created PC Skill.
  2. Go to the Parameters tab.
  3. Locate Cadence Settings.
  4. Maximum Attempts per Record: Set to 3.
  5. Minimum Rest Period: This is critical. If a call goes to voicemail, the dialer should not attempt the record again immediately. Set the rest period to 24 Hours.
  6. Timezones: You must map the contact’s zip code or area code to a timezone database to ensure the dialer does not call a customer in California at 5:00 AM EST. Enable strict timezone enforcement.

3. The Calling List and Filter Logic

Instead of building 10 different campaigns for 10 different states, upload a single master list and use dynamic filtering.

  1. Navigate to Outbound > Calling Lists.
  2. Upload your master list (ensure columns for Phone, State, LeadScore).
  3. Return to the PC Skill. Go to the Filters tab.
  4. Instead of dialing the list top-to-bottom, define a filter to prioritize high-value targets.
    • Filter Condition: LeadScore > 80 AND State = 'NY'.
  5. Apply the filter. The dialer will instantly sort the master list and only dial records matching that criteria for the current session. When the New York session ends, you simply change the filter to State = 'CA', reusing the same list and same skill.

4. Handling Call Analysis Responses (Answering Machines)

When PC dials, it must know what to do before the agent hears audio.

  1. In the PC Skill, go to the Call Analysis tab.
  2. Define the routing logic:
    • Live Voice: Connect to Agent.
    • Answering Machine: Do not connect to the agent. Select the action Play Message.
    • Message: Upload a pre-recorded .wav file (“Hi, we are trying to reach you regarding your account…”). The dialer will dynamically wait for the voicemail beep and inject the audio file in the background without wasting an agent’s time.

Validation, Edge Cases & Troubleshooting

Edge Case 1: The “No Ports Available” Error

If you activate a Predictive PC skill and assign 50 agents to it, but the dialer isn’t making any calls, you may have exhausted your CXone Voice Ports.

  • The Trap: Predictive dialing requires a massive multiplier of voice ports. If your pacing ratio is 3:1 (dialing 3 lines for every 1 available agent), 50 agents require 150 active outbound ports. If your CXone contract only includes 100 ports, the dialer will stall.
  • Solution: You must adjust the Pacing Aggressiveness down in the Skill Parameters, or move from Predictive to Progressive dialing, which operates on a strict 1:1 port ratio.

Edge Case 2: DNC (Do Not Call) Scrubbing

Uploading a DNC list is not enough; you must ensure the skill is actively using it.

  • Troubleshooting: If agents report calling customers who explicitly opted out yesterday, your PC Skill is likely disconnected from the master DNC group.
  • Solution: In the PC Skill settings, verify the DNC Group is explicitly assigned. Furthermore, ensure your Studio Script for inbound calls contains a ManageDNC action so that if a customer calls the inbound line to complain, their number is instantly written to the global DNC table, instantly protecting the Outbound PC dialer from calling them again.

Official References