Passenger-related settings

Permissions: update_product

In the Passenger-related settings section of the tenant settings of a product, you can configure the following settings.

Waiting for passenger acceptance until the system cancels

This time specifies how long a passenger has to confirm an offered ride before the system cancels the offer.

The countdown starts when matching has found a solution and the offer is presented to the passenger. From that moment, the passenger must accept within the configured time; if they do not, the offer is no longer valid and the system cancels it, freeing the matched capacity for other requests. During operator booking, the remaining time is shown as a countdown that reflects this setting.

This is the passenger-side counterpart to waiting for driver acceptance until the system cancels. It can range from 5 seconds to 5 minutes and is selectable from a dropdown, divided into 5-second intervals.

Threshold for slightly delayed tasks

This threshold defines the point at which a task’s delay state is considered slightly delayed.

A task is classified as slightly delayed if its planned execution time occurs later than the negotiation time max by more than the slightly delayed threshold, but does not exceed the heavily delayed threshold.

This represents a minor schedule deviation that is noticeable but not critical.

Threshold for heavily delayed tasks

This threshold defines the point at which a task’s delay state is considered heavily delayed. It is the most severe of the three delay states—on time, slightly delayed, and heavily delayed—which are derived from a task’s delay relative to its negotiation time max.

A task’s delay is measured as how much later its execution time is than the negotiation time max. That delay is then classified:

• On time. The delay does not exceed the slightly delayed threshold.
• Slightly delayed. The delay exceeds the slightly delayed threshold but not the heavily delayed threshold.
• Heavily delayed. The delay exceeds the heavily delayed threshold.

Because the heavily delayed threshold takes precedence, a task is only ever slightly delayed while its delay sits between the two thresholds; once it passes the heavily delayed threshold it is reclassified as heavily delayed.

This represents a significant delay that may require urgent attention. Heavily delayed tasks are often highlighted in client applications to draw attention.

This setting is the passenger-facing threshold; a matching driver-facing threshold is configured separately under driver-related settings, so the same task can be evaluated independently from each perspective.