How a catch works
This example has a dispatcher Flow on status Ready to be Assigned and a catch on status Needs Dispatch.- The dispatcher skill finds no one, and moves the ticket to Needs Dispatch.
- The catch takes over.
Variations
Before you start
- You know which status your dispatcher sets when it gives up, or you’ll add one.
- You’ve decided who catches: a profile, a different skill, or a person.
Set up a catch
1
Give the dispatcher a way out
Tell the dispatcher skill which status to set when no one qualifies, and check the update ticket tool.
2
Point the catch at that status
Create an Auto-assign profile, a second Flow with a different skill, or a dispatcher View on that status.
3
Add a View anyway
Save a View of unowned tickets in your “ready” statuses. It shows anything that slipped past both.
Rules for catches
- A Flow never runs twice on a ticket. That holds even after a failure or a requeue, so the catch must be a different Flow, a profile, or a person.
- Auto-assign takes only unowned tickets. To hand a ticket to a profile, remove the owner and set its dispatch status.
- Reclaimers overwrite. A skill that replaces an owner does it whether or not the owner is mid-task. Write clear rules for “abandoned”.
- “Succeeded” isn’t “assigned”. Run history shows the skill ran. Use a View to see what’s still unowned.