Skip to content

Timeline · reads event

Itinerary

Day-by-day plan.

A run of events in order, along a single line.

Written for someone who does not know the city. The notes column is why.

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. 1

    A day is planned hour by hour and handed over rather than kept.

  2. 2

    Every line is written for somebody who does not know the city, which changes the wording throughout.

  3. 3

    The notes column carries the detail that stops a guest calling.

  4. 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.

FieldTypeFilled from
TimerequiredtimeA clock time on the day, as dictated when the day is planned out.
WhatrequiredtextWhat happens, phrased for somebody who has not been before.
WhererequiredtextThe place. Required, because a guest needs it and the host already knows it.
NotestextDirections, 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 was said to the agent

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.

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.

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

Agents

More

👤
Profile
FAQ