Bookings — A 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. Plain English: the thing you book is the same thing you report on. Nothing to export, nothing to keep in step by hand. A booking is a row on a table you chose. The client, the service and the stylist are links to other tables — which is what puts the booking in every report and filter you already have.