How time-window dispatch works
This example uses one board and three Flows, all matching Status Ready to be Assigned.- A ticket reaches Ready to be Assigned at 6 PM on a Tuesday.
- Only the Evening Flow’s conditions match, so only its skill runs.
- The skill assigns someone from the evening crew.
Variations
Before you start
- You’ve written down every window, with time zone, and who covers it.
- The windows don’t overlap, so only one Flow matches at a time.
- The skills are shared skills.
Set up time-window dispatch
1
Write one skill per pool
Each skill names its pool and how to pick. Include the out-of-office list if you keep absences in the skill.
2
Create one Flow per window
Add the board and status conditions, then the window’s day and time conditions. Add Agent Builder → Run a Skill with the update ticket and add note tools checked.
3
Check the edges
Test a ticket just before and just after each boundary, and at the weekend.
Rules for time-window dispatch
- Built-in agent tools don’t read work schedules or time off. A skill can read Planner entries and, through an enabled Auto-assign profile, the available-for-dispatch toggle. Anything else has to be written into the skill.
- Auto-assign profiles can use work schedules to decide who is available. If schedule-based availability is your main need, compare a profile first.
- No clock trigger. A Flow runs on ticket changes. A ticket that missed its window waits until something changes it, or until a person picks it up.
- One run per ticket per Flow. Each window’s Flow runs once on a ticket.
- Someone owns the calendar. Shift and absence lists in skills go stale unless one person updates them.