Hey everyone!

We have released Version 4.100.3 on Friday, December 19, 2025.

This release introduces new server-side configuration controls for geofence-based driver warnings and made multiple improvements impacting route suggestions, vehicle seating validation, passenger-level exclusions, and historical suggestion applicability.

Key Highlights

1. Configurable Geofence Warnings for Driver Actions

Feature Summary:

Administrators can now configure geofence-based warnings for driver actions using server-side controls. This ensures consistent and predictable behavior when drivers mark arrival events, aligned with tenant-specific geofencing requirements.

What’s New?

• A new server-side configuration allows tenants to:
  • Enable or disable geofence warnings for driver actions.
  • Define the geofence radius used for validation.
• When Geofence Alerts are enabled the system uses the radius defined in the Geofence Alert configuration for:
  • arriveAtPickup
  • arriveAtDestination
• When Geofence Alerts are disabled:
  • The system retrieves the radius from the database.
  • A minimum radius of 100 meters is always enforced to prevent overly strict validations.
  • This ensures consistent behavior across driver arrival events and avoids mismatched radius calculations.

2. Route Suggestion Validation Fixes (Vehicle Seating & Passenger Exclusions)

Feature Summary:

Multiple improvements impacting the validity of route suggestions have been resolved, improving dispatcher confidence when applying both new and historical suggestions.

What’s Improved?

Vehicle Seating Validation for Suggested Routes

• Made improvements where vehicle seating validation failed for valid suggested routes.
• Scenarios where the vehicle contains only flexible seats, and no seating configuration was changed, were incorrectly marked as invalid.
• The system now correctly allows these suggestions, recognizing that flexible seating can be adjusted within the route.

Passenger-Level Driver & Vehicle Exclusions

• Made improvements where passenger-level exclusions were ignored during route suggestion generation.
• Suggestions will no longer assign trips to:
  • Drivers excluded at the passenger level, or
  • Vehicles excluded at the passenger level.
  • This ensures exclusion rules are consistently respected during suggestion generation and review.

3. Historical Suggestions No Longer Invalidated by Service Type Mismatch

Feature Summary:

Historical route suggestions are now evaluated more accurately when booking details are reviewed, preventing valid suggestions from being incorrectly blocked.

What’s Improved?

Improved historical suggestions were marked invalid with the message:

“Booking details changed: Service Types”

• When service types are compatible or unchanged:
• Historical suggestions remain valid.
• Dispatchers can successfully apply them without manual rework.
• This restores expected behavior and improves usability of historical suggestions during dispatch operations.

Value Delivered: 

This release improves operational reliability and dispatcher efficiency by introducing configurable geofence controls, correcting route suggestion validation logic, enforcing passenger-level exclusions, and restoring trust in historical suggestions. Together, these updates reduce false validation errors, prevent incorrect assignments, and ensure routing decisions behave consistently with real-world configurations.

Thank you for choosing Tobi as your preferred partner.

Please contact help@tobicloud.com if you have any questions.