Bookings

What it does

Behaviours, not fields. Choosing between two modules is choosing between these.

Shows the free slots, which a booking list cannot. The empty space is what a visitor is actually looking for.

The agent will not offer a slot already taken — the only guarantee that matters in a booking module.

Duration comes from Services, so a ninety-minute treatment consumes ninety minutes rather than an arbitrary hour.

Payment state is informational and does not block. Refusing an unpaid booking is a business decision, not a default.

How it works

1
Bookable slots are defined by opening hours and service duration; the module renders the whole grid, taken and free.
2
A booking fills a slot. The agent will not offer one already taken, which is the only guarantee that matters here.
3
Duration comes from Services where it exists, so a 90-minute service consumes 90 minutes.
4
Paid is informational. Nothing prevents an unpaid booking, because refusing one is a business decision, not a default.

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
Slotrequired	time	A stated day and time, resolved against the current date.
Customerrequired	text	Who the slot is for. "Free" is a real value, not an absence.An empty slot is the thing this module shows that a booking list cannot.
Service	text	Matched against Services, which supplies the duration.
Paid	choiceUnpaid · Deposit · Paid · Invoiced	Mentioned payment, or set by Payments when the amounts match.

What it does not do

A module chosen for something it cannot do costs more than one that was never offered.

The grid is a month drawn from the dates in the data. There is no week or day view, so a business with many slots per day will find one cell crowded.
No double-booking protection across two agents sharing a resource. Each agent sees only its own rows.
No cancellation policy, no reminders, and no sync with an external calendar.
Times are the agent timezone, not the visitor one, which is wrong for anything booked across borders.
Rows whose date falls outside the displayed month are counted and reported rather than shown — the grid is one month, not a scrolling range.

Before it works

What you have to provide, if anything.

Needs a dataset with a parseable date column. The module says so rather than drawing an empty grid when it cannot find one.
Pairs with Services, which supplies the duration a slot consumes.

In practice

A studio taking consultations by phone, in a paper diary.

“Thursday ten with Lena, ninety minutes, fifty euro deposit.”

What was said to the agent

What the agent built

The slot filled, the deposit recorded, and the two hours around it left visible as bookable.

What changed

The diary stopped being the only copy. In the first week it caught a double booking already made on paper and not yet discovered.

Better with

These do a different job on the same data. An agent can have all of them.

ServicesLive

You sell time and expertise rather than objects, and people need to know the shape of an engagement.

ContactsLive

Almost any agent that talks to more than one person and needs to remember who they were. The default people module when nothing more specific fits.

PaymentsLive

Payments arrive by several routes and the net figure never quite matches what was invoiced.

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.