How to Configure Pipeline Status Filters for Custom Recruiter Pools
Overview
Pipeline status filtering lets you limit a Custom Recruiter Pool so it only assigns recruiters when a prospect is at a specific stage in the recruitment pipeline — for example, only routing prospects to a pool once they reach Interested or Applied. This closes a gap where a pool's Attribute or Name Rules might match a prospect correctly, but at a stage where that routing doesn't actually make sense yet.
At a Glance
- Adds an "Only match when prospect status is" setting to each Custom Recruiter Pool
- When set, the pool is skipped entirely for any prospect not currently at that status — even if their Attributes or Name Rules match
- Pools left at "None (any status)" behave exactly as before — no status restriction
- Fully supported in the Test Pools preview, so you can validate status-based routing before it runs live
How It Works
Without a status filter, a Custom Pool evaluates a prospect purely on its configured Attributes and/or Name Rules, regardless of what pipeline stage they're currently at. With "Only match when prospect status is" set, the pool adds one more condition: the prospect's current status must match before the pool will assign a recruiter at all. If the status doesn't match, the pool is skipped — the prospect moves on to the next eligible pool, or falls through to the Default Recruitment Pool if nothing else matches.
Please note: This works alongside — not instead of — Attribute and Name Rule matching. A pool with both a status restriction and Attributes configured must satisfy all of them before it assigns a recruiter.
Configuring a Required Status on a Pool
- Navigate to Recruitment Center > Manage Recruiter Pools.
- Open the Custom Pool you want to restrict.
- Locate the "Only match when prospect status is" field.
- Select the pipeline status this pool should be limited to (for example, Interested or Applied), or leave it set to None (any status) to keep the pool running at every stage.
- Save the pool.
Validating Status-Based Routing with Test Pools
Before relying on a status restriction, confirm it behaves the way you expect using the Test Pools preview:
- From the Manage Recruiter Pools page, click Test Pools.
- For an existing student, the preview automatically reads their current status. For a hypothetical prospect, use the Prospect status selector to simulate any status you want to test against.
- Run the preview. Pools that don't match the prospect's status don't appear as eligible matches — instead, they're listed in a "Skipped (required prospect status)" section below the results, so you can see at a glance which pools were excluded and why.
No assignment or student data is created or changed by running a test.
Things to Know
- Auto-assignment strictly respects Pipeline Stage Settings for both status and attribute matching.
- A pool with no status restriction set is unaffected — it continues to evaluate every prospect regardless of stage.