Bookings

How it works

1
The agent writes a date onto whatever it schedules — a booking, a delivery, a call.
2
The calendar reads every node of that kind that carries one and places it.
3
Moving something on the grid writes the new date straight back.

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.

Who uses this page

Venue manager

Answers availability and capacity questions instantly, and turns them into real bookings.

Restaurant

Answers the menu, the allergens and the opening hours — in every language your guests speak.

Private chef

Takes the brief — dates, guests, diets, budget — while you are still cooking.

Estate agent

Qualifies buyers, answers property questions, and books viewings while you are at one.

Questions

What data does the Bookings page use?

It reads booking records the agent has collected. Appointments on a calendar. 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.