Configuring WFM Planning Groups for Blended Inbound/Outbound Agent Pools

How-To-Articles
1

Configuring WFM Planning Groups for Blended Inbound/Outbound Agent Pools

Executive Summary & Architectural Context

In many sales and service organizations, the workforce is divided into “Silos”: one team is dedicated to Inbound (answering the phones) and another is dedicated to Outbound (making follow-up sales calls or collections). This siloed approach is a recipe for massive operational inefficiency. At 10 AM, the Inbound team might be overwhelmed with a 5-minute wait time, while the Outbound team is sitting idle, waiting for the “Predictive Dialer” to find a fresh lead. To fix this, a supervisor has to manually log into the WFM tool, search for 20 agents, change their work plan, and click “Save.” By the time the agents are moved, the inbound peak has already passed. Now, the Inbound team is overstaffed and the Outbound team is failing to hit their daily sales targets because they were pulled off the dialer too late.

A Principal Architect eliminates these manual “Tug-of-War” moments by implementing Blended Planning Groups. By grouping Inbound and Outbound traffic into a single planning entity, the Workforce Management (WFM) engine (Genesys Cloud or NICE CXone) can generate a single, unified schedule. The engine understands that an agent’s primary job is to answer the phone (Immediate Work) but, when the phones are quiet, they should automatically be used for outbound dialing (Deferred/Predictive Work). This “Automated Blending” ensures that your agents are always occupied, your service level is stable, and your sales targets are hit without a supervisor ever having to move a single agent manually.

This masterclass details how to architect planning groups and service goal groups for a modern, blended contact center environment.

Prerequisites, Roles & Licensing

Licensing & Permissions

  • Licensing Tier: Genesys Cloud CX 1, 2, or 3. NICE CXone. (Outbound licenses required).
  • Granular Permissions:
    • WFM > Planning Group > View, Add, Edit
    • WFM > Service Goal Group > View, Add, Edit
    • Outbound > Campaign > View
  • Dependencies:
    • Interaction Metadata: Inbound and Outbound interactions must be clearly identifiable via different Queues or Media Types.
    • Predictive Dialer: Configured and active for the outbound pool.

The Implementation Deep-Dive

1. The Architectural Strategy: The “Immediate vs. Deferred” Balance

WFM planning groups work by categorizing work into two types:

  • Immediate (Inbound): Must be answered within seconds (Service Level).
  • Deferred (Outbound): Can wait for minutes or hours (Average Speed of Answer / Backlog).

The Principal Architect’s Strategy:
Create a Unified Planning Group. Instead of a “Sales_In” and “Sales_Out” group, create a single “Sales_Blended” group. The WFM engine then calculates the total labor requirement by summing the “Immediate” demand and the “Deferred” demand.

2. Configuring Service Goal Groups

The Service Goal Group tells the engine how to prioritize the work within the blended pool.

Step 1: Set the Primary Goal (Inbound)

  • Metric: Service Level.
  • Target: 80% in 20 seconds.
  • Architectural Reasoning: The engine will prioritize staffing for this goal first. If the inbound volume is high, the engine will “Borrow” capacity from the outbound task.

Step 2: Set the Secondary Goal (Outbound)

  • Metric: Average Speed of Answer (ASA) or “Workload Completion.”
  • Target: 100% of the dialer list completed by 5 PM.
  • Architectural Reasoning: During the “Lulls” in the inbound day, the engine sees that it has “Excess Capacity” relative to the 80/20 goal. It then automatically assigns that labor to the outbound campaign.

3. “The Trap”: The “Outbound Abandonment” Spike

The Scenario: You have a blended pool of 50 agents. A sudden spike of inbound calls arrives. The platform automatically moves 40 agents to handle the inbound peak.

The Catastrophe: You are using a Predictive Dialer for the outbound campaign. The dialer, unaware that the agent pool has just shrunk by 80%, continues to blast out calls to customers. Because there are now only 10 agents available, the dialer starts “Abandoning” calls (ringing customers and then hanging up because no agent is free). This is a major regulatory violation (OFCOM/FTC) and leads to massive customer frustration.

The Principal Architect’s Solution: The “Dynamic Dialer Throttling” Bridge

  1. API Integration: Your WFM engine must talk to your Dialer engine.
  2. The Logic: Use a script or a native integration to monitor the Available Agent Count in the blended pool.
  3. The Action: If the WFM engine pulls agents for an inbound peak, the script must automatically send a command to the Dialer: PATCH /api/v2/outbound/campaigns/{id} to reduce the Dialing Mode or Multiplier.
  4. This ensures that your outbound activity “Shrinks” and “Grows” in perfect sync with your inbound capacity, maintaining legal compliance and customer experience.

Advanced: “Interaction Lead Time” for Outbound

In a blended environment, you don’t always need “Predictive” dialing.

Implementation Detail:
For “Low-Urgency” outbound work (like “Happy Birthday” calls or “Service Reminders”), use Interaction Lead Time (deferred work) logic in the WFM planning group.

  1. The engine calculates that these calls can wait up to 4 hours.
  2. It intentionally “Under-staffs” the morning to force the agents to focus on inbound.
  3. It “Over-staffs” the afternoon (a historical lull) to ensure the 4-hour lead time is met.
  4. This “Staffing Smoothing” is the ultimate goal of blending-it turns a jagged, inefficient labor curve into a flat, predictable one.

Validation, Edge Cases & Troubleshooting

Edge Case 1: Skill Mismatch in the Pool

The failure condition: The engine blends an agent into the Outbound Sales campaign, but that agent is only trained for “Support.” They get a sales call and have no idea how to close the deal.
The solution: Use “Skill-Based Planning Groups.” The WFM engine must only blend interactions into a pool if the agents in that pool have the matching Skills and Proficiencies. Do not “Blindly Blend” by department; blend by capability.

Edge Case 2: Outbound Compliance (Time-of-Day)

The failure condition: The WFM engine identifies a “Lull” at 9 PM and tries to blend agents into an outbound campaign.
The root cause: Dialing a customer at 9 PM is illegal in many jurisdictions.
The solution: Ensure your Outbound Campaign Rules are the “Hard Stop.” The WFM engine can suggest a shift for outbound work, but the Dialer must be configured to only allow calls during the “Legal Calling Window.”

Reporting & ROI Analysis

The success of a blended planning group is measured by Occupancy and Resource Utilization.

Metrics to Monitor:

  • Blended Occupancy: (Talk Time + Dialing Time) / Paid Time. (Goal: > 85%).
  • Cross-Channel Service Level: Are both Inbound and Outbound targets being met?
  • Manual Move Count: Number of times a supervisor had to manually re-assign an agent. (Goal: 0).

Target ROI: Expect a 10-15% increase in total agent productivity and a near-total elimination of “Idle Time” during inbound lulls, resulting in a significantly lower cost-per-contact and higher sales revenue.

Official References