WFM-friendly routing methods are those that do not change skill requirements (e.g., adding or stripping of skills) after the initial requirements were set.
@Eric Hagaman, we should look at improving documentation.
The workforce management supported configuration page you mentioned is accurate in that only those noted as being supported are supported and any not listed or said not to be supported are not supported. I.e., "Forecasting and scheduling does not support queues configured for bullseye routing." means bullseye routing, regardless of how it is configured, is not supported by WFM.
Forecasts and schedules are plans and those plans are built on the initial requirements of interactions. Routing methods that employ tricks to reduce the initial requirements are violating the plans made in the forecast and staffing stages. For standard routing, the all skills matching is greatly preferred. You could have a different evaluation method, but if those things happen frequently (disregarding some or all skills after initial requirement), then forecasting and staffing will diverge even more from what actually occurs / is needed.
Related recent post:
https://community.genesys.com/discussion/conditional-group-routing-impacting-fte-differentials#bma9949391-5c15-463d-9027-018f1f79768b
------------------------------
Jay Langsford
VP, R&D
------------------------------