Service violation blocks
The Service violation blocks page displays the service violation blocking settings and lists all passengers who committed a service violation as well as the associated consequences. The types of service violations that are tracked are configured on the product and can include no-shows (passenger did not show up at the pick-up location) and late cancellations (passenger cancelled later than an allowed threshold of time before the pickup).
This feature had formerly been named “No-show records”. It has been renamed and repurposed to serve more cases than no-shows and to be extendable for more types of violations.
View service violation blocks
Permissions:
read_service_violations
From the product overview in Control Center, follow the link for Service violation blocks in the side navigation panel. In this view, service violations are listed in a table containing the following information.
| Column | Description |
|---|---|
| ID | Service violation block identifier |
| User | User name |
| Lifted at | Unblock timestamp |
| Lifted by | Person who removed the block |
| Blocked until | Block end timestamp |
| Created at | timestamp of block |
Open the detailed view of a service violation block
Permissions:
read_service_violations
To open the detailed view of a service violation block, select ⚙️ > Show in the dropdown menu.
Unblock a passenger
Permissions:
create_service_violation_acknowledgments
A service violation is recorded each time a passenger either does not appear at the pick-up location or cancels the ride too late, depending on product settings. When service violation blocking is turned on and a user collects more than the allowed number of service violations within the configured period, the user is automatically blocked from booking new rides until the block expires. Only service violations that have not been reset still count toward this limit.
To act on a block, select ⚙️ > Show to open it, then choose one of the following actions:
- Lift block. Lifts the block immediately, so the user can book rides again. The user’s earlier service violations stay on record and still count toward the block limit, so a further service violation can trigger a new block.
- Lift block & waive all service violations. Lifts the block and clears all of the user’s service violations for the product at the same time. This resets the count to zero, so the user starts fresh.
Use Lift block when you want to end the block but keep the user’s service violation history. Use Lift block & waive all service violations when you want to give the user a clean slate.