2.6 Trip Allocation Config

Discover how to deliver trip requests to drivers in various ways.

Start by clicking on the settings option, on the left side of the menu at the bottom, and find the option labeled "trip".

Under "trip," there's a submenu called "trip configured."

Here, find different categories that allow the admin to deliver trip requests in various ways. To deliver trip requests to drivers in other ways, click "trip allocation config."

This config displays three methods: batch-wise, one-to-one, and manual.

Batch-wise means that when a customer generates a trip request, all nearby drivers receive the trip request simultaneously. Any driver can accept the trip request and pick up the customer.

In the one-to-one config, the driver closest to the pickup location receives the request. Then another driver, and so on. Each driver receives the trip request one by one within the radius of the nearby discharge.

The manual method doesn't deliver the trip request to the driver. Instead, the admin assigns the trip manually to the drivers. The admin decides which trip request to assign to which drivers.

Each config has a few configurations. For example, the "maximum request router to driver" allows the admin to define how many drivers should receive one trip request. After delivering to all the drivers, the system will show "no driver available."

Another option is the search radius for finding a driver. When a customer generates a trip request, the system defines the radius of the defined kilometers. Those drivers within the ten-kilometer radius receive the trip request from the system.

The "request timeout" option defines how much time a driver has to accept a trip request after it's generated.

The last option is the batch size. Batch-wise, decide how many batches to send the trip request in. For example, if ten drivers get the trip request, decide in how many batches to send it.

In one-to-one, the configurations remain the same, but the driver receives the trip requests one by one.

Under manual, there are no configurations because the admin decides which driver takes the ride.

In this way, the trip allocation feature works. The admin decides which allocation type to use to deliver the trip request to the driver.