Last updated

Better Route Deep Integration

Disclaimer

See for other integration options the decision helper.

Basic Data Flow

The Better Route API requires you to set up a basic connector set up upfront — allowing job information to reach Bettermile, so it can be used in the route optimizations over the day.

Better Route - deep integration - minimal data flow

The Basics - Setting up a tour and generating sequences

Once the job data for a tour has reached Bettermile in the connector, you can go ahead and create a tour.

With this being done, you can then trigger a sequence generation. The sequence generation is recommended for any mode to be requested in at least 10-minute intervals — if you have updates in the meantime (e.g. a job status update), more frequent requests are beneficial.

The modes allow you to define whether the route should follow a custom order of waypoints or optimize freely based on current location, destination, and the defined start time. Alternatively, it can keep a previously defined order mostly intact. The most used optimization mode is FIXED_OPTIMIZATION as it instructs that ETAs of waypoints be recalculated while the order of the waypoints remains mostly unchanged (waypoints may only move in special cases, like when a timeframe changes).

Talk to us if you want to learn more on the basics. Happy to have a chat!

Further supported use cases

Read up on further supported use cases