01A booking is a row
When somebody books time with you, RowFold writes a row in one of your tables. Not into a separate booking product you later reconcile against your real data. A row, in a table you can see, with columns you chose.
Everything else follows from that. The booking is on your scheduler because it has a date. It is in your reports because it is a record. It can fire an automation, sit in a filtered view, go out in a CSV or come back through the API. None of that had to be built for bookings. It works because a booking is not special.
02Two doors, one table
There are two surfaces, and they are opposite ends of one thing.
| Surface | Who it is for | What it does |
|---|---|---|
| Booking page | Anyone with the link. No account. | Shows the free slots and writes one booking. |
| Scheduler | You and your team | Reads the whole day back: a column per person, drag to move, check people in. |
Same table, same rows. If you already have a booking page, the scheduler usually arrives configured — it reads that page's settings — it does not ask you a second time which link is the staff member and which is the client, because the page already answered that.
03Availability is data, not a settings screen
Your opening hours live in a table. Each row is roughly a sentence: this person, this weekday, from this time to this time. Which means you can edit them in a grid, paste a season of them in from a spreadsheet, or have an automation close the shop, using the things you already know how to do.
Two kinds of row. A Working hours row adds time. A Time off row takes it away, and can name a single date, a range, or nobody at all — leave the person blank and it closes the whole business for a bank holiday, in one row.
From there the page subtracts the practical things: slots that overlap a booking you already have, the gap you want either side of an appointment, anything sooner than your minimum notice, anything further out than your booking window. What is left is what a visitor sees. If they have not asked for a particular person, it offers whoever has the lightest recent load rather than always the first name on the list.
04Running the day
Taking the booking is the easy half. The scheduler is the other one: a day laid out as a column per staff member, room or chair, including the people with nothing booked, because an empty column is usually the one you want to fill.
Click an empty slot to book it. Drag an appointment to move it, or into someone else's column to reassign it in the same movement. Drag its bottom edge to change how long it runs. Down the side, a short list of the things that actually need a decision: bookings with nobody assigned, and anyone double-booked. Both are worked out from the data rather than from a status somebody has to remember to set, so the number is always real.
05Moving one, and who gets told
Two things happen when you move a booking, and both are easy to take for granted until they go wrong somewhere else.
It keeps the length it was booked with. A haircut booked when that service was 90 minutes stays 90 minutes when you move it, even if you have since changed the service to two hours. Bookings you have already taken never shift under you, which is what makes last quarter's schedule still true.
The customer is told. A moved booking sends an email showing the old time struck through above the new one, because the first thing most people think is “was that always when it was?” A cancellation says who cancelled it. And both report back who was actually told — if the booking has no email on it, you are told nobody to notify rather than being left to assume a message went out.
Cancelling sets your own cancelled status, whatever you happen to call it, so the booking stays visible as a cancellation instead of vanishing from the day it was on.
06Repeats, classes, and things booked by the night
A repeat is stored as a rule, not as a thousand rows. “Every Tuesday, forever” is literally true: no hidden end date, no cap. Change one and you are asked how far it should reach — just this one, this and every later one, or the whole repeat — and the middle answer leaves everything before today exactly as it was.
A class is not a double-booking. Twenty people at one yoga session is twenty rows at the same time with the same instructor. Tell the view how many the session holds and it counts seats instead, so only the real problems are left: a full class, and an instructor booked into two different rooms.
Some things are booked by the night. Cottages, rooms, boats, hire cars. Give the view a start date and an end date with no time of day and it becomes a chart with a row per unit and a column per day. The end date is the day the unit comes free again, so a guest leaving on the 8th and one arriving on the 8th sit side by side rather than reading as a clash.
07What it does not do
Two gaps worth knowing before you decide. Finding them later is probably worse than reading them now.
- No deposits or card payments at the point of booking. You can take a booking; you cannot take money for it in the same step.
- No two-way sync with Google Calendar or Outlook. A visitor can download a calendar file for their own diary, and that is one direction only — a meeting in your personal calendar does not block a slot here.
Next: a workspace already shaped for this, the helpdesk (same scheduling engines, a support face), or what it costs. Bookings are part of RowFold, not an add-on with its own price. There is a longer walkthrough in the help centre once you are signed in.