|
|
|
|
|
by dvetrano
4080 days ago
|
|
Hey, Ryan. Thanks for the kind words! David, here, CTO & Co-founder at Onfleet. We're quite busy on a number of improvements touching on some of your points. We released dynamic filtering based on delay time recently which is our first foray into exception-driven dispatching for large volume customers. There's a lot more to come here! While we think of tasks as the smallest atomic unit of work for a driver -- and so we like to imagine that at most one can be active for a given driver at once -- we're rolling out dependencies soon and will be exposing configurable notifications that support these cases. Additionally, the concept you mention around exposing ETAs for future but inactive tasks is in the pipeline. The biggest challenges here are around privacy for the driver and other customers and we'll be sure to put a lot of consideration into balancing visibility and privacy. Often, in the on-demand space, it's common to see companies which expose the driver's location to a customer as they make deliveries to other customers. We do want to allow this feature but it's essential for us that alternatives which better protect customer information are available. |
|