Set the Geosearch and Georoute rules on an AroFlo booking form
Geosearch offers a customer only the times near visits that are already booked. Dynamic travel times add the real drive between visits. This page, headed "Geosearch for AroFlo Bookings", sets how a single form uses them.
Before you start
- Geosearch is turned on for the account first, on the Geosearch page. Until then this page says "Geosearch not turned on" with a Turn on Geosearch link.
- Without a subscription the page says "Subscription required". On a subscription without the add-on, Turn on Geosearch? is greyed out and reads "Geosearch functions available with the Geosearch plan".
- Allow dynamic travel times? needs the Georoute plan, and reads "Dynamic travel times available with the Georoute plan" without it. The Geosearch rules and Georoute rules sections appear only once their plan is there.
Step by step
- Open your form from Forms. On the Settings tab, open Geosearch under Bookings setup.
- Switch on Turn on Geosearch. Usage charges apply.
- Under Home location, search for an address. This is the point empty days and the first drive of the day are measured from.
- Set the Maximum allowable searchable distance radius and the Maximum allowable searchable time in minutes.
- Choose what happens on Empty visit days.
- Optionally switch on Allow dynamic travel times and set the Georoute rules.
- Click Save.
Beside Save, the page says why it is off: "this form is archived.", "enter a search distance.", "enter a searchable time.", "enter a maximum travel time.", "the minimum travel time cannot be more than the maximum.", or "choose a home location, which empty days and travel times are measured from. Or let customers book on days with no visits, and turn dynamic travel times off."
Geosearch form rules
Home location shows the saved address with a Clear button, and Update home location replaces it. The home location does not apply to time groups, unless dynamic travel times is on. With it on, each staff member's first booking of the day includes the drive from here, and cannot start before their start time plus that drive.
Maximum allowable searchable distance radius is in kilometres, or miles if the form is set to miles. It starts at 50. A time is only offered when an existing visit is within that distance. Distances are measured as the crow flies, so allow extra for the real route.
Maximum allowable searchable time in minutes starts at 120 and is in multiples of the form's time interval. The field rounds up to the next multiple when you leave it. A time is offered when an existing visit is within that many minutes before or after it. Once both are filled in, a sentence under them says exactly what the form will offer.
Empty visit days
When a customer looks at a future date with no visits, choose one:
- Allow customers to book any time when there is an empty day.
- Block out all available times that are not near the home location. Visits will be manually created in AroFlo to create availability.
Treat free stretches like empty days applies the same choice to a time with no visit within the searchable time before or after it, instead of blocking it. A gap of exactly the searchable time counts as enough.
Non-work events
Empty visit days can ignore events that are not work, such as a lunch break or toolbox meeting. Type the title of an AroFlo event in Event title and click Add title. Titles are not case sensitive, are held to 60 characters, and a form takes up to 30. Enter adds a title without saving the form. With none added, every event counts as work.
Dynamic travel times and Georoute rules
Turning on Allow dynamic travel times calculates the travel time between sites when the booking is scheduled. A route request is made for every visit the form checks, even when the customer does not book, so charges rise. See the Usage tab.
- Add travel at both ends of a booking. Counts the drive after the visit as well as the drive before it. Each end uses the route from or to the nearby task on that side, or the home location when there is none. A time is offered only when both drives fit inside the staff member's hours. Needs a home location.
- Regions lets you limit travel times to the regions ticked. Addresses elsewhere are booked without them. Leave every region unticked to calculate them for every address. It appears when the form searches by region and has regions.
- Maximum allowable travel time in minutes is required once dynamic travel times is on, and starts at 60. Only times within it are shown. Travel times are an estimate, and can run longer than the searchable time at peak hours.
- Minimum travel time allowance in minutes sets a floor. If the calculated drive is shorter, the visit allows this long. It cannot be more than the maximum.
- Book the drives in the AroFlo calendar puts the drive before the visit, and the one after it when both ends are on, on the AroFlo calendar as events titled "Travel to ..." and "Travel from ...". They have no task and keep the time free, for the same staff member and team as the visit. No extra route usage is charged for them. If the visit is moved from an auth link, its drives are taken off the calendar. Dynamic travel times has to be on.
Turning dynamic travel times off also turns off travel at both ends and the calendar drives.
When it goes wrong
A day offers nothing
Use Search Diagnostics to try the form on an address and read the reason for each time.
A visit that looks close is not counted
The radius is a straight line between the addresses. A visit that is a short way across the map can be a long drive, and one that is a long way in a straight line is never counted. Set the radius wider than the drive you will accept. With dynamic travel times on, the maximum travel time rules out long drives.
My change did not reach the form
Saving publishes the form. If the page says the form could not be published, the change is saved, and Publish again on the form sends it.