A critical ticket is a delivery ticket that has been sitting unassigned for longer than you are willing to let it sit. Zippykind marks it with a red flashing circle next to the ticket on the dashboard, so a ticket nobody picked up does not quietly age on a busy board.
Turning it on
Go to Settings → General Settings in the dispatch software and find the Ticket Critical Options panel.
- Enabled — switches the flag on. It is off until you turn it on.
- Minutes — how long a ticket may stay unassigned before it is treated as critical. The default is 30 minutes.
Press Save Settings at the bottom of the tab to store both values.
What it does and does not do
Marking a ticket critical is a visual alert on the dispatch dashboard. It does not assign the ticket, it does not notify a driver, and it does not change the ticket's status — the ticket is still unassigned. It exists so a human looking at the board can see which unassigned tickets have waited too long.
If you want unassigned tickets to be handed to drivers without a human, that is auto-assignment, and the two work well together: auto-assignment tries to place the ticket, and the critical flag tells you when it has not succeeded. Auto-assignment can also email a named address when a ticket fails to assign at all.
Choosing a number of minutes
Set it to a little less than the time by which you would want to have intervened. For on-demand delivery, 10 to 15 minutes is a common choice. For scheduled route work where tickets are created hours ahead of time, a short window will flag every ticket you create and the flag stops meaning anything — pick a longer one, or leave the feature off.