Treat Needs Attention as a triage queue, not a status to clear mechanically.
- Prioritize by time sensitivity and operational impact.
- Open the reservation and identify the condition behind the attention indicator.
- Confirm the relevant assignment, timing, route, and communication history.
- Resolve the underlying issue using the appropriate workflow.
- Recheck the queue after correcting the reservation or resolving the warning.
Understand what is counted
The organization chooses which conditions contribute to Needs Attention in Settings → Dispatch Board → Needs Attention. Available conditions are Overdue pickup, Awaiting customer card, Missing booking information, Dispatch note, Booked for another person, and Unresolved warning.
Some conditions ask for a review rather than indicate an error. A booking made for another person may be correct; confirm who is traveling and whose contact information should be used. A dispatch note can keep a trip in the queue while that condition is enabled. Passenger and billing notes are separate from the dispatch-note condition.
Administrators must leave at least one condition selected. Changing the selected conditions saves that selection without changing the assignment rules in Operations. Wait for Needs Attention Updated before leaving the settings page; a failed save restores the previous selection. Controls marked TBD are not available settings.
Resolve a booking warning
Select the warning badge beside the reservation’s confirmation number to open Warnings. Read each message and its author, time and source, then address the operational issue. Select an individual warning to resolve it, or choose Resolve all only after reviewing every warning shown.
Resolved rows display Resolved, with the resolver and time when available. Resolving a warning records that action; it does not change the booking’s trip status or repair missing reservation information. If the warning list cannot load, choose Try Again.
If an item remains after the underlying issue is resolved, refresh the view and capture the topic, reservation reference, and non-sensitive error text for the approved escalation process. Do not include passwords, tokens, or payment card data.