Open Settings → Dispatch → Operations → Assignment rules to review the policies stored for assignment exceptions.
Read the assignment controls
Five rules offer Allow, Warn, and Block choices:
| Rule | Situation covered |
|---|---|
| Assign without vehicle | The driver has no assigned vehicle. |
| Fallback vehicle type | The driver’s vehicle type is on the booked type’s fallback list. |
| Outside the fallback list | The driver’s vehicle type is neither the booked type nor one of its fallbacks, whether higher or lower in class. |
| Override service type | The driver’s service type differs from the requested one. |
| Override capacity limit | The passenger count exceeds the vehicle’s capacity. |
Review the selected choice separately for each rule. Warn is a distinct saved value; do not treat it as an enabled or disabled toggle.
Fallback vehicle type and Outside the fallback list replace the former Different vehicle type switch. Both start at Allow for every company, so a different vehicle type is accepted until you choose Warn or Block. Each vehicle type’s fallback list is kept in Fleet; select Set fallback lists in Fleet and see Prepare fleet resources for operations.
When a dispatcher assigns a driver from Dispatch, a Warn rule opens Confirm Driver Assignment and a Block rule opens Driver Not Assigned. Both dialogs list the reason for each rule that applied. Confirm assigns the driver anyway; a blocked driver is not assigned.
Change and verify a policy
- Record the current choice and the assignment scenario you want to support.
- Select the new choice or change the toggle. The row saves immediately; wait for the update to complete before changing another row.
- Reload the page and confirm the stored value. If saving fails, the control returns to its previous value.
- Test a representative assignment and follow any warning or rejection displayed by Dispatch. Confirm the observed behavior with the dispatcher who will use the policy.
Each change saves the selected setting, so unrelated assignment policies retain their values. Use a test reservation for the first check. See assignments and trip statuses for the dispatch workflow.
Choose which bookings need review
In Dispatch → New bookings, choose the channels that wait for review: Backoffice, Driver App, Customer Web, Customer App, and Public API. Each switch saves separately. Confirm the selected channel and the result on a test booking before relying on the review queue.
Webhooks and retention
The webhook section accepts an https delivery address when API access is available. Save it, copy the Signing secret while it is displayed, and store it securely; it is shown only once. Rotate secret replaces it, so update the receiving integration. Send test event posts a test to that address. Review Recent deliveries, attempts, HTTP status and errors when diagnosing a connection. Never put the secret in screenshots or support messages.
Data retention is optional and initially off. A saved period from 6 to 120 months controls anonymisation of passenger and booker details on older finished bookings. Shortening the period asks for confirmation and cannot be undone. Agree the period with the responsible owner before saving; changing it back does not restore anonymised details.