Timeline · reads event
Itinerary
Day-by-day plan.
A run of events in order, along a single line.
09:00
Coffee and briefing
Oberkampf
10:30
Roastery tour
Atelier Nord
12:30
Lunch
Café Bellevue
15:00
Cupping session
Oberkampf
What it does
Behaviours, not fields. Choosing between two modules is choosing between these.
One day, hour by hour, written for somebody who has not been there before.
The notes column is the difference between a schedule and something a guest can follow.
Handed over rather than kept, which changes how every line is worded.
How it works
- 1
A day is planned hour by hour and handed over rather than kept.
- 2
Every line is written for somebody who does not know the city, which changes the wording throughout.
- 3
The notes column carries the detail that stops a guest calling.
- 4
Changes propagate to whoever has the link rather than needing a reissue.
Best for
A schedule someone reads top to bottom — a run-of-show, an itinerary.
Not the right choice for
Comparing parallel workstreams; that is a Gantt.
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 |
|---|---|---|
| Timerequired | time | A clock time on the day, as dictated when the day is planned out. |
| Whatrequired | text | What happens, phrased for somebody who has not been before. |
| Whererequired | text | The place. Required, because a guest needs it and the host already knows it. |
| Notes | text | Directions, booking references, anything that prevents a phone call. |
What it does not do
A module chosen for something it cannot do costs more than one that was never offered.
- One day per itinerary. A multi-day visit is several, or a travel plan.
- No live updates or notifications if something moves.
- Times are the host timezone.
- No map, so directions are text.
Before it works
What you have to provide, if anything.
- Nothing.
- Write it for a stranger. An itinerary written for yourself is a schedule and helps nobody else.
In practice
A roaster hosting a buyer visit.
“They arrive at nine, roastery tour at half ten, lunch booked for eight at Bellevue.”
What the agent built
A timed day with places and the walking directions between them.
What changed
The guests found the roastery without calling. The 20-minute-walk note was the line that mattered.
Better with
These do a different job on the same data. An agent can have all of them.
A trip spans several days and locations, and the shape of it needs agreeing before the detail exists.
The business puts on things people attend and needs the next few dates visible on the site without editing a page each time.
Spaces are offered or recommended, and the choice turns on capacity and facilities rather than location.
Questions
What data does the Itinerary page use?
It reads event records the agent has collected. Day-by-day plan. 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 timeline the wrong choice?
Comparing parallel workstreams; that is a Gantt. It is best for: a schedule someone reads top to bottom — a run-of-show, an itinerary.
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.
- 1 — Café Bellevue, 75011
- 2 — Hôtel Vasari, 75004
- 3 — Marché, 75004
Routes
Paths between places.
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