Re-batch when the board changes
New stops, cancellations, or a closed ramp should not wait for tomorrow’s planning window, drivers need a route that matches dispatch right now.
Routing, ETAs, and dispatcher tools built for the volume your fleet actually runs.
Re-optimize mid-shift, validate addresses at intake, and keep ETAs honest as traffic moves.
Trusted by fleet teams across North America.
Built around how fleets actually run
Keep the ETA tied to the road
When flow drops, the window in your TMS or customer portal should move before the first “where’s my truck” call.
Validate the address before it hits the solver
Bad suite numbers and bad geofences belong in the exception queue, not baked into an “optimal” line that sends a driver to the wrong dock.
One map surface for the lead
Vehicles, geofences, and incidents on one screen beats tab roulette when the shift is already behind.
Why fleet teams choose MapQuest
Pricing that scales with your fleet, not against it.
Per-call maps pricing turns every re-run into a finance conversation. We price for the route and geocode volume you actually run so ops can re-batch without opening a ticket to procurement.
Routing that survives the morning
The plan from the stand-up rarely survives first coffee. You need legs, traffic, and time windows that can be re-cut mid-shift without swapping vendors, same point we make in the field notes below.
A real partner, not a portal.
Enterprise fleets get named technical support and account coverage. When dispatch calls at shift open, there is a person who knows your integration, not a generic queue.
What we've learned working with fleet operators
The biggest gains usually don't come from a smarter optimizer, they come from re-optimizing more often. Dispatch plans built at 6am rarely survive the morning intact, and fleets that re-plan mid-shift consistently outperform those that don't.
Address quality is the silent killer of route efficiency. A clean optimization on a dirty address list still ends with a driver in the wrong parking lot. The fleets seeing the biggest gains validate addresses at order intake, not at dispatch.
ETAs aren't a one-shot promise, they're a relationship with the customer. The fleets we work with that update ETAs every couple of stops report higher delivery satisfaction than the ones that lock in a window at dispatch.
Want the deeper technical view? Read our routing best-practices guide →
Common questions from fleet teams
How is pricing structured compared to per-call maps and routing APIs?
Contracts are built around the route, geocode, and tile volume you actually run, not a long tail of metered SKUs on every screen load. We walk pricing with your ops and finance leads against your dispatch pattern so re-optimization is not a budget line item.
What SLAs and uptime commitments do you publish for enterprise fleets?
Targets for availability, support response, and escalation are set in the enterprise agreement, not on a marketing landing page. If we miss a committed window, remedies are spelled out there (typically credits plus a written recovery plan). Exact numbers are reviewed line-by-line before signature.
How does MapQuest sit next to our TMS and telematics (Samsara, Geotab, Motive)?
Your telematics system stays the system of record for vehicles, HOS, and breadcrumbs. MapQuest supplies directions, matrixed ETAs, geocoding, and map tiles over REST; most fleets wire us in where stops are built or where dispatch renders the map. Samsara, Geotab, and Motive are common pairings, integration is usually stops and positions in, routes and polylines out.
What does onboarding look like from contract to production?
Expect a proof-of-concept in your sandbox in about a week once keys and sample loads are in place. Hardening for auth, caching, rate limits, and cutover is usually four to eight weeks depending on how many environments you run and who owns QA.