Capabilities & Priority
Capabilities and label priorities give you fine-grained control over how the dispatch algorithm matches and prioritizes tickets.
Capabilities
Capabilities are tags that describe what a shuttle driver can do. They enable the dispatch algorithm to match tickets to qualified drivers and specialized equipment requirements.
Defining Capabilities
An Admin user defines capabilities for the organization in Admin Configuration. Each capability has:
- Name — A short identifier (e.g. "hazmat", "oversize", "chassis-move"). Names are case-insensitive.
- Description — Optional explanation for other admins.
Assigning to Shuttles
After defining capabilities, assign them to shuttle profiles in Shuttle Management. A shuttle can have multiple capabilities.
Requiring on Tickets
When creating a work ticket, you can specify requiredCapabilities in the ticket data. The dispatch algorithm will only assign the ticket to shuttles whose capabilities are a superset of the requirements.
| Ticket Requires | Shuttle Has | Eligible? |
|---|---|---|
["hazmat"] | ["hazmat", "oversize"] | Yes |
["hazmat", "oversize"] | ["hazmat"] | No — missing "oversize" |
[] (none) | ["hazmat"] | Yes — no requirements |
["chassis-move"] | [] | No — missing capability |
You don't need capabilities to use auto-dispatch. If no tickets have required capabilities, all on-duty shuttles are eligible for all tickets. Add capabilities later as your operations grow in complexity.
Label Priority
Work ticket labels can have an optional priority value that the dispatch algorithm uses as one of its five weighted factors. Lower numbers = higher priority.
Priority Scale
| Priority | Meaning |
|---|---|
| Critical | Dispatched first |
| High | |
| Normal | |
| Low | Dispatched last among prioritized tickets |
| None | Label has no effect on dispatch ordering |
Setting Priority
Set priority values on labels in Admin Configuration. Only labels with a priority value influence the dispatch algorithm. Labels without priority continue to work as display-only tags.
How Priority Affects Dispatch
When a ticket has multiple labels, the lowest priority value (most urgent) among them is used for scoring. For example, if a ticket has labels with priorities "High" and "Normal", the score uses "High" priority.
Label priority is one of five factors the dispatch algorithm weighs against each other — sequence, due date, label priority, proximity, and workload — to decide which (ticket, shuttle) pair gets dispatched next. The relative influence of label priority versus the other factors is tuned in Admin Settings. See Dispatch Algorithm for how all five factors combine.