Contact
One inbox, read by the people who build it
An address matched to the wrong place
The most useful report we get. Send the address exactly as you typed it and where it should have landed. Geocoder gaps are fixable once we can reproduce them.
A route came out wrong
Tell us roughly how many stops, the metro area and what looked wrong, such as a repeated stop, an obvious detour or a leg that failed to calculate.
Business or fleet use
Multiple drivers, time windows, service durations, API access. Include how many stops and drivers you run on a typical day; that shapes what gets built first.
Something missing
Truck routing, avoiding tolls, a state we do not cover yet, an import format that failed. Feature requests from people driving real routes carry the most weight.
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.