Map · reads route
Routes
Paths between places.
Anything with an address or coordinates, placed.
- 1 — Café Bellevue, 75011
- 2 — Hôtel Vasari, 75004
- 3 — Marché, 75004
What it does
Behaviours, not fields. Choosing between two modules is choosing between these.
Ordered stops with distances, because the same four addresses in a different order can be an hour apart.
Time windows per stop, which is where a route usually breaks.
A conflict between the order and the windows is visible rather than discovered mid-round.
How it works
- 1
Stops are entered in the planned order with their time windows.
- 2
A window that conflicts with the order is visible before the van leaves rather than at the third stop.
- 3
Distances between consecutive stops show where the order is costing time.
- 4
Reordering renumbers the run.
Best for
Places, deliveries, catchments, anything geographic.
Not the right choice for
Data where location is incidental.
What a row holds
Every field, and what the agent listens for to fill it — which is the difference between a page you type into and one that fills itself.
| Field | Type | Filled from |
|---|---|---|
| Stoprequired | number | Position in the run. The order is the content. |
| Addressrequired | text | The destination for this stop, usually taken from an order or a customer record. |
| Distance | text | How far from the previous stop, which is what makes the order matter. |
| Window | text | When it has to happen by. A conflict with the order is the thing to catch. |
What it does not do
A module chosen for something it cannot do costs more than one that was never offered.
- CANNOT BE BUILT YET. No DataModule type draws a route, and no provider computes travel time.
- No optimisation even once it exists — the order is yours, and nothing suggests a better one.
- Distances are as entered, not computed.
- No live tracking or ETA.
Before it works
What you have to provide, if anything.
- Not currently possible. Use Deliveries, which is a table and renders today.
- When it lands it needs coordinates plus a routing provider, which is a cost per request.
In practice
A delivery round of four stops across Paris.
“Bellevue before nine, the market before ten, Vasari between nine and eleven.”
What the agent built
A route with distances and windows in the planned order.
What changed
Stop three had an earlier window than stop two. Reordering saved a doubling-back that had been happening every week.
Better with
These do a different job on the same data. An agent can have all of them.
Goods travel to customers and "where is my order" is a question the agent should answer without a person.
The business has several physical places, or recommends them, and proximity is what decides between them.
The business runs vehicles and the renewals are currently tracked in someone's memory.
This module cannot be built yet
Drawing a route needs coordinates and a projection, and ordering one usefully needs travel times between points — which is a routing API on top of geocoding, with a cost per request. The stops and their windows are recorded correctly and the order is respected; what cannot be drawn is the line, and what cannot be computed is whether that order is the fast one. Same blocker as Map, plus a second provider.
Questions
What data does the Routes page use?
It reads route records the agent has collected. Paths between places. Nothing has to be imported first — the page appears once there is something to show.
Do I have to build or configure it?
No. You describe what you need in a sentence and the agent chooses the view and fills it. Custom pages exist for the cases no built-in view covers, and those are reviewed before they go live.
When is a map the wrong choice?
Data where location is incidental. It is best for: places, deliveries, catchments, anything geographic.
Does it stay up to date?
Yes. The page is a view over the data rather than a copy of it, so anything the agent learns afterwards shows up without a rebuild or a re-import.
More in Places & logistics
- Oberkampf — 48 rue Oberkampf, 75011
- Marché des Vosges — Place des Vosges, 75004
- Café Bellevue — 12 rue de Charonne, 75011
Map / locations
Pinned places.
The Long Room
80 standing, 50 seated
Open, pillars
Atelier, 2nd floor
24 seated
Workshop, benches
Courtyard
120 standing
Outdoor, covered half
Meeting room
10 seated
Boardroom, screen
Venues
Candidate locations.
14–16 Oct
Lyon
TGV 06:52 from Gare de Lyon
16–18 Oct
Turin
Train, 4h, change Chambéry
18–20 Oct
Milan
Train, 1h50
20 Oct
Return
Flight MXP–CDG 19:40
Travel plan
Segments of a journey.
09:00
Coffee and briefing
Oberkampf
10:30
Roastery tour
Atelier Nord
12:30
Lunch
Café Bellevue
15:00
Cupping session
Oberkampf
Itinerary
Day-by-day plan.
Ask for it in a sentence
You do not configure this page. You tell your agent what you need and it builds it from what it has already collected.
Build your agent free