Creating Queues
Last updated: March 24, 2026
Queues help you route scheduling requests to the right schedulers without assigning each request manually.
If you are setting this up for the first time, think of a queue as:
a group of coordinators
a set of assignment rules
one place to manage who gets new work
Create a queue
Go to Settings > Scheduling > Queues.
Click Create queue.
Enter a clear queue name (for example, EMEA Recruiting or Sales Hiring).
Add the scheduler who should receive work from this queue.
Choose your communication channel (email or Slack).
Choose an assignment strategy.
Choose an assignment strategy
Each queue uses one strategy:
1) Intelligent assignment
Best when you want balanced distribution over time.
Balances current active workload
Also accounts for recent assignment activity
Helpful when onboarding new scheduler so they are not flooded immediately
2) Least workload assignment
Best when you want the most direct workload balancing.
Assigns to the scheduler with the lowest workload relative to capacity
3) Leave unassigned
Best when your team prefers to triage manually.
Requests are created with no owner
Queue members can claim or assign requests from the queue view
Add optional assignment settings
These settings are in addition to the strategy:
Keep with previous scheduler (optional)
If a previous scheduler exists and is still an active member of the queue, the request stays with them.Respect working hours (optional)
Prioritizes scheduler currently in working hours. If no one is currently in working hours, assignment falls back to all active queue schedulers.
How assignment works
When no calendar owner is provided:
If the strategy is Leave unassigned, the request is created without an owner.
If the strategy is Intelligent assignment or Least workload assignment, candidate.fyi:
Applies Keep with previous scheduler (if enabled and applicable)
Applies Respect working hours (if enabled)
Applies the selected strategy to the eligible schedulers
Workload is measured by active interview scheduling requests on that queue (excluding canceled and archived requests). Capacity is a routing target, not a hard assignment limit.