Notifications sent on booking events
MobilityManager sends in-app notifications at each step of the booking lifecycle so drivers and approvers never have to poll for updates. This article explains which event triggers which notification and who receives it.
Where notifications appear
Notifications are delivered inside the application to the relevant user's notification list, where each one carries a title, a message, and a link to the related booking or request. Every booking-creation path — self-service, auto-assign, and manager-assign — routes through the same notification step, so the behavior is identical no matter how a booking was made. This single, shared notification step is why approvals no longer stall silently: whenever a booking needs review, the right people are told automatically.
Notifications by event
| Event | Who is notified | Message |
|---|---|---|
| Booking created and immediately Confirmed | The driver | Booking confirmed, with vehicle and time window. |
| Booking created but needs approval (PendingApproval) | Every user with the bookings:approve permission in the organization |
"Booking Approval Required" — names the driver, vehicle, and window, asking them to review. |
| Approver approves a pending booking | The driver | Booking approved, with vehicle and time window. |
| Approver rejects a pending booking | The driver | Booking rejected, including the reason. |
| Manager assigns a vehicle to a driver's request | The driver | Request fulfilled — the booking is confirmed with the assigned vehicle. |
| Manager rejects a driver's request | The driver | Request rejected, including the reason, linking back to the requests list. |
| Fleet manager cancels a booking | The driver | Booking cancelled, including the reason. |
How approvers are chosen
When a booking needs approval, the system looks at every user assigned to the organization and keeps only those who actually hold the bookings:approve permission. Each of them receives the "Booking Approval Required" notification, so approval never depends on a single named person being online.
Note: Manager-assigned bookings do not generate an "approval required" notification, because the fleet manager who assigned the vehicle is already the approver. The driver receives the fulfilment notification directly.
Tip: If drivers report that approvals "go quiet", check that at least one active user in the organization has the bookings:approve permission. With no eligible approver, no approval notification can be delivered.
Reasons travel with the notification
For every event that ends a booking negatively — a rejected request, a rejected pending booking, or a fleet-manager cancellation — the reason entered by the approver or manager is included in the driver's notification. This keeps the driver informed without a separate email or phone call, and gives them the context they need to resubmit or rebook. Confirmation and approval notifications instead carry the vehicle name and the booking's start and end times so the driver can see exactly what was reserved.
Related
- Approve or reject bookings awaiting approval
- Approve or reject a booking request
- Track and cancel your booking requests
- Require approval for auto-assigned bookings
