Effective: Aug 6th, 2026

Applies to:

• MileMaker 2.0 WebApp

What's New

MileMaker now includes a built-in AI Assistant in the WebApp. Ask for directions and mileage in plain language, describe your constraints, compare results across map guide versions, and run a whole spreadsheet of routes without leaving the conversation.

• Ask in plain language. Type a question the way you'd say it — "how far from Dallas to Laredo with a 53-foot trailer?" — and get directions, distance, and drive time back. No forms to fill in first.
• See it on the map, not just in text. Any route the Assistant calculates can be visualized on the WebApp map in the same session — the path, the stops, and the turn-by-turn directions — with nothing to re-enter. 
• Compare Guide 19 and Guide 20 side by side. Ask for the same route under both guide versions and see the difference, so you can validate mileage changes before you standardize on one.
• Process routes in bulk from a spreadsheet. Upload a spreadsheet of origins and destinations, and the Assistant runs the whole file and returns the results for download.
• Build a mileage matrix by asking for one. Give the Assistant a set of locations and it calculates the point-to-point mileage matrix across them, then returns it for review and download. This was previously available through the MileMaker API only — it's now reachable by anyone in the WebApp, with no integration work.
• Keeps the thread. Follow-up questions build on what you already asked — add a stop, switch the vehicle profile, or re-run under a different guide without re-entering everything.

Why it matters

• Skip the setup. Routing options and vehicle parameters that normally mean working through several screens can just be stated in the request — "53-foot trailer, avoid tolls, practical route" — and changed as fast as you can ask the next question.
• Insight into your bulk results, not just the results. Bulk routing already lives in the WebApp; what's new is that the Assistant can analyze the output. Ask which lanes came back longer than expected, what the outliers have in common, or how this run compares to the last one — instead of exporting the file and working it out in a spreadsheet yourself.
• Explanations, not just numbers. Ask what "practical" and "shortest" actually mean for your lanes, or why Guide 19 and Guide 20 return different mileage on a specific route, and get an answer in context — with the routes to demonstrate it. Knowledge that used to live in documentation or a support ticket is now part of the conversation.
• Catch problems at a glance. A mileage number on its own is hard to sanity-check. Seeing the route on the map makes an unexpected detour or a mis-resolved stop obvious immediately, before it reaches a rate or a dispatch.

Availability

AI Assistant is available for all users in the MileMaker WebApp.

Questions or need help configuring your provider? Contact MileMaker Support via support@milemaker.com.