When double round robin is used in Chili Piper, the second participant pool is selected as a flat group with no conditional logic applied. Teams running paired AE/SE selling motions need the second slot to resolve dynamically based on deal attributes evaluated after the first slot (AE) is already matched. For example: route to the appropriate AE queue first, then evaluate device count and third-party product flags to determine which SE pool to draw from, or whether to include an SE at all.

The requested behavior is a second assignment node that evaluates its own set of conditions independently after the first assignment resolves, selecting the appropriate pool (or no one) based on those conditions. Without this, admins have to duplicate routing rules for every AE segment times every SE scenario, which scales badly and creates maintenance overhead.

This is specifically a gap from the AE's perspective as well: even when SE inclusion is objectively appropriate by deal size, the AE may decide not to bring one on the first call. So the feature also needs to support making the second-slot assignment optional or overridable by the assigned AE.