WFM stakeholder management

What they need from WFM

Volume forecast (4–13 weeks ahead); published schedule (4+ weeks ahead); intraday queue position and recommended actions; post-day and monthly SL attribution (was the SL failure a WFM problem or an adherence/adherence problem?); headcount risk alerts (when the planned headcount will not meet the requirement).

What WFM needs from them

Decisions on headcount actions (approval for recruitment, overtime, or agency engagement); confirmation of operational events (campaigns, training, changes to processes) that WFM must plan around; feedback on schedule quality; adherence management (WFM can identify adherence problems but cannot resolve them without Operations' authority).

Engagement cadence

Daily: intraday queue position update. Weekly: short-range forecast and schedule review. Monthly: performance pack and headcount review. Quarterly: medium-range plan review.

Relationship failure mode

WFM produces outputs that Operations does not act on because the outputs are not communicated clearly enough, come too late to be actionable, or have lost credibility through repeated inaccuracy. The WFM function becomes a reporting function rather than a planning function.

What they need from WFM

The headcount plan (FTE count by month, translated into salary cost); the variance between planned and actual headcount cost (with explanation); the staffing cost forecast for the budget cycle; the cost impact of WFM decisions (e.g. overtime cost, agency cost, training capacity impact).

What WFM needs from them

Budget approval for headcount above the current establishment; the timing of budget cycle inputs (WFM must know when to submit headcount plans to Finance); the cost-per-head assumptions that Finance uses to convert FTE into cost; the cost treatment of temporary contracts and agency workers.

Engagement cadence

Monthly: headcount actuals vs. budget. Quarterly: headcount forecast for next 2 quarters. Annual: headcount input to the budget cycle (typically September–November for a January budget).

Relationship failure mode

WFM submits headcount requirements that do not connect to the Finance budget process — too late, in FTE counts rather than cost, or without explanation of the business impact of not funding the request. Finance treats headcount as a cost line to cut rather than a business requirement.

What they need from WFM

The recruitment requirement (how many agents are needed, by skill, by when); the ramp time assumption (how long before a new starter is at full productive capacity); the attrition forecast (WFM's view of likely leavers in the next 3–6 months, to allow recruitment to pipeline ahead of the gap); the scheduling constraints that HR must respect in employment contracts.

What WFM needs from them

Confirmed start dates and training completion dates for new starters; notification of confirmed leavers (notice period start); confirmation of contractual working patterns that constrain scheduling; legal review of any proposed scheduling changes (shift changes, new shift patterns) before WFM communicates them to agents.

Engagement cadence

Monthly: headcount tracker update (new starters, confirmed leavers, pipeline). Quarterly: attrition forecast and recruitment requirement for next 2 quarters. Ad hoc: legal review of new scheduling arrangements.

Relationship failure mode

WFM submits recruitment requirements without adequate lead time (minimum 8–12 weeks for recruitment + training). HR cannot fill a gap that is already present — they can only pipeline ahead of a forecast gap. A WFM function that requests recruitment when the shortfall has already arrived cannot be rescued by HR.

What they need from WFM

Advanced notice of changes to WFM system configuration (routing changes, skill changes, new queue configurations) that require IT involvement; lead time for system upgrades or migrations that affect WFM data; the data specification for ACD report feeds that WFM depends on.

What WFM needs from them

Notification of planned maintenance windows and system changes that will affect ACD data quality (so WFM can adjust its forecasting methodology for that period); notification of telephony configuration changes that affect volume routing (if a new IVR option deflects 10% of contacts, WFM must know before, not after, the change goes live); access to ACD raw data at interval level for WFM modelling.

Engagement cadence

Monthly: review of planned system changes in the next 4 weeks. Quarterly: system roadmap review. Ad hoc: notification of any routing or configuration change affecting volume distribution.

Relationship failure mode

IT makes routing, IVR, or configuration changes without notifying WFM. The forecast becomes wrong overnight without WFM knowing why. This is one of the most common sources of unexplained forecast error — not a WFM methodology failure, but a failure of the IT-to-WFM communication channel.