Query, edit, and export a plan with AICopy link
Someone calls to cancel, a driver phones in sick, dispatch wants the stop list in the format the warehouse screen expects. The assistant answers questions about the finished plan, applies edits to it, and produces the output you ask for.
Open the plan in a tab, point your assistant at it, and it reads the whole solution: every route, every stop in driving order, arrival and departure times, loads, waits, reported problems, and the orders nobody could serve. It works on a plan you just optimized and on a saved plan you reopened by its link.
Querying a finished planCopy link
Which routes finish after 16:00, and by how much?
List every stop arriving in a 15 minute window or less of its deadline.
Those are the ones that will slip if the morning runs late.
Route 3 looks light. What is its load factor and its total distance
compared to the others?
Give me the stop sequence for van 2 as a numbered list with addresses
and ETAs, ready to paste into WhatsApp.
The assistant reads the plan open in the tab; no export step is involved.
Batch-edit from a sentenceCopy link
Manual editing through an assistant uses the same engine as drag and drop in the app, including the shared undo history. A batch is applied all or nothing: either every change lands, or none does.
Cancel orders 88431 and 88437, they called this morning. Then move the
three Molenbeek stops from route 1 to route 2, put them after the
Rue Verte stop, and re-sequence route 2 afterwards.
What is available:
| Ask for | What happens |
|---|---|
| "move these stops to route 2" | Stops are re-planned onto that route, at a position you name or the cheapest one |
| "take these off the routes" | They become unassigned and stay in the plan |
| "give route 4 the big truck instead" | The route keeps its stops, changes vehicle |
| "split route 1 in two" / "merge 3 into 2" | Routes split and merge |
| "add an empty route" / "delete the empty one" | Routes are created and removed |
| "tidy up route 2" | One route is re-sequenced |
| "undo that" | The last edit is reverted |
The assistant's undo walks the same history as your manual edits in the app. If you dragged a stop a minute ago, "undo that" can revert your change, not the assistant's. Ask for a corrective edit rather than a blind undo when both of you have been working.
Problems and drift reportingCopy link
Problems are reported, not refused. An edit that breaks a time window or overfills a van is still applied, exactly like dragging the stop yourself. Routing24 scores it and reports the problem, and the assistant relays it. Ask "what did that break" after any significant edit, see Problems and warnings, explained.
Drift from the last optimization is measured. Every read and every edit carries a comparison against the last full solve, covering your manual edits as well as the assistant's. When it degrades materially, the assistant is required to say so, leading with cost, for example "cost +2348 (+12.3%), distance +12.4%, 1 new problem vs the last optimization", and to offer a fix: re-sequence the one rough route, or re-run the optimizer.
Any edit puts the app behind a full-screen Agent controlled overlay, which blocks manual editing until it finishes. Press Take control to take it back at any moment. The edit history is shared, so you can continue by hand exactly where the assistant stopped.
Getting the result outCopy link
The standard export does not need an assistant: Export on the Optimize page downloads the full solution workbook, see Export routes to Excel. Use it whenever the receiving side is a human with Excel.
The assistant is for the other cases, where you need a specific slice of the plan in a specific shape:
Write me a CSV with one row per stop: route number, stop sequence,
order id, customer name, arrival time as HH:MM, and pallets. No header
row. That is what our warehouse screen imports.
Draft one email per driver with their stop list, ETAs and the customer
notes, and the plan link at the bottom. Do not send them, let me read
them first.
Post tomorrow's route summary to the dispatch channel: driver, number
of stops, first and last ETA, total distance. One line each.
Compare today's plan against the one we saved yesterday and tell me
what actually changed: stops added, stops dropped, routes that got
longer.
Because the assistant holds the structured solution, it can push those into any system it can reach: a spreadsheet, an email draft, a ticket, a message, or an API your ERP exposes. Routing24 has no self-serve public API, see Integrations, so an assistant holding both ends is how a finished plan reaches a system we do not integrate with directly.
Ask the assistant to save the plan and give you the link. If you are not signed in, that link opens the plan only in this browser on this computer, so sign in first when the link has to reach someone else. Driver-facing links are a separate feature, see Share a route with a driver.
Next stepCopy link
- WebMCP: Routing24 as an AI tool explains what the assistant is calling.
- Edit routes by hand: drag, split, merge is the same editing model, done with a mouse.