Booking Rules

Booking rules determines how a program type operates within your workspace. The settings here can range from what displays to what is required for a booking to proceed.

Book By VIN/Category

When a booking is created, an asset or a category must be selected. This option determines if categories are displayed and selected, or a VIN. A VIN is required for an activated booking, however categories can serve as a representation of a potential asset, rather than the specific asset that the booking will end up with.

For example, you may want your customers to select from types of vehicles like "Small family car", "Large SUV" and assign the specific vehicle at handover. This is an example of booking by category.

Allow alternate drop off location

Alternate drop off location means that a different drop off location to the one specified for pick-up may be used.

Website

Here, you may specify what steps will appear on the signup flows for collecting information on the booking flow. Just check the boxes for what you want to appear.

Other settings

You may optionally specify the minimum age of a booking applicant. This only applies on the customer facing sign-up flows. If the user's age does not meet the minimum criteria, a validation error will occur, and the user will not be able to continue

Booking Requirements

Booking requirements act as a guard to ensure the right information has been obtained before transitioning to the next stage of a booking. Simply choose when you need each requirement to have been met. Once you have chosen one, a drawer will appear on the booking overview screen to show if it has been met yet, and if it's urgently required before continuing.

The rules behave as follows:

Examples

Lets look at a booking with the following booking rules applied:

License has been set as required for confirmation to happen

This means that a valid licence is required on all drivers to confirm the booking. If a valid licence is no longer available after confirmation, it will also be required for activation. This might happen if an additional driver is added or a license has expired.

Example 1

Below is a quote with one driver without a valid licence defined. It's greyed out because it's not required for the next transition, but it will be required for a future transition (requested -> confirmed)

Example 2

The booking is requested. It shows as an error, because it is required for the next transition to confirmed. "Not provided" is just one example of an error, a licence can fail for other reasons, such as being expired.

Example 3

In this example, the booking is in quote status, and a licence is provided and valid. It would look like this no matter what status the booking is in.

In this scenario, we have the primary driver and 2 additional drivers. One has a person specified, and the other has no person specified. The primary driver has no licence. In this scenario, we require valid licences for all drivers, including the one without a person specified.

Automation

Automation enables configuring when and how an ID check is performed.

Note: this customisation is only available if FrankieOne is integrated in your workspace. Go to Settings > Integrations to set it up.

• Select "Automatic" to automatically initiate an ID check once a booking is in "requested" state. This will occur when the signup funnel is completed and payment method submit.

• Select "Manual" if you prefer to perform an ID check manually. This can be done any time by navigating to the Trupass tab for the selected person, clicking the licence or passport you wish to perform the ID check against and clicking "New Check".