Calendar · reads event
Calendar
Month/week view across all dated nodes.
Everything with a date, laid out on a month or week grid.
4 Sep — Tasting — Maison Lauret
What it does
Behaviours, not fields. Choosing between two modules is choosing between these.
Places every dated record of a kind, so the month fills itself as conversations happen.
Shows the shape of the month rather than a list, which is what tells you the week that is overloaded.
An all-day entry and a timed one are different things and render differently.
How it works
- 1
Anything the agent schedules gets a date written onto it, and every dated record of that kind lands on the grid.
- 2
The month shown is the month the data is about, not today, so a calendar of next quarter is not an empty box.
- 3
Entries with no time render as all-day rather than being placed at midnight.
- 4
Editing a date moves the entry; nothing needs re-saying.
Best for
Anything where "when" is the first question.
Not the right choice for
Work with an order but no dates — a board reads better.
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 |
|---|---|---|
| Daterequired | date | A stated day, resolved against the conversation date. Tomorrow and next Tuesday both work. |
| Eventrequired | text | What is happening, in the words it was said in. |
| Time | time | A time if one was given. All day is a real value, not an absence. |
What it does not do
A module chosen for something it cannot do costs more than one that was never offered.
- One month at a time. A range spanning a quarter is reported as falling outside rather than shown.
- No recurrence. A weekly commitment is a row per week, which is fine for a season and painful for a year.
- Times are the agent timezone, which is wrong for anything scheduled across borders.
- No conflict detection — two things at eleven both render, and neither complains.
Before it works
What you have to provide, if anything.
- Nothing. It works from the first sentence that names a date.
- Pair with Bookings if slots need to be reservable rather than only visible.
In practice
A caterer juggling tastings, deliveries and supplier visits.
“Tasting with Maison Lauret on the fourth, eleven in the morning.”
What the agent built
A dated entry on the month grid, alongside everything else already scheduled.
What changed
The week of the seventeenth turned out to hold three commitments nobody had noticed stacking up. One moved.
Better with
These do a different job on the same data. An agent can have all of them.
The business puts on things people attend and needs the next few dates visible on the site without editing a page each time.
Customers reserve time, capacity is finite, and double-booking would be a real problem.
A single day has many dependent parts and the order matters more than the date — a shoot, an install, a wedding, a service window.
Who uses this page
Venue manager
Answers availability and capacity questions instantly, and turns them into real bookings.
Gym or studio
Answers timetable, level and membership questions, and signs people up.
Tutor or school
Answers parents’ questions and captures the level, subject and availability that matter.
Hairdresser or salon
Takes bookings while your hands are in someone’s hair.
Questions
What data does the Calendar page use?
It reads event records the agent has collected. Month/week view across all dated nodes. 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 calendar the wrong choice?
Work with an order but no dates — a board reads better. It is best for: anything where "when" is the first question.
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 Planning & time
Fri 12 Sep — Autumn tasting
Events
Everything the agent schedules — dates, place, attendees.
07:30
Load in, unlock the hall
45m
08:15
Floor plan and chairs
1h 30m
09:45
Sound check
30m
10:30
Doors
—
Planning / schedule
A run-of-show / agenda timeline.
Gantt chart
Tasks & phases with dependencies and durations.
Q3
Custom domains
Shipped
Q3
Module library
Shipped
Q4
Team accounts
In progress
Q1
Public API
Planned
Roadmap
Milestones across quarters/phases.
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