OnsitePilot answer
What is route-aware booking?
Route-aware booking means a slot is offered only if it works with travel time, service duration, buffer rules, and nearby calendar commitments. It treats open time as only one input, not the whole scheduling decision.
Key facts
- Open calendar time is not always reachable time.
- Route-aware logic should run before confirmation, not after the operator reviews the day.
- The beta build uses TomTom for route and travel-time checks.
- A map alone is not route-aware booking unless route data controls slot acceptance.
Why normal availability is not enough
A normal calendar can show a blank block between appointments. For a mobile service operator, that block may still be impossible because the previous job is too far away, traffic is heavy, cleanup time is missing, or the next appointment would be affected.
Route-aware booking adds the physical constraints of the workday to the booking decision.
What the system should check
A useful route-aware workflow checks the service location, existing appointments, travel time, expected service duration, setup or cleanup buffer, and whether the appointment should be rejected or sent to review.
The goal is not to show more availability. The goal is to show fewer but better slots that the operator can actually deliver.
Related questions
- Is route-aware booking only for same-day appointments?
- No. Same-day work makes the issue obvious, but route logic also matters for future bookings, reschedules, and any day with multiple service locations.
- Does map integration alone solve this?
- No. Map data is an input. The booking workflow must use that data to accept, reject, or review slots before confirmation.