Contact
One inbox, read by the people who build it
An address matched to the wrong place
Send the address exactly as entered, the expected location and the candidate you selected. Those details help us reproduce the match.
A route result looked wrong
Tell us the stop count, metro area and what you observed, such as a repeated stop, an implausible detour or a segment that failed to calculate.
Business or fleet use
The current product handles one driver and one route. Tell us what you need and we can confirm whether the planner fits or whether dispatch software is the better choice.
Something missing
Tell us the task you were trying to complete, the device you used and where the current workflow stopped helping.
What helps us answer faster
A route planner bug is almost always about specific addresses, so specifics are what make a report actionable:
- the addresses involved, copied exactly as you entered them;
- what you expected and what happened instead;
- phone or computer, and which browser;
- a share link to the route, if you still have one open.
Bear in mind that a share link contains the addresses it was built from. If those belong to customers, describe the problem instead of sending the link.
What we cannot help with
We cannot retrieve yesterday’s route for you: there is no account-based server history after a request has been processed. We also cannot help with problems inside Google Maps, Waze, Apple Maps or a gig platform’s own app once the route has been handed over to it.
Coverage questions have a short answer: the planner works across the 48 contiguous states and Washington, DC. Alaska, Hawaii and the US territories are not supported yet, and telling us you need them is useful.